{"version":"2.1.248","anchor":"mcp-connection-failure-telemetry-records-where-the-auth-head","canonical_anchor":"mcp-connection-failure-telemetry-records-where-the-auth-head","heading":"MCP connection-failure telemetry records where the auth header came from","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/mcp-connection-failure-telemetry-records-where-the-auth-head","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### MCP connection-failure telemetry records where the auth header came from\n\nMCP connection failure reports now note when auth headers came from a credential helper.\n\n**What**\n\nFailure reports for sse, http and claudeai-proxy MCP transports now carry a field marking headers minted by a credential helper, alongside the existing user-header and CLI-bearer flags. It feeds the same classifier behind `tengu_mcp_server_connection_failed`. Unconditional.\n\n**Evidence**\n\n`helperMintsAuthHeader`\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}