July 12, 2026
One server to rule them all?
Show HN: Only 1 of 4,356 reachable MCP servers is ready for the 2026-07-28 spec
Only 1 server passed the big test, and commenters instantly started fighting about what that even means
TLDR: A new scan found only 1 of 4,356 public MCP servers fully ready for a big upcoming rules update, though the author says there’s no doomsday deadline. Commenters immediately split between “useful reality check” and “misleading scare headline,” with extra grumbling about confusing docs and login bureaucracy.
A tiny tool with a huge, chaotic number just dropped on Hacker News: out of 4,356 publicly reachable MCP servers, exactly one is fully ready for a major protocol update coming later this month. MCP is basically a way for apps and AI tools to talk to online services, and this upcoming change rewrites some of the rules so servers work in a simpler, more "stateless" way. The author jumped in fast to calm the panic, stressing that nothing explodes on release day and older ways will still work for at least a year. But the comments? Oh, they smelled blood.
The spiciest reaction was the brutal product-manager-style dunk: if something doesn’t work with 99.995% of the ecosystem, why would anyone touch it? Others accused the post title of being wildly misleading, arguing that of course almost nobody is ready for a spec that isn’t even officially out yet. One annoyed reader said they couldn’t even figure out which one lucky server passed, roasting the docs for repeating themselves. So the drama split neatly in two: is this a valuable early warning, or just a scary scoreboard posted before the race starts?
There was also some low-key industry pain in the thread, with one commenter groaning about the nightmare of registering IDs and handling sign-in bureaucracy across different services. In other words: beneath the stats flex, the real story is classic tech-comment-section energy — one part useful audit, one part semantic knife fight, one part paperwork trauma dump.
Key Points
- •mcp-spec-check is a black-box tool that probes remote MCP servers for readiness for the 2026-07-28 MCP specification.
- •The article says the 2026-07-28 MCP release removes the initialize handshake and session-based protocol behavior in favor of a stateless core, and requires routing headers on every request.
- •In a scan conducted on 2026-07-12, the author probed 7,850 remote servers in the official MCP registry and found 4,356 openly reachable servers.
- •Exactly 1 of the 4,356 openly reachable servers passed all three required readiness checks, while 90.8% were reported as not ready.
- •Readiness verdicts are based only on discover, routing-headers, and session-independence, while other checks are warning-only and the tool is validated against reference servers, public servers, and the official conformance suite.