{"version":"2.1.305","anchor":"mcp-transport-predicate-simplified","canonical_anchor":"mcp-transport-predicate-simplified","heading":"A check on MCP servers now looks only at the connection type","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/mcp-transport-predicate-simplified","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### A check on MCP servers now looks only at the connection type\n\nA check on MCP server settings now goes by connection type alone, true for `sse`, `http` and `ws` servers, instead of reading commands and URLs\n\n**Unclear.** It is not clear what this check controls.\n\n**What**\n\nMCP servers are outside tools Claude Code connects to. A check on their settings now answers yes for servers that connect over the network (`sse`, `http` and `ws`) and no for the rest, including local `stdio` servers. It no longer looks at the server's command, arguments, environment variables, URL or headers.\n\n**Why**\n\nWhatever this check controls now applies to every remote MCP server, whatever its other settings say.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}