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 capability probe no longer hangs on a bad reply

An MCP server replying badly to the capability probe no longer hangs your connection.

You'll notice Bug Fixes
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
Bug FixesKind: in v2.1.232,
Bug FixesSection of the release
What

When probing an HTTP MCP server for discovery support, a reply carrying the wrong request id or one that fails to decode now resolves cleanly and the server is treated as predating the discovery protocol, instead of hanging or throwing.

Details
  • Outcomes are reported as id-mismatch or malformed; the synthesised errors are named McpProbeIdMismatchError and McpProbeMalformedReplyError.
  • Decode failures cover both malformed JSON and schema validation failures.
  • Quoted values in the errors are cut at roughly 200 characters with a … [truncated] marker.
  • A stream ending early is now distinguished from a send failure via a dedicated stream-end callback.
Evidence

McpProbeIdMismatchError

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