{"version":"2.1.232","anchor":"mcp-servers-that-garble-the-version-probe-now-fall-back-to-t","canonical_anchor":"mcp-servers-that-garble-the-version-probe-now-fall-back-to-t","heading":"MCP servers that garble the version probe now fall back to the legacy protocol","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/mcp-servers-that-garble-the-version-probe-now-fall-back-to-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### MCP servers that garble the version probe now fall back to the legacy protocol\n\nGarbled MCP version-probe replies now fall back to legacy rather than erroring the connection.\n\n**What**\n\nWhen Claude Code probes an MCP server for its protocol version, a reply with a mismatched id, unparseable content, or a stream that ends early is now handled as a legacy server and the connection proceeds, instead of surfacing an error.\n\n**Evidence**\n\n`Connection closed during the version negotiation probe`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}