{"version":"2.1.319","anchor":"tengu-snug-mist-enabled-gate-removed-from-http-mcp-terminal","canonical_anchor":"tengu-snug-mist-enabled-gate-removed-from-http-mcp-terminal","heading":"Some web-based MCP servers now always survive repeated fatal errors","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/tengu-snug-mist-enabled-gate-removed-from-http-mcp-terminal","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Some web-based MCP servers now always survive repeated fatal errors\n\nThe three-error disconnect exemption for some HTTP MCP servers no longer depends on a switch and applies whenever the URL check matches\n\n**Unclear.** It is not clear which server addresses pass the URL check, so which MCP servers are affected.\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. Claude Code closes a connection after three fatal connection errors in a row. For some servers reached over the web, as type `http`, those errors do not count toward that limit.\n\nThis exemption used to apply only when a server-controlled switch, `tengu_snug_mist_enabled`, was on. That switch is gone. The exemption now applies to every `http` server whose address passes Claude Code's URL check.\n\n**Why**\n\nThe reconnect behaviour that was held back is now live for matching servers. Their connections are no longer closed after three fatal errors.\n\n- Flag `tengu_snug_mist_enabled`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.319; this account: on, anonymous baseline: on, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}