We’re launching Lyria 3.5 in Google Flow Music, with advances across musicality, lyrics, vocals, and creative control
deepmind.google·6d ago
AI Engineering
Hacker News·23d ago·5 min read
Show HN: Only 1 of 4,356 reachable MCP servers is ready for the 2026-07-28 spec
TL;DR
Only 1 out of 4,356 reachable MCP servers is prepared for the upcoming 2026-07-28 MCP specification release. A new tool, mcp-spec-check, evaluates server readiness by probing live endpoints without requiring code access.
✦ Why It Matters
Server operators should use mcp-spec-check today to assess their readiness for the upcoming MCP spec changes.
Key Takeaways
- Use mcp-spec-check to evaluate your server's readiness for the new MCP spec.
- Migrate to the stateless core to avoid losing support in the next year.
- Update your server configurations to comply with new routing header requirements.
- Stay informed about protocol changes to ensure your applications remain functional.
Full Summary
The 2026-07-28 MCP (Message Communication Protocol) release represents the most significant update since its inception, introducing a stateless core that eliminates the initialize handshake and Mcp-Session-Id. Key changes include mandatory Mcp-Method/Mcp-Name routing headers and the replacement of Server-Sent Events (SSE) with Multi Round-Trip Requests.
To assess server compliance with the new spec, the mcp-spec-check tool uses black-box probing to evaluate live endpoints, providing immediate feedback on readiness. Currently, only 1 in 4,356 reachable servers is ready for the new specification, indicating a substantial gap in adoption.
As SDKs and clients transition to the stateless core, servers that do not migrate risk losing support within a year. This situation necessitates prompt action from server operators to ensure continued functionality and compliance with the evolving protocol.