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.234 ·

MCP failures are sorted into a cause taxonomy for reporting

MCP failures are now sorted into causes like server down, login problem or bad config for reporting.

Under the hood Internal Changes
JSON All of v2.1.234
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
MCPArea: what it touches
Internal ChangesKind: in v2.1.234,
Internal ChangesSection of the release
What

Failures from MCP servers are now classified as downstream_error, downstream_unreachable, user_auth, user_config or other and attached to tool-error telemetry, so it is possible to tell a server that is down from a login or config problem. Nothing you see changes.

Details
  • Classification uses error classes, JSON-RPC and HTTP codes, and a curated set of network error codes including ECONNREFUSED, ERR_PROXY_TUNNEL and ESOCKETTIMEDOUT, following up to four chained causes.
  • The classification is also attached to "MCP server is not connected" and MCP tool timeout errors.
  • MCP connect telemetry gained flags for a suppressed listen and a denylisted negotiation.
Evidence

downstream_unreachable, mcpErrorSource

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.234 →

Feedback