MCP server teleprompter added 8 declared tools, from 4 to 12
If your agent relies on this server, 200 % of its declared tools were added to its public list between 2026-08-20 and 2026-08-21. Here is exactly what our dated snapshots show, which tools were affected, and how to check it yourself.
The machine economy changes silently — and agents break when it does. We keep the dated record: what was declared, and when it changed. So you can see the change, and act before it breaks something you depend on.
Why changes like this matter
Agents are built against a server's declared list of tools. There is no versioning duty and no changelog requirement for these declarations — a server can change what it declares at any time, without notice. Calls to a tool that is no longer declared return an error, often with nothing surfacing it, in systems that run unattended. And without a dated register there is no way to establish afterwards what was declared, or when it changed. That is why this record exists.
An agent built against the older declaration may call tools that are no longer listed. Where tools were added instead, code written against the older list keeps working but does not see the new capability.
More on what this register is and why it exists: /about.
What we observed
| date we looked | what the server declared that day |
|---|---|
| 2026-08-18 | 2 tools declared (contract hash eb5c4ec1b0bf...) |
| 2026-08-19 | 2 tools declared (contract hash eb5c4ec1b0bf...) |
| 2026-08-20 | 4 tools declared (contract hash 8ccb7d25558d...) |
| 2026-08-21 | 12 tools declared (contract hash ef9df28e70ee...) |
| 2026-08-22 | 12 tools declared (contract hash ef9df28e70ee...) |
| 2026-08-23 | 12 tools declared (contract hash ef9df28e70ee...) |
What changed, exactly
These are the tool names the server itself declared on each date. 4 were declared on both.
Newly declared (8)
archive_planned_scriptscancel_scheduled_postedit_planned_scriptsget_planned_scriptslist_collectionslist_scheduled_postsreorder_planned_scriptsretry_scheduled_post
If you use this server
- Check whether your agent expects only the tools that were declared before.
- Re-derive today's declaration yourself at /verify.
- Check back, or follow the feed, for later dated observations of the same server.
For scale: across the ~16,000 MCP servers we track, about 12 % change their declared contract in a given month (measured 2026-09-15, methodology v1).
What this means — and what it does not
- It means the server's public list of tools changed between those two dates. We say what changed, not why anyone changed it.
- The dates are a window, not an event time. We did not look on every day in between, so we do not claim a change happened on any particular day inside it.
- We have not measured how many other projects depend on this server. That is not the same as none — it means we do not have that number for this kind of server yet.
- This is a record of a public declaration. It is not a judgement about the server, its authors, or whether you should use it.
Verify it yourself
Every row above is a dated observation we stored on the day we took it; you can re-derive any of them at /verify.
Technical detail — method, hashes, source filter
Observed by comparing consecutive dated snapshots of the server's declared tool list. The contract hash is a fingerprint of that list: an identical hash on two dates means an identical declaration.
declared tool count: 4 → 12 (+8) declared-contract hash: changed between the two dated snapshots observation window: 2026-08-20 → 2026-08-21 (interval; no point date is asserted inside it)
Observation slice hash: pending. Full method, class definitions and the measured significance threshold: methodology v1.1 (frozen, versioned). Class 1 — Schema break.
Operators of this server can submit context via /dispute — submissions are logged and linked here.
Full forensic dossier available on request — request the dossier.
These are factual observation records derived from dated snapshots of publicly declared, machine-readable material. They contain no assessment of fault, intent, or fitness for purpose. Corrections and context: /dispute.