{"version":"2.1.232","anchor":"mcp-version-negotiation-recovers-from-probe-timeouts","canonical_anchor":"mcp-version-negotiation-recovers-from-probe-timeouts","heading":"MCP version negotiation recovers from probe timeouts","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/mcp-version-negotiation-recovers-from-probe-timeouts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### MCP version negotiation recovers from probe timeouts\n\nAn MCP probe timeout now retries on the older protocol instead of failing the connection.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- 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.\n- 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.\n\n**Evidence**\n\n`era probe classified the server legacy in-SDK`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}