{"version":"2.1.280","anchor":"mcp-listing-prior-rejected-telemetry-gains-a-priorsource-fie","canonical_anchor":"mcp-listing-prior-rejected-telemetry-gains-a-priorsource-fie","heading":"MCP listing-prior-rejected telemetry gains a priorSource field","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/mcp-listing-prior-rejected-telemetry-gains-a-priorsource-fie","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### MCP listing-prior-rejected telemetry gains a priorSource field\n\nMCP telemetry for rejected cached listings now records where the cached data came from\n\n**Unclear.** Whether the `tengu_mcp_listing_prior_rejected` gate is enabled for any accounts is unknown; it has not been read.\n\n**What**\n\nThe `tengu_mcp_listing_prior_rejected` telemetry event, which fires when a server rejects a connection built from a cached list of MCP tools\/servers, now also records a `priorSource` field alongside the existing `priorKind` and `reason` fields.\n\n**Why**\n\nThis gives more detail about where the stale cached data came from when a connection built from it gets rejected, which can help diagnose why a cached MCP listing went bad.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}