mcp-spec-check - Black-box readiness validator for MCP 2026-07-28 servers
Show HN: Only 1 of 4,356 reachable MCP servers is ready for the 2026-07-28 spec
mcp-spec-check is a powerful command-line tool that instantly verifies if your remote Model Context Protocol (MCP) server is ready for the upcoming 2026-07-28 specification release. Using pure black-box HTTP probes, it assesses critical requirements like the new stateless core, routing headers, and session independence without needing code access. This tool helps developers avoid future compatibility issues by providing a clear readiness verdict in seconds, complete with migration links. Whether you are maintaining a public registry server or a private endpoint, mcp-spec-check ensures your infrastructure stays ahead of the curve as the ecosystem transitions to the latest protocol standards.
Is your remote MCP server ready for the 2026-07-28 MCP spec release? Find out in 30 seconds.
- namnnumbr
That's a misleading title - of course no existing MCP server is going to be compliant with a spec that has not yet been released, and obviously no server is going to incorporate substantial, breaking changes when the clients themselves don't support the spec...
- jeroenhd
I have to give it to the vibe coding industry, I didn't think one could reinvent the wheel quicker and more often than frontend JavaScript programmers, but they're pulling it off!
I can't really tell why you would need to support the newer spec. It's mentioned that old stuff will work for at least a year after the new spec has been released, but I'm not so clear on what exactly will break. Is there some kind of phase out plan that the AI players have agreed upon for protocol versions will support for how long? Who is making these promises?
More importantly, I see a whole bunch of changes in headers and routing and whatnot on the MCP side itself, but I'm not really seeing what the advantages of the new spec are to either LLM users or MCP server resellers. Why consider upgrading in the first place?
- parhamn
"OAuth 2.0 Client ID Metadata Document (CIMD)" is a big one. As an agent-provider, prereigstering client IDs for a bunch of different services and going through each ones special hoops for org validation sucks.