Free tool

Is your MCP server open to anyone?

Paste the address. We send the same first requests any AI client sends and tell you, in plain words, what a stranger would get.

Read only. We send the same first requests any MCP client sends, then stop. Nothing is stored. Only check servers you own or are allowed to test.

What it checks

Four things that decide whether strangers can use your server, and whether real users can sign in.

Sign-in required

We start a session the way Claude or Cursor would, with no token. A safe server refuses. An open one hands back a session.

Tools visible to anyone

If the session opens, we ask for the tool list. Every tool a stranger can see is a tool a stranger can call.

Sign-in discovery

Connectors look for a /.well-known/oauth-protected-resource document to find your login server. Without it, users hit a dead end.

Encryption and reachability

https with a valid certificate, no redirects that confuse clients, and no software names leaking in headers.

What the check does not do

It is read only. It never calls a tool, never sends data, never guesses passwords, and keeps nothing about your server. Eight checks per connection every ten minutes.

Knowing it is locked is step one. Seeing what happens inside is step two.

AriesView Security records every call to your MCP server with the user and client behind it, and flags the odd ones. Two lines of code for a Python server.