{"version":"2.1.280","anchor":"new-cleanup-pass-for-an-mcp-discovery-verdicts-cache-file","canonical_anchor":"new-cleanup-pass-for-an-mcp-discovery-verdicts-cache-file","heading":"MCP server 'discover' probe results now cached to disk","tier":"internal","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-cleanup-pass-for-an-mcp-discovery-verdicts-cache-file","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### MCP server 'discover' probe results now cached to disk\n\nClaude Code now remembers for 24 hours which MCP servers already passed a protocol discovery probe, instead of re-checking every time\n\n**What**\n\n- claude.ai (`claudeai-proxy`) MCP connectors now remember, per server, whether a `server\/discover` probe already succeeded with the modern protocol, and skip re-probing for 24 hours.\n\n- These verdicts are persisted to a `mcp-discover-verdicts.json` state file (or, when a plugin filesystem sandbox is active, via a virtual state store), read and written through a serialized write chain.\n\n- A retention\/cleanup sweep now also prunes this file periodically.\n\n**Why** Caching the discovery result avoids re-probing the same MCP server's protocol support on every connection, while the periodic cleanup keeps the cache file from growing unbounded.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}