Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.224 Home All releases ←olderv2.1.223 v2.1.225newer→
Claude Code v2.1.224

MCP events forwarded to Datadog, with identifying fields removed and a per-server cap

Under the hood
Useful2 Signal2
Telemetry

MCP events are forwarded for logging with identifying fields stripped, and skipped entirely if analytics are off.

What

MCP events are now admitted to log forwarding, and every payload has its identifying fields deleted before send. Forwarding is skipped entirely when analytics are disabled.

Details
  • Newly allowed: tengu_mcp_degraded, tengu_mcp_list_changed, tengu_mcp_listen_reopen, tengu_mcp_sdk_generation, tengu_mcp_server_connection_failed, tengu_mcp_server_connection_succeeded, tengu_mcp_tripwire.
  • Stripped fields include the server name, base URL, hashed server key, attribution hashes, hashed error details and a server digest.
  • Five of the MCP events are capped per event-and-server pair at 10 per 60 seconds, tracked over at most 200 keys; the number of suppressed events rides along on the next one that gets through as droppedSinceLastForward.
Evidence

PEER_RATE_BOUND_EVENTS

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