{"version":"2.1.300","anchor":"mcp-frame-relay-more-specific-failure-reasons-and-an-advert","canonical_anchor":"mcp-frame-relay-more-specific-failure-reasons-and-an-advert","heading":"Relayed MCP connections give more specific failure reasons","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/mcp-frame-relay-more-specific-failure-reasons-and-an-advert","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Relayed MCP connections give more specific failure reasons\n\nRelayed MCP connections now wait a limited time for a server's offer and report more specific reasons when they cannot connect\n\n**What**\n\nMCP (Model Context Protocol) is how Claude Code connects to outside tool servers. When Claude Code relays MCP traffic, it now waits a limited time for the server's offer and reports a late offer as its own reason. Before, the reasons were limited to cannot carry, no offer and narrower. Now:\n\n- a refusal is reported with a more specific sub-reason\n\n- when a restriction is applied, its status is included\n\n**Why**\n\nThis mostly gives better reporting on why a relayed connection failed, and it also changes timing a little because Claude Code now waits for a late offer.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}