{"version":"2.1.268","anchor":"mcp-tool-telemetry-now-sends-hashed-servertool-names-even-w","canonical_anchor":"mcp-tool-telemetry-now-sends-hashed-servertool-names-even-w","heading":"MCP tool telemetry now sends hashed server\/tool names even without consent","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/mcp-tool-telemetry-now-sends-hashed-servertool-names-even-w","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### MCP tool telemetry now sends hashed server\/tool names even without consent\n\nMCP tool telemetry now sends hashed server and tool names even when full-name consent is withheld\n\n**What**\n\nThe function that builds the MCP server and tool name fields for telemetry previously sent nothing at all when the user hadn't consented to sharing full names. Now, in that same no-consent case, it sends hashed versions of the server name and tool name (`mcpServerNameHash` and `mcpToolNameHash`) instead of omitting the fields entirely.\n\n**Why**\n\nThis lets Claude Code's telemetry distinguish and count distinct MCP servers and tools in aggregate even without consent to see their actual names, since a hash reveals usage patterns without exposing the original name.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}