Protocol & transport
Detects the stateless 2026-07-28 protocol (server/discover), stateful Streamable HTTP with initialize and sessions, or the deprecated HTTP+SSE transport, the way the spec tells clients to.
Connect to a remote MCP server the way a real client does, and see what it offers and where it breaks the spec.
Kept in this browser only. Click one to test it again.
Detects the stateless 2026-07-28 protocol (server/discover), stateful Streamable HTTP with initialize and sessions, or the deprecated HTTP+SSE transport, the way the spec tells clients to.
Lists everything the server advertises, with pagination, and lints tool names, input schemas, descriptions and annotations. Estimates how much model context the tool definitions cost.
On a 401, follows the WWW-Authenticate challenge to protected resource metadata (RFC 9728) and the authorization server (RFC 8414 / OpenID), and checks PKCE S256 and client registration.
Sends a CORS preflight to see whether browser-based MCP clients can call the server, and whether they can read Mcp-Session-Id.
Desktop clients can launch local stdio servers. This tester runs on the Internet and can only reach remote HTTP servers on public addresses. Use the server's public URL, usually ending in /mcp (or /sse for older servers).
PASS: the server speaks MCP correctly. WARN: it works, with issues worth fixing. FAIL: clients will have trouble connecting or using its tools. AUTH REQUIRED: it asks for authorization first. Add a token to test what is behind it.
No. It only lists them, so a test never changes data on your server.