Agent supply-chain evidence
MCP tool descriptions and schemas can change silently after you approve them, the rug pull. Security tools can block it in your own pipeline, but when an incident lands, you need what none of them keep: a neutral, dated record of what the server was publishing that day. BotWitness records the MCP registry and live tools/list manifests daily, hashed, timestamped, tamper-evident.
The gap
The MCP registry shows a server's current entry; a live server shows its current tools. There is no spec-level change history for tool manifests: an entry that is edited, moderated away, or re-pointed simply overwrites its past. After an agent incident, "what did the tool's description say three Tuesdays ago?" is unanswerable, unless someone was recording it that day. We are.
How it works
01 · Record
Every day we sweep the official MCP registry (one canonical-JSON record per server) and speak the protocol to remote servers, initialize → tools/list, capturing each tool's name, description, and input schema exactly as served. An auth wall or an error is recorded as a fact, not skipped.
02 · Seal
Manifests are canonicalized (so formatting isn't a "change"), SHA-256 hashed, and sealed into a daily Merkle digest with an independent RFC-3161 timestamp on the root, continuous monitoring you can prove.
03 · Prove
Retrieve the manifest a server published on any recorded date, or the diff between two dates: the exact description edit, the new parameter, the tool that appeared or vanished.
Who needs it
Your agent leaked data through a tool call. Which description did the model actually see that day? A dated third-party manifest turns guesswork into a timeline, and attributes the change to a date.
Rug-pull detectors need trustworthy baselines. A neutral archive of manifest history is the ground truth your customers can verify against, and the feed your product can build on.
Approve-time governance meets run-time drift. Show auditors what every third-party server in your stack was publishing on any day in scope.
Live now
Registry coverage and per-server manifest history are queryable now.
« search watched registry entries » curl "https://bot-witness.com/watch?kind=mcp&q=github" « the dated tools/list manifest history of one live server » curl "https://bot-witness.com/watch/history?kind=mcp-tools&key=<server-name>"
Early access
A record like this only exists from the day someone starts keeping it. Ours is running. Tell us which servers matter to you and we'll make sure they're covered.
