You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
MCPArea: what it touches
Bug FixesKind: in v2.1.232,
What probably matters to youSection of the release
What
When auto-negotiating an MCP server's protocol version, a discovery probe that times out is now detected and the connection retried against the pinned legacy protocol within the remaining time budget, instead of the connect failing outright.
Details
If that legacy retry fails for an unrelated reason, the original timeout classification is kept so the connect stays eligible for the normal retry ladder.
When the probe decides a server is legacy from an id mismatch, malformed response or early stream end, the reason is now recorded and written to the MCP debug log.
Evidence
era probe classified the server legacy in-SDK
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
