You'll notice
Useful2 Signal0
MCP servers announcing tool or prompt list changes will not cause Claude to refetch them.
What's wrong with this entry?
Anonymous. No account, no email.
What
Client construction and request-handler registration were reworked, and server list-changed notifications explicitly do not trigger refetching.
Details
- The Client is created with
jsonSchemaValidator, the negotiation config, and alistChangedblock settingautoRefresh: !1, debounceMs: 0with no-oponChangedfor tools, prompts and resources. - Request handlers are registered by method-name strings (
"roots/list","elicitation/create") rather than schema objects. - A set of recognised JSON Schema draft URIs, draft-04 through 2019-09 plus the unversioned ones, is now kept in the module.
Evidence
jsonSchemaValidator
Strings lifted out of the shipped bundle, so the claim above can be checked against them.