Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
MCPArea: what it touches
Internal ChangesKind: in v2.1.271,
Internal ChangesSection of the release
What
When an MCP (Model Context Protocol) server sends repeated list_changed notifications that its tool list has changed, a new scheduler now coalesces rapid successive notifications into a single refetch instead of triggering one refetch per notification. If a refetch fails, the wait before the next attempt doubles, up to a capped maximum.
Why
This avoids hammering an MCP server with repeated refetch calls when it sends a burst of change notifications, and backs off automatically if refetching keeps failing.
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed sustained high CPU usage and repeated tool-list requests when an MCP server sends list_changed notifications in a tight loop
