{"version":"2.1.224","anchor":"mcp-version-mismatch-is-reported-before-it-throws","canonical_anchor":"mcp-version-mismatch-is-reported-before-it-throws","heading":"MCP version mismatch is reported before it throws","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/mcp-version-mismatch-is-reported-before-it-throws","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### MCP version mismatch is reported before it throws\n\nMCP version mismatches are reported to telemetry before the same error is raised.\n\n**What**\n\nThe check that the loaded MCP client module matches the MCP version Claude Code expects now reports the expected and observed versions to telemetry before raising the same error as before.\n\n**Evidence**\n\n`MCP runtime accessor tripwire: resolved generation is v2 but the loaded client module does not carry MCP_TREE_ID v2`\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}