{"version":"2.1.318","anchor":"mcp-connection-failures-carry-a-notforwarded-message","canonical_anchor":"mcp-connection-failures-carry-a-notforwarded-message","heading":"Failed MCP connections can carry a message about the server address not being forwarded","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/mcp-connection-failures-carry-a-notforwarded-message","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Failed MCP connections can carry a message about the server address not being forwarded\n\nWhen connecting to a URL-based MCP server fails, the failure can now include a message saying the address was not forwarded\n\n**Unclear.** It is not clear whether this message is shown to you or only recorded.\n\n**What**\n\nWhen a connection to an MCP server that is reached by a web address fails, the failure result can now include an extra message saying the address was not forwarded. The same message is recorded in the usage data Claude Code reports. A request timeout is still treated as a connection timeout, as before.\n\n**Why**\n\nThis may let Claude Code explain a failure caused by a server address that was not passed through, rather than showing a plain connection error.\n\n- Flag `tengu_mcp_connect_timeout_retry`: Not enough to say (read for one account on one subscription tier against v2.1.318; this account: no value returned, anonymous baseline: no value returned, compiled default: on) 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: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}