Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.280 ·

MCP claude.ai-proxy connections cache legacy-peer discovery results

MCP connections to claude.ai-proxy servers now remember when a peer needs legacy discovery and skip repeat probes

Group of 2 You'll notice Improvements
JSON All of v2.1.280
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
MCPArea: what it touches
ImprovementsKind: in v2.1.280,
ImprovementsSection of the release

What

  • 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.
  • 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.

Why

This avoids repeating the same discovery round trip on every connection to an older MCP server reached through claude.ai-proxy, reducing unnecessary network calls.

See this entry in the whole of v2.1.280 →

Feedback