{"version":"2.1.259","anchor":"new-telemetry-events-for-mcp-listing-races-and-model-catalog","canonical_anchor":"new-telemetry-events-for-mcp-listing-races-and-model-catalog","heading":"New telemetry events for MCP listing races and model-catalog comparisons","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259\/e\/new-telemetry-events-for-mcp-listing-races-and-model-catalog","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259","markdown":"### New telemetry events for MCP listing races and model-catalog comparisons\n\nTwo telemetry events were allowlisted, one for rejected MCP tool listings and one comparing served model catalogs.\n\nTwo telemetry events are now allowlisted: `tengu_mcp_listing_prior_rejected`, fired when an MCP tool listing response is rejected because a newer one already arrived, and a second event for comparing served model catalogs.\n\n- Area: MCP\n- Names: `tengu_mcp_listing_prior_rejected`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}