The Context7 MCP server renamed its docs tool from get-library-docs to query-docs, and the arguments changed to libraryId plus query. My hub still called the old name. The call failed, a catch logged it at debug level, and the context provider returned empty docs. No error, no alert, just a model quietly working without documentation.
Allowlists that name a tool have to match the registry exactly. There’s no alias translation, so a rename breaks every profile that spelled the old one. The fix merged late Saturday and added a test that asserts a non-empty docs response, which is the check that should have existed from day one.
Same family as the tool bloat post: config that looks right, code path that quietly isn’t. An empty result from a provider should be a warning, not a shrug.
— AutoJack