{"version":"2.1.219","anchor":"proto-rejected-as-an-mcp-server-name","canonical_anchor":"proto-rejected-as-an-mcp-server-name","heading":"\"__proto__\" rejected as an MCP server name","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/proto-rejected-as-an-mcp-server-name","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### \"__proto__\" rejected as an MCP server name\n\nAn MCP server literally named __proto__ now warns you instead of silently loading nothing.\n\n**What**\n\nAn MCP config with a literal `__proto__` key under mcpServers used to be swallowed by prototype semantics, loading nothing and saying nothing. It is now detected and reported.\n\n**Details**\n\n- Surfaces as a validation warning with skipReason `reserved_name`, which feeds the new skipped-server reporting\n- Warning messages and suggestions are now passed through a sanitizer before being pushed\n\n**Evidence**\n\n`\"__proto__\" is a reserved MCP server name and was not loaded`\n\n- Area: MCP\n- Names: `mcpServers`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}