{"version":"2.1.267","anchor":"mcp-remote-tool-registry-now-tracks-passthrough-tools-and-a","canonical_anchor":"mcp-remote-tool-registry-now-tracks-passthrough-tools-and-a","heading":"MCP remote-tool registry now tracks passthrough tools and a generation counter","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/mcp-remote-tool-registry-now-tracks-passthrough-tools-and-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### MCP remote-tool registry now tracks passthrough tools and a generation counter\n\nMCP remote-tool registry now tracks individual passthrough tools and a change counter\n\n**What**\n\nThe internal registry that tracks tools announced by remote MCP (Model Context Protocol) servers now keeps its list of \"passthrough\" tools (tools forwarded through rather than wrapped) as a full map instead of just a count. It also now:\n\n- reports `passthroughAdopted` in the results when tools are announced\n\n- exposes a `passthroughTools` map of tool name to local name via `hostsForTable()`\n\n- adds a `generation()` counter that increases every time something meaningful changes, such as a tool being accepted, cleared, or its status changing\n\n**Why**\n\nTracking individual passthrough tools and a generation counter, rather than just a count, lets other parts of Claude Code detect exactly what changed and when, which matters for keeping remote tool state in sync.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}