An observation record, not an assessment. Every row below is a change we recorded directly, with the content hash before and after. https://app.tascan.io/mcp
6 of these transitions happened while the reported version string stayed the same. A consumer pinning that version would have received a different tool surface with nothing in the version to indicate it. That is a compatibility and review fact, not a security finding and not an allegation of wrongdoing — unversioned iteration is normal practice and is frequently deliberate.
| observed at (UTC) | change | version signal | reported version | tools | surface hash |
|---|---|---|---|---|---|
| 2026-10-08 01:40:02Z | DESCRIPTION_CHANGED | SILENT — version string did not move | 3.19.0 (unchanged) | no tool-name change recorded | fa151fb8a9d4 → b361bb870a90 |
| 2026-10-08 01:40:02Z | PARAMS_CHANGED | SILENT — version string did not move | 3.19.0 (unchanged) | no tool-name change recorded | b2b2695825d8 → ef2409759188 |
| 2026-10-07 19:40:03Z | DESCRIPTION_CHANGED | SILENT — version string did not move | 3.19.0 (unchanged) | no tool-name change recorded | 1225caa17815 → fa151fb8a9d4 |
| 2026-10-06 19:40:03Z | SURFACE_CHANGED | SILENT — version string did not move | 3.19.0 (unchanged) | +tascan_get_signature_bundle | 3f0f958d8e5c → 075eac3edc57 |
| 2026-10-06 01:40:03Z | DESCRIPTION_CHANGED | SILENT — version string did not move | 3.19.0 (unchanged) | no tool-name change recorded | 6b2c174d3594 → 3b293c064a8e |
| 2026-10-06 01:40:03Z | PARAMS_CHANGED | SILENT — version string did not move | 3.19.0 (unchanged) | no tool-name change recorded | 1d15b9d50c14 → 1d89e5a10ce1 |
| 2026-09-29 01:40:03Z | SURFACE_CHANGED | version-signalled | 3.18.0 → 3.19.0 | +tascan_quickstart | b497e9f97558 → 3f0f958d8e5c |
| 2026-09-28 19:40:03Z | SURFACE_CHANGED | version-signalled | 3.17.0 → 3.18.0 | +tascan_claim_run +tascan_finish_run +tascan_heartbeat_run | 50a4975bc231 → b497e9f97558 |
| 2026-09-28 13:40:03Z | SURFACE_CHANGED | version-signalled | 3.16.1 → 3.17.0 | +tascan_control_fanout +tascan_create_fanout +tascan_get_fanout | b22753b00cc4 → 50a4975bc231 |
| 2026-09-27 19:40:02Z | SURFACE_CHANGED | version-signalled | 3.16.0 → 3.16.1 | +tascan_delegate_to_agent +tascan_get_budget +tascan_get_device +tascan_get_usage +tascan_list_delegations +tascan_list_devices +tascan_revoke_delegation +tascan_revoke_device | 03002514e09f → b22753b00cc4 |
This section is identical for ~92% of publishers and is published as
shared context, not as a finding about app.tascan.io. 90 dependency
packages sit beneath the measured MCP population; 41 have a
single maintainer and 31 have not published in over two years.
The widest is zod at
80.46% of npm-backed servers (8529 servers,
1 maintainer, last publish 2026-09-13).
These are properties of the shared SDK dependency closure. Any page claiming this set as
one operator's personal exposure is misreading a universal fact as a private one.
Source: state/mcp-census/chokepoint-maintainers.json, as_of 2026-10-07.
Observation window 2026-09-21 → 2026-10-10.
22,294 servers were observed; 2,214
were seen to change and 20,080 were observed and
recorded no change — that negative control is why a non-zero count here means something.
Across the corpus, 4,781 of
6,334 changes carried no version signal, and
1,690 of those added or removed tools.
What this does NOT cover: servers outside the observed set; changes that
occurred before 2026-09-21; changes that began and reverted between two observations;
and any server reachable only with credentials we do not hold. A server's absence from this
record is not evidence it did not change — only that we did not observe it.
Universe captured 2026-10-10T19:40:03.823Z. Produced by core/surface_history_page.cjs (reads core/surface_clock producers).
Hashes are of the served tool surface and are recomputable from the server's own response.