Under the hood
MCP telemetry for rejected cached listings now records where the cached data came from
What
The 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.
Why
This 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.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Whether the `tengu_mcp_listing_prior_rejected` gate is enabled for any accounts is unknown; it has not been read.