{"version":"2.1.280","anchor":"mcp-claudeai-proxy-discover-projection-now-remembers-a-le","canonical_anchor":"mcp-claudeai-proxy-discover-projection-now-remembers-a-le","heading":"MCP claude.ai-proxy connections cache legacy-peer discovery results","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/mcp-claudeai-proxy-discover-projection-now-remembers-a-le","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### MCP claude.ai-proxy connections cache legacy-peer discovery results\n\nMCP connections to claude.ai-proxy servers now remember when a peer needs legacy discovery and skip repeat probes\n\n**What**\n\n- A new async check probes whether a `claudeai-proxy` type MCP (Model Context Protocol, the way Claude Code talks to external tool servers) connection needs a legacy-discovery fallback. It skips stateless connections and ones already marked `discoverSupport: 'supported'`, and caches ids already found to have 'burned' listing\/discover priors.\n\n- The connection logic gains a `remembered_legacy` negotiation-mode outcome and a matching log line: once an earlier probe on a connector has found a legacy (pre-modern) peer, later connects skip the server\/discover round trip entirely instead of re-checking the cached `\/v1\/mcp_servers` projection every time.\n\n**Why**\n\nThis avoids repeating the same discovery round trip on every connection to an older MCP server reached through claude.ai-proxy, reducing unnecessary network calls.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}