How often remote MCP servers change their tools
A monthly report of how many remote MCP servers alalanet reads changed their tools/list, by kind: tools added, redefined (same name, new definition) and removed. Each edition is signed into the transparency log (kind 4323), and every figure but one is a count of a published record of signed changes.
Editions
No edition yet. Each month's edition is signed on the first day of the next month (UTC).
All editions: GET /v1/reports/tools. The last 7 days, unsigned: /research/tool-drift.
Method
A server is on record in a month when one of its tool sets was first read before the month's end and last read at or after its start, as the cited daily file of tool-set digests (kind 4313) lists them, or when a change of its set was signed in the month. A change is a statement of kind 4305 created in the month (UTC): alalanet read a tool set other than the one it held, a set is the digest of every tool's name, title, annotations.title, description, input and output schema and annotation hints. Its kinds are read from the signed summary, each label once and in the order alalanet writes them: added (a tool name the set before did not have), removed (a tool name the new set does not have), redefined (the summary's "changed": a tool of the same name defined otherwise), gained authority (a tool of the same name lost readOnlyHint or gained destructiveHint or openWorldHint); one change can be of several kinds. A lapse is a statement to the empty set (digest e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855): the server answered tools/list at two scheduled reads in a row, six hours or more apart, and alalanet got no set from either. It is signed as every tool removed, but no set was read: it is counted as a lapse, not as a change or a removal, and a server whose only statements are lapses, or lapses and its set coming back, did not change. A set coming back after a lapse is signed (restored) and not counted as a change; a different set after a lapse is a change, described against the set before the lapse. Servers changed: servers with at least one change. Changes: the statements that are changes; one server can sign many (each read that finds a new set signs one, live checks included), so the largest server's share of them is given. Counted from: the latest of the month's start, 2026-11-10 00:00 UTC (when alalanet's first read of every server it listed was done) and 23 hours (one read cycle) after the cited file's earliest first read, so that the servers of the watch's first reads are not taken for new ones. Appeared: its first set was first read at or after that time. Gone: its latest read of any set, as the snapshot lists it, is more than three days before the month's end. Whole month: on record, neither appeared nor gone. Every figure but the opted-out one is counted from the record, one line per server with its signed changes, whose sha256 this edition signs; the command alalanetd verify -tools-rate recounts it.