{"version":"2.1.304","anchor":"mcp-requests-for-cli-owned-servers-fail-closed-when-the-bear","canonical_anchor":"mcp-requests-for-cli-owned-servers-fail-closed-when-the-bear","heading":"MCP requests now fail instead of going out without their login token","tier":"notice","area":"MCP","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/mcp-requests-for-cli-owned-servers-fail-closed-when-the-bear","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### MCP requests now fail instead of going out without their login token\n\nIf an MCP request's login token is withheld, the request now fails instead of being sent unauthenticated\n\n**What**\n\nMCP servers are outside programs that give Claude extra tools, using the Model Context Protocol. Requests to some of them carry a login token. When that token is withheld for a stated reason, the request now fails with an error. Before, it was sent without the token.\n\nSeparately, a session that takes its managed settings from your organization now refuses to add MCP servers, and says so with a message.\n\n**Why**\n\nThis is a security tightening: a request that should be signed in no longer goes out unsigned. It also means such MCP calls now fail visibly where they used to be sent anyway.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}