Free tool · no sign-up · a few seconds
Test your MCP server online
Paste your server's URL. We connect the way Claude, Cursor and the directories do: initialize, then list the tools. You see whether a client gets in and, if not, why and what to change.
What it checks
- The address: the hostname has to resolve at Cloudflare's public resolver. A lapsed domain or a deleted subdomain stops every client.
- The handshake:
initializeover Streamable HTTP with protocol version 2025-06-18, and once more with the version your server names if it refuses that one. - The tools:
tools/liston the same session, the list a client shows its user. - Sign-in: when the server answers
401, we follow MCP sign-in the way the official TypeScript SDK does: the protected resource metadata, the authorization server's metadata, then whether a new app can register and use PKCE. We only read public metadata: no app is registered and no sign-in page opens. - The older SSE transport: when the URL is an event stream, we check that it names its message endpoint.
- The host's own error page: a Cloudflare Tunnel that isn't connected (530, error 1033), a Vercel deployment that's missing or crashing, a proxy whose app is down.
A server that asks for a key, limits the rate or speaks only the newest protocol version has answered, so we say so instead of calling it down. A sign-in that clients can't complete is different: we name the step where it stops.
Why servers fail
This month, 1 in 20 company MCP servers in the official registry failed this check twice. The causes, and a fix for each, are in the state of MCP servers.
Questions
Is it free?
Yes, with no sign-up and no email, up to 10 tests an hour.
Do you call my tools?
No. We send initialize, the initialized notification and tools/list, as directories do. When a server asks for sign-in, we also read its public sign-in metadata. Nothing else.
It works in my client but fails here. Why?
We test from Cloudflare's network, not your machine. A server that only listens on localhost or a private network, allows only some IP ranges, or needs a key in the URL works for you and fails for everyone else, including directories.
What do you keep?
The address you tested and its result, for up to 30 days, to spot common problems. Nothing about you. See Privacy.