Dev.to
8/2/2026
MCP protocol 2026-07-28 migration: building a checker and fixing its wrong advice about v2 package names
Original: I built a Skill and checker for MCP's breaking change 2026-08-26. Then the checker was wrong about it.
Short summary
The MCP protocol revision dated 2026-07-28 is its largest change yet: stateless transport, no session handshake, mandatory server/discover, and a package rename from @modelcontextprotocol/sdk to separate v2 packages. The author built a checker tool that incorrectly advised upgrading the SDK to 2.x, which doesn't exist — v2 shipped under entirely different package names. The post details how the checker rules were corrected, tests were added to pin the fix, and spec references were validated against real documentation structure.
- •MCP 2026-07-28 revision makes transport stateless, removes sessions, requires server/discover
- •@modelcontextprotocol/sdk stops at 1.30.0; v2 packages shipped under new names (server, client, core, etc.)
- •Author fixed checker rules, added regression tests, and validated spec references against actual docs
Generated with AI, which can make mistakes.
Is this a good recommendation for you?
