All news
aiproductregulationcybersecurity

Only 1 of 4,356 MCP Servers Ready for July 2026 Spec

13 Jul 2026

A scan of the official Model Context Protocol (MCP) registry, conducted on 2026-07-12, found that just 1 of 4,356 reachable servers passes all three required readiness checks for the upcoming 2026-07-28 spec. With the deadline just over two weeks away at the time of the scan, the finding suggests the vast majority of the MCP ecosystem may not be prepared for what's described as the largest revision to the protocol since launch.

The numbers

  • 7,850 total remote MCP servers are registered in the official registry.
  • 4,356 of those were reachable during the scan.
  • 1 reachable server passes all three required checks for the new spec.
  • 90.8% of reachable servers were reported as not ready for the 2026-07-28 spec.

Sources differ on the exact scale of non-readiness: the "1 of 4,356" figure implies roughly 99.98% non-compliance, while the same source separately reports a 90.8% non-readiness rate. The report notes these two figures are inconsistent, and it's unclear whether they reflect different readiness thresholds or measurement criteria.

What's changing in the spec

The 2026-07-28 release makes several structural changes to MCP:

  • The initialize handshake and Mcp-Session-Id are removed in favor of a stateless core.
  • Mcp-Method and Mcp-Name become required routing headers.
  • SSE elicitation is replaced by Multi Round-Trip Requests.
  • Deprecated features will remain supported for at least 12 months after release, giving teams a grace period to migrate.

A tool called mcp-spec-check is available via npx for teams that want to self-assess their server's readiness ahead of the deadline.

The risks

Several risks stem directly from these changes:

  • Widespread non-compliance could disrupt MCP server availability or functionality once the spec takes effect.
  • Removing the initialize handshake and Mcp-Session-Id may break integrations that depend on session-based state.
  • The new required headers could cause silent failures for servers that haven't been updated.
  • Startups relying on third-party MCP servers may face unexpected downtime if those providers aren't ready in time.

Why founders should care

For founders building products on top of MCP, this data points to a few likely scenarios worth planning around:

  • Given the reported readiness rates, it's plausible that a large share of MCP-dependent products could hit compatibility issues around July 28, 2026, whether from their own servers or third-party dependencies.
  • The scope of the revision — stateless core, new headers, new elicitation model — suggests migration could require meaningful engineering effort rather than a quick patch, especially for teams that leaned on session-based handshakes or SSE elicitation.
  • Because the source's own readiness figures conflict (1-in-4,356 vs. 90.8%), founders should treat aggregate numbers as directional rather than precise, and instead run their own servers through mcp-spec-check to get a definitive answer.
  • The 12-month deprecation window for legacy features may reduce the odds of an immediate hard break, giving some breathing room — but it likely won't eliminate the need to plan a migration path well before the buffer expires.

Where this leaves things unclear

The report doesn't specify what the three required checks actually test, nor does it detail how server operators should remediate issues before the deadline. The methodology behind "reachability" in the scan also isn't explained. Founders relying on MCP infrastructure may want to treat this scan as an early warning signal rather than a definitive audit, and verify their own compliance status directly.

Opportunities amid the disruption

Not all of the implications are negative. The mcp-spec-check tool offers a straightforward way for teams to self-assess before the deadline hits. And with the reported majority of the ecosystem seemingly unprepared, early movers who align with the stateless core and new header requirements now may be able to differentiate their MCP offering from competitors still catching up.

Sources