Follow Discord
Sweep 27 Oct 2026 · 19:04Z Build v2.1.312 531 read Stable v2.1.308 Latest v2.1.312 Next v2.1.312 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.311 ·

MCP results are checked differently and tool checks are built when needed

Some MCP results now skip a validation step, and per-tool output checks are prepared only when a tool needs them

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

Unclear Which MCP connections use the mcp-wire-codec format, and so skip the result check, is not stated.

What

Claude Code connects to outside tools through MCP, the Model Context Protocol. It has changed how it checks the replies those tools send back:

  • Replies from one particular message format, called mcp-wire-codec, now skip the step that checked each result against its expected structure. Before, every complete result was checked.
  • The check for each tool's output is now prepared only when that tool needs it, rather than for every tool at once. It is prepared for all tools when a structure definition contains "$id".
  • Incoming messages are now checked by simpler built-in structure checks.
Why

Listing tools can now cost less work. It could also change which badly formed replies are accepted from an MCP server.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhich MCP connections use the `mcp-wire-codec` format, and so skip the result check, is not stated.

See this entry in the whole of v2.1.311 →

Feedback