{"version":"2.1.311","anchor":"mcp-proxy-fallback-only-applies-ca-bundle-when-a-proxy-is-ch","canonical_anchor":"mcp-proxy-fallback-only-applies-ca-bundle-when-a-proxy-is-ch","heading":"MCP connections read SSL_CERT_FILE only when they actually use a proxy","tier":"notice","area":"MCP","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/mcp-proxy-fallback-only-applies-ca-bundle-when-a-proxy-is-ch","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### MCP connections read SSL_CERT_FILE only when they actually use a proxy\n\nMCP connections now read the SSL_CERT_FILE certificate bundle only when a proxy applies, not whenever HTTPS_PROXY is set\n\n**What**\n\nMCP servers are outside tools Claude Code connects to. When it reaches one through a proxy (a go-between server set with `HTTPS_PROXY`), it can use a file of trusted certificates named by `SSL_CERT_FILE`.\n\nClaude Code now first works out whether a proxy applies to the address. It reads the `SSL_CERT_FILE` bundle only if one does. Before, it read the file whenever `HTTPS_PROXY` was set.\n\n**Why**\n\nAddresses you exclude from the proxy with `NO_PROXY` no longer cause the certificate file to be read.\n\n- Area: MCP\n- Names: `SSL_CERT_FILE`, `HTTPS_PROXY`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: yes"}