MCP Compatibility Checker
Enter your remote MCP server's URL and get a live 7-point audit against the July 2026 spec rewrite — a full pass/fail breakdown, not just a single verdict, plus concrete upgrade guidance for anything that's out of date.Free, no account needed.
Last verified
MCP spec rules checked against: the official changelog,
How this works
This isn't a single yes/no check — it's seven independent probes run live against your server, each testing a distinct, verifiable signal from the 2026-07-28 specification: whether server/discover (the RPC every compliant server must expose) is implemented; whether results carry the requiredresultType field; whether the server has stopped issuing Mcp-Session-Id; whether it actually enforces the required MCP-Protocol-Version/Mcp-Method headers by rejecting a request that's missing one; whether the deprecated ping method has been removed; how a GET request to the MCP endpoint behaves; and whether the legacy initialize handshake is still accepted. Every result page shows a pass/fail/informational line for each — a real audit, not a headline you have to take on faith.
Enter your URL above and the audit runs immediately — no payment, no account, no waiting on a checkout redirect. Once you have a result, free re-checks are available for 60 hours so you can confirm a fix without re-entering the URL.
Frequently asked
What exactly does this check?
Seven independent checks against your server, run live: whether it implements server/discover (the RPC every 2026-07-28-compliant server must expose), whether its results carry the required resultType field, whether it's stopped issuing Mcp-Session-Id, whether it actually enforces the required MCP-Protocol-Version/Mcp-Method headers, whether the deprecated ping method has been removed, how it responds to a GET on the MCP endpoint, and whether it still accepts the legacy initialize handshake. Each shows up as its own pass/fail/informational line in your report, not just one overall verdict.
Can I re-check the same server after fixing an issue?
Yes — free re-checks for 60 hours after your first result. Fix what the report flagged and click "Re-check this server" on your result page as many times as you need within that window, without re-entering the URL.
Can I keep a copy of my report?
Yes — your result page has "Copy report as Markdown" and "Download .md" buttons, so you can paste it into a pull request or hand it to a teammate instead of it only existing as a webpage.
Does this work for local (stdio) MCP servers?
Not in this first version — only remote servers reachable over HTTP (the Streamable HTTP transport). A local, stdio-only server has no URL for this tool to probe.
Where do these compatibility rules come from?
Directly from the official MCP specification changelog and Streamable HTTP transport page (checked August 14, 2026), not from secondary commentary. See the source link in your result for the exact page.
Emitted as FAQPage JSON-LD from the same frontmatter — one source, no duplicated prose.