{"version":"2.1.315","anchor":"mcp-requests-refuse-when-tls-ca-settings-changed-after-conne","canonical_anchor":"mcp-requests-refuse-when-tls-ca-settings-changed-after-conne","heading":"Hosted-worker MCP requests stop when trusted certificates no longer match","tier":"notice","area":"MCP","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/mcp-requests-refuse-when-tls-ca-settings-changed-after-conne","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Hosted-worker MCP requests stop when trusted certificates no longer match\n\nIn a hosted worker, an MCP request whose trusted CA certificates share none with Claude Code's current list is now refused with an error\n\n**What**\n\nMCP servers are add-ons that give Claude extra tools. Connections to them are encrypted with TLS. CA certificates are the authorities trusted to vouch that a server is genuine.\n\nThe code that sends requests to MCP servers was rewritten for `hosted_worker` mode. It now compares the request's list of trusted CA certificates with the list Claude Code is using now:\n\n- If the two lists have nothing in common, the request is not sent. Instead there is an error, \"MCP request not sent: its list of trusted CA certificates has nothing in common with the one Claude Code uses now\", which tells you to reconnect the server.\n\n- If they share some certificates, the request is narrowed to the shared ones.\n\n**Why**\n\nThis only affects hosted workers whose TLS settings change during a session. When the trusted certificates no longer overlap, you get an error straight away that tells you to reconnect the server.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}