DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.
MCP telemetry identifies servers by a hash, not the base URL
Under the hood
Useful2Signal2
MCP
MCP telemetry identifies servers by a hash rather than their raw URL.
What's wrong with this entry?
Anonymous. No account, no email.
What
The 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.
Details
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.
Evidence
mcpServerKeyHash
Strings lifted out of the shipped bundle, so the claim above can be checked against them.