{"version":"2.1.271","anchor":"mcp-client-notification-handlers-wrapped-uniformly","canonical_anchor":"mcp-client-notification-handlers-wrapped-uniformly","heading":"MCP client notification handlers wrapped uniformly","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/mcp-client-notification-handlers-wrapped-uniformly","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### MCP client notification handlers wrapped uniformly\n\nMCP client notification handlers are now wrapped by a shared function before registration\n\n**Unclear.** The finding does not say what the shared wrapper actually does to the handlers.\n\n**What**\n\nInternally, the three handlers Claude Code registers for MCP (Model Context Protocol, the standard it uses to talk to external tool servers) notifications \u2014 for changes to a server's tools, prompts, and resources lists \u2014 are now all wrapped by the same helper function before being registered, instead of each being passed through directly.\n\n**Why**\n\nThis is an internal consistency change with no described effect on what these notifications do; it likely centralizes some shared handling logic across the three cases.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}