{"version":"2.1.315","anchor":"mcp-http-connect-probe-and-403-proxy-retry-changes","canonical_anchor":"mcp-http-connect-probe-and-403-proxy-retry-changes","heading":"MCP reconnects behind a proxy retry only after a 403 refusal","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/mcp-http-connect-probe-and-403-proxy-retry-changes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### MCP reconnects behind a proxy retry only after a 403 refusal\n\nClaude Code now retries an MCP connection through a proxy only when the proxy refused with a 403, and runs its test less often\n\n**Unclear.** It is not clear when the new check allows the test connection to run.\n\n**What**\n\nMCP servers are add-ons that give Claude extra tools. Several things changed about how Claude Code connects to MCP servers over the web:\n\n- the test connection made first now runs only when an extra check passes\n\n- a retry happens only when the proxy refused the connection with a 403 status\n\n- a server already in the retry list is skipped and not dialled again\n\n**Why**\n\nThis changes how MCP servers reconnect when you work behind a proxy.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}