{"version":"2.1.221","anchor":"mcp-connection-failure-telemetry-normalizes-the-error-code","canonical_anchor":"mcp-connection-failure-telemetry-normalizes-the-error-code","heading":"MCP connection-failure telemetry normalizes the error code","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/mcp-connection-failure-telemetry-normalizes-the-error-code","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### MCP connection-failure telemetry normalizes the error code\n\nMCP failure codes are now cleaned up before reporting, so odd server values don't leak through.\n\n**What**\n\nThe error code attached to MCP connection failures is now classified before being reported, so arbitrary values from a server do not reach telemetry verbatim.\n\n**Details**\n\n- Emits `missing` when there is no code, the numeric value when it is an integer, a known code from an allow-list, or `other` as the fallback.\n- Applies to every `tengu_mcp_server_connection_failed` report; no gate.\n\n**Evidence**\n\n`tengu_mcp_server_connection_failed`\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}