Some MCP server discovery calls are answered from cache, avoiding an extra round trip.
What's wrong with this entry?
The stateless claudeai-proxy path, which already short-circuited initialize from a cached projection, now does the same for server/discover.
- It either replies with the cached result or synthesises a JSON-RPC "Method not found" error for servers known to be legacy, without a round trip.
- Both cases are logged.
Stateless claudeai-proxy — server/discover resolved locally as legacy (method-not-found), server/discover resolved locally as legacy (method-not-found)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.