{"version":"2.1.224","anchor":"mcp-telemetry-identifies-servers-by-a-hash-not-the-base-url","canonical_anchor":"mcp-telemetry-identifies-servers-by-a-hash-not-the-base-url","heading":"MCP telemetry identifies servers by a hash, not the base URL","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/mcp-telemetry-identifies-servers-by-a-hash-not-the-base-url","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### MCP telemetry identifies servers by a hash, not the base URL\n\nMCP telemetry identifies servers by a hash rather than their raw URL.\n\n**What**\n\nThe helper that tagged MCP events with a server's base URL was replaced, in both of its copies, by one that also carries a hashed server key. Server identity in telemetry no longer depends on the raw URL.\n\n**Details**\n\n- The hash is attached to `tengu_mcp_listen_reopen` events and is the preferred key for per-server rate limiting when forwarding logs, with the base URL used only as a fallback.\n\n**Evidence**\n\n`mcpServerKeyHash`\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}