mcptest.io

mcptest.io is a browser-based inspector, playground, evaluator, and public catalog for remote Model Context Protocol (MCP) servers. It speaks the current stateless MCP protocol and remains compatible with stateful and legacy servers already in production.

What it supports

• MCP 2026-07-28 (stateless): probes with server/discover, sends self-describing requests, and adds the required MCP-Protocol-Version, Mcp-Method, and Mcp-Name routing headers.
• MCP 2025 and earlier (stateful): automatically falls back to initialize / notifications/initialized, retains Mcp-Session-Id, and supports JSON or SSE responses over Streamable HTTP.
• Legacy HTTP+SSE: detects the original two-endpoint transport as a final compatibility fallback.
• Capabilities: discovers and exercises tools, resources, and prompts with raw JSON-RPC logs and schema-driven tool forms.
• Authentication: supports OAuth 2.1 with PKCE, bearer tokens, and API keys. Target credentials remain separate from Firebase credentials when the optional CORS proxy is used.
• Server catalog: ships a validated catalog of public remote servers, authentication and protocol badges, and indexable server report pages included in the sitemap.
• Evaluation: creates shareable server reports and reusable tool-call dashboards.
• Headless release gate: evaluates remote endpoints in CI and emits the same versioned JSON and Markdown report semantics as the web app.

The exact URL entered by a user or supplied by the catalog is tried first. Conventional /mcp and /sse paths are compatibility fallbacks; they do not replace an explicit custom endpoint.

For command-line and GitHub Actions usage, credential handling, thresholds, and stable exit codes, see the headless release gate guide.

Embedding a badge

Show that your MCP server has been tested by adding a badge to its README. Every report page and catalog server profile has a “Share and embed” section with ready-to-copy Markdown, HTML and reStructuredText snippets that link to the public report for the endpoint.

[![Tested on mcptest.io](https://mcptest.io/badge/mcptest.svg)](https://mcptest.io/report/https%3A%2F%2Fexample.com%2Fmcp)

Replace the URL-encoded endpoint after /report/ with your own. Result badges use the release decision vocabulary from the report: ready.svg, review.svg, blocked.svg, unknown.svg and authorization-required.svg under https://mcptest.io/badge/. These static badges record the result at the time you copied the snippet.

Catalog servers can use a badge that follows the latest catalog validation instead:

[![Tested on mcptest.io](https://mcptest.io/badge/server/context7.svg)](https://mcptest.io/servers/context7/)