{"version":"2.1.280","anchor":"mcp-connect-failure-telemetry-now-includes-an-extra-field-vi","canonical_anchor":"mcp-connect-failure-telemetry-now-includes-an-extra-field-vi","heading":"MCP connect failure telemetry now includes an extra field via Mae(n)","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/mcp-connect-failure-telemetry-now-includes-an-extra-field-vi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### MCP connect failure telemetry now includes an extra field via Mae(n)\n\nMCP connect-failure telemetry now includes an extra data field\n\n**Unclear.** What data the added field actually carries is not specified in the evidence.\n\n**What**\n\nWhen a connection to an MCP server (a way Claude Code connects to external tools and data sources) fails, the telemetry events sent for it (`mcp_connect_failed`, `mcp_connect`) now include an additional set of fields drawn from a new source, alongside the fields already collected.\n\n**Why**\n\nThis gives more detail to diagnose why MCP connections fail, though the finding does not specify what the new fields contain.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}