Surface history — mcp.eqvps.com

An observation record, not an assessment. Every row below is a change we recorded directly, with the content hash before and after. https://mcp.eqvps.com/mcp

12
distinct tool surfaces served
10
transitions observed
7
carried no version signal
45
tools on the current surface

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

Recorded changes

observed at (UTC)changeversion signalreported versiontoolssurface hash
2026-10-06 13:40:04Z DESCRIPTION_CHANGED SILENT — version string did not move 1.6.0 (unchanged) no tool-name change recorded d79aa63a990b → 35666d079ac9
2026-10-06 07:40:03Z DESCRIPTION_CHANGED SILENT — version string did not move 1.6.0 (unchanged) no tool-name change recorded 425333f972ef → d79aa63a990b
2026-10-05 19:40:04Z DESCRIPTION_CHANGED SILENT — version string did not move 1.6.0 (unchanged) no tool-name change recorded 5e4556a7e53b → 425333f972ef
2026-10-05 01:40:03Z PARAMS_CHANGED SILENT — version string did not move 1.6.0 (unchanged) no tool-name change recorded 03abfe1de4cc → 0853901cf25e
2026-10-04 01:12:58Z DESCRIPTION_CHANGED SILENT — version string did not move 1.6.0 (unchanged) no tool-name change recorded 7231b717ca7d → c53470568684
2026-10-03 13:40:03Z SURFACE_CHANGED version-signalled 1.3.0 → 1.6.0 +change_plan +get_download_url +get_started +get_upgrade_options +get_upload_url +refresh_token +undo_cancel 605e1d49b4fb → 100000cf29f5
2026-10-03 07:40:04Z SURFACE_CHANGED version-signalled 1.1.0 → 1.3.0 +get_task +kill_task bab7f6fa91a3 → 605e1d49b4fb
2026-10-03 01:40:03Z SURFACE_CHANGED version-signalled 1.0.1 → 1.1.0 +create_sandbox +download_file +exec_command +get_sandbox +kill_sandbox +list_sandboxes +run_code +sandbox_pricing +upload_file 9ae97b5c07c8 → bab7f6fa91a3
2026-09-28 19:40:03Z PARAMS_CHANGED SILENT — version string did not move 1.0.1 (unchanged) no tool-name change recorded —
2026-09-28 01:40:05Z PARAMS_CHANGED SILENT — version string did not move 1.0.1 (unchanged) no tool-name change recorded —
Right of reply. If any row is wrong — a change we attributed to you that isn't yours, a hash that doesn't match, a host that was reassigned — say so and we will correct or withdraw the record and publish the correction alongside it. Dispute or correct this record. We will also remove this page on request from the operator of mcp.eqvps.com.

Ecosystem context — not specific to this server

This section is identical for ~92% of publishers and is published as shared context, not as a finding about mcp.eqvps.com. 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.

Coverage and limits

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.