Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.318 ·

MCP tools and their results are now labelled with where they came from

Tools from MCP servers and their output are now marked as unverified, MCP-owned content when sent to the model, with the server address where safe

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

Unclear Which setting turns this on, and whether it is on by default, is not clear.

What

MCP servers are outside programs that give Claude extra tools. Claude Code now attaches a provenance label, ownership_metadata, to these tools and to their results before sending them to Anthropic's API.

  • Each MCP server is classed as configured (set up by you) or connector.
  • The label reads {verified:false, owner:'mcp', server_url?}: the content is unverified, owned by an MCP server, and may include the server's address.
  • Connector addresses are hidden unless known to be safe.
  • If the API refuses a server_url, Claude Code logs "[tool-provenance] the API refused a server_url; marking tools without addresses and retrying" and sends again without addresses.
  • The feature uses a beta flag and an api_tool_provenance marker. In cloud sessions it also records the MCP addresses present at launch, using CLAUDE_CODE_REMOTE and CLAUDE_CODE_ENVIRONMENT_KIND.
  • The tool sanitizer strips ownership_metadata from tool definitions in another path that sends tools to the API.
  • Separately, WebFetch's output gains an optional internal citable field, and several new internal diagnostic names were added.

Why

The model can now tell that output from an MCP tool is unverified, third-party content rather than something Claude Code itself produced. This changes what each request carries.

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 setting turns this on, and whether it is on by default, is not clear.

See this entry in the whole of v2.1.318 →

Feedback