{"version":"2.1.221","anchor":"mcp-server-discover-answered-from-the-cached-projection-on-t","canonical_anchor":"mcp-server-discover-answered-from-the-cached-projection-on-t","heading":"MCP: server\/discover answered from the cached projection on the stateless proxy","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/mcp-server-discover-answered-from-the-cached-projection-on-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### MCP: server\/discover answered from the cached projection on the stateless proxy\n\nSome MCP server discovery calls are answered from cache, avoiding an extra round trip.\n\n**What**\n\nThe stateless claudeai-proxy path, which already short-circuited `initialize` from a cached projection, now does the same for `server\/discover`.\n\n**Details**\n\n- 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.\n- Both cases are logged.\n\n**Evidence**\n\n`Stateless claudeai-proxy \u2014 server\/discover resolved locally as legacy (method-not-found)`, `server\/discover resolved locally as legacy (method-not-found)`\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}