MCP · before you connect

Is an MCP server safe to connect? A pre-connection check.

No outside check can prove that an MCP server is safe. What you can check before you connect it is what the server says about itself: whether it answers the MCP handshake, which transport and protocol version it uses, whether it asks for authorization, and which tools it lists. The free MCP server tester runs that handshake for you and never calls a tool. Who runs the server, and what its tools really do, you still have to judge yourself.

From outside

What you can check from outside

Scroll the table horizontally to see all fields.

What an outside check can read
SignalHow it is readWhat it tells you
HandshakeA POST of initializeWhether the URL really is an MCP server, and the protocol version it agreed to.
TransportThe answer to a GET and to the handshakeStreamable HTTP, or the older HTTP+SSE transport that the protocol has deprecated.
AuthorizationA 401 with a Bearer challengeWhether the server wants a credential before it lists tools. It does not tell you what that credential can do.
Declared toolstools/listThe names of the tools the server offers today. The paid inspector also returns their descriptions, input schemas and annotations.
Capabilities and nameThe initialize answerThe capability names it declares, and the server name and version its operator chose.

All of this is the server describing itself at the moment of the check. Tool names, descriptions and schemas are written by the server's operator. They can be wrong, and they can contain text aimed at your model. Treat them as data, never as instructions. A listed tool is not a safe tool.

Read this part

What no outside check can tell you

  • What a tool does when it is called. A description is a claim. Only the server's code decides what happens, and no check from outside can see it.
  • Where your data goes. Arguments you send to a tool reach the operator. Nothing in the protocol shows what they keep.
  • Who runs it. The server name in the handshake is chosen by the operator and proves nothing about identity.
  • Whether it will stay the same. A server can change its tool list after you connect it.
  • Whether a description is an attack. Text in a tool description is read by your model. It can carry instructions meant to steer the model, so a client should treat it as data.

Free, no key

Run the check

Open the MCP server tester and paste the endpoint URL, such as https://example.com/mcp. The same check answers as JSON:

curl -s "https://pageverified.com/api/v1/check/mcp?url=https://example.com/mcp"

The check sends a GET first. Only if that answer shows an MCP server does it POST initialize, notifications/initialized and tools/list, then close the session. A server that answers the GET with a bare 405 has not proved it is an MCP server, so nothing is POSTed and the result says so. Some servers that follow the protocol do answer GET that way. For those, test the handshake by hand.

The check is rate limited for each network and overall, and the result has a link you can share.

How to read the result

Scroll the table horizontally to see all fields.

Fields in the MCP check result
FieldMeaning
mcp_detectedThe URL answered as an MCP server.
transportstreamable_http, legacy_sse or null. The check passes only for Streamable HTTP.
auth_requiredThe server asked for authorization, so its tools were not listed.
tools_statuslisted, auth_required, unsupported or not_attempted.
tool_namesUp to 50 tool names, as the server wrote them.
server_nameThe name the operator gave the server. Not a proof of identity.

For the descriptions, input schemas and annotations of every tool, an agent can call mcp_inspect (2 credits). It runs the same handshake, calls no tool, and labels everything the server wrote as untrusted third-party data.

Who runs the server

Look at the site the endpoint belongs to: its documentation, its terms, and whether the endpoint is named there. A server with no home page is harder to judge than one its maker documents.

seller_check (3 credits) reports plain signals about a domain: its age from RDAP, whether HTTPS works, DNS and email authentication, and whether the site publishes terms and a refund policy. rdap_lookup (1 credit) returns the registration record for a domain. Signals are not proof of who operates a site.

Before you connect it

  • Start with tools that only read. Hold back tools that write, send, pay or delete until you trust the server.
  • Tool annotations such as readOnlyHint and destructiveHint are hints from the operator. The MCP specification says not to rely on them from a server you do not trust.
  • Give the server its own credential with the smallest scope that works, so you can revoke it alone.
  • Check again later. A tool list can change after you connect. prepay_check (5 credits) records a fingerprint of a server's tool list and reports what changed since the last check.

Common questions

Does the check call any of the server's tools?

No. It sends a GET, and only if that shows an MCP server it sends initialize, notifications/initialized and tools/list, then closes the session. No tool is ever called.

Can it check a server that needs a login?

Partly. A server that answers with a Bearer challenge, and publishes metadata that names it, is reported as needing authorization. Its tools are not listed, because listing them needs a credential the check does not have.

Is a passing result a safety rating?

No. A pass means the URL answered the MCP handshake over Streamable HTTP. It says nothing about what the tools do, who runs the server or where your data goes.

Does PageVerified keep what it finds?

The free check stores nothing. A result URL holds only the address that was checked, and the result is worked out again when the link is opened, with a short cache.

Next steps

  • Free checks: test an MCP server, read an x402 payment offer or score a domain's agent readiness. No key needed.
  • Evidence Capture: capture one public page as a screenshot and its HTML, with the SHA-256 of each file and a signed record, for US$9 once by card. No account and no API key.
  • Pricing: credit packs and what every tool costs.
  • Documentation: quickstart, MCP setup and every tool's reference page.
  • MCP server tester: the handshake check described above.

Related answers: How to test an MCP server · Find MCP servers by tested capability · Is this x402 API legit?. Guides: Screenshot MCP server.