{"version":"2.1.246","anchor":"third-party-mcp-server-and-tool-names-are-replaced-with-a-pl","canonical_anchor":"third-party-mcp-server-and-tool-names-are-replaced-with-a-pl","heading":"Third-party MCP server and tool names are replaced with a placeholder in telemetry","tier":"notice","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/third-party-mcp-server-and-tool-names-are-replaced-with-a-pl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Third-party MCP server and tool names are replaced with a placeholder in telemetry\n\nMCP servers you added yourself are reported as \"custom\" in usage data, with tool names withheld.\n\n**What**\n\nWhen a tool call from an MCP server is attributed in usage reporting, the server name is now sent as the literal `\"custom\"` unless that server is on a per-session list of servers marked as first-party. The tool name is withheld the same way. Servers you add yourself are therefore no longer named in reporting.\n\n**Details**\n\n- The list is filled in at tool-call time and only when a first-party marker is present on the call, so there is no setting to opt a server in or out.\n- Plugin loading now records which marketplace each plugin came from, keyed by name and marketplace, with a counter that discards registrations left over from a previous load.\n\n**Evidence**\n\n`loggableMcpServers`\n\n- Area: Telemetry\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}