Only one of 4,356 reachable MCP servers is currently ready for the July 28, 2026, specification [1].

This lack of preparation suggests a potential disruption in how Model Context Protocol servers interact as the target date approaches. If the vast majority of servers fail to meet the new specifications, it could lead to widespread compatibility issues across the ecosystem.

Roee Tsur shared the findings through a GitHub repository designed to check the readiness of these servers [2]. The analysis focused on reachable servers to determine how many have already implemented the necessary updates for the 2026-07-28 spec [3].

According to the data, 4,356 reachable MCP servers were evaluated [4]. Out of that total, only one server met the requirements [5].

"Only 1 of 4,356 reachable MCP servers is ready for the 2026-07-28 spec," Tsur said [6].

The gap between the current state of the network and the requirements for July 28 indicates that most developers have not yet updated their servers. This discrepancy highlights a critical window for implementation before the specification becomes the standard for the network.

“Only one of 4,356 reachable MCP servers is currently ready”

The stark contrast between the number of existing servers and those compliant with the new specification suggests that the industry is lagging behind the technical roadmap. This may force a choice for developers: either accelerate updates to avoid service interruptions on July 28 or risk a fragmented ecosystem where most servers are incompatible with the latest protocol standards.