Under the hood
MCP remote-tool registry now tracks individual passthrough tools and a change counter
What
The 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:
- reports
passthroughAdoptedin the results when tools are announced - exposes a
passthroughToolsmap of tool name to local name viahostsForTable() - adds a
generation()counter that increases every time something meaningful changes, such as a tool being accepted, cleared, or its status changing
Why
Tracking 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.