{"version":"2.1.221","anchor":"cached-mcp-initialize-responses-checked-against-supported-pr","canonical_anchor":"cached-mcp-initialize-responses-checked-against-supported-pr","heading":"Cached MCP initialize responses checked against supported protocol versions","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/cached-mcp-initialize-responses-checked-against-supported-pr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Cached MCP initialize responses checked against supported protocol versions\n\nCached MCP handshakes with an unsupported protocol version are now thrown away and redone.\n\n**What**\n\nA stored initialize response for a claudeai-proxy server is now discarded when its protocol version is unsupported, not only when it fails schema validation.\n\n**Details**\n\n- Applies to `cachedInitResponse` on the claudeai-proxy path.\n- Previously only an InitializeResult validation failure caused a discard; now an out-of-range `protocolVersion` does too.\n- Either failure logs and falls back to a real initialize round trip.\n\n**Evidence**\n\n`falling back to real initialize`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}