{"version":"2.1.247","anchor":"mcp-servers-that-fail-to-connect-are-now-reported-by-default","canonical_anchor":"mcp-servers-that-fail-to-connect-are-now-reported-by-default","heading":"MCP servers that fail to connect are now reported by default","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/mcp-servers-that-fail-to-connect-are-now-reported-by-default","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### MCP servers that fail to connect are now reported by default\n\nMCP servers that fail to connect are now reported to you by default.\n\n**What**\n\nThe switch controlling whether MCP servers that failed to connect are shown to you now defaults to on instead of off, so unless the server says otherwise you will see connection failures reported.\n\n**Details**\n\n- The gate is `tengu_surface_failed_mcp_servers`; only its local fallback changed, from false to true.\n- A server-supplied value still wins over the fallback.\n\n**Evidence**\n\n`tengu_surface_failed_mcp_servers`\n\n- Flag `tengu_surface_failed_mcp_servers`: Not enough to say (read for one account on one subscription tier against v2.1.247; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read)\n- Area: MCP\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}