Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.232 ·

MCP servers that reply badly to the version probe now fall back to legacy instead of failing

MCP servers that reply oddly to the version probe now fall back to legacy instead of failing.

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

When connecting to an MCP server, Claude Code sends a server/discover probe to work out which protocol version to use. It previously handled only a proper response, a send error, a closed connection or a timeout. Three more bad-reply shapes are now recognised and all three are treated as evidence the server is an older one, so the connection falls back to the legacy path rather than failing negotiation outright.

Details
  • New outcomes: id-mismatch (the reply does not echo the request id, seen with HTTP transports), malformed (the reply fails JSON-RPC decoding) and stream-end (the request stream ends with no reply at all).
  • Named errors for these cases are passed to the transport's error handler.
Evidence

server/discover probe reply did not echo the request id (expected

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.232 →

Feedback