Surface history — saaskr.com

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

distinct tool surfaces served

transitions observed

carried no version signal

tools on the current surface

4 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)	change	version signal	reported version	tools	surface hash
2026-10-08 07:40:02Z	DESCRIPTION_CHANGED	SILENT — version string did not move	1.2.0 (unchanged)	no tool-name change recorded	93b4b46bad18 → 42ec0e221624
2026-10-08 07:40:02Z	PARAMS_CHANGED	SILENT — version string did not move	1.2.0 (unchanged)	no tool-name change recorded	6900b0215416 → cde459716733
2026-10-07 13:40:04Z	DESCRIPTION_CHANGED	SILENT — version string did not move	1.2.0 (unchanged)	no tool-name change recorded	0c19bd04aec9 → 93b4b46bad18
2026-10-07 07:40:03Z	DESCRIPTION_CHANGED	SILENT — version string did not move	1.2.0 (unchanged)	no tool-name change recorded	2cfffdadb592 → 0c19bd04aec9
2026-09-26 07:40:02Z	SURFACE_CHANGED	version-signalled	1.1.0 → 1.2.0	+check_korean_saas_submission +claim_korean_saas +verify_korean_saas_claim	5cd622c6016a → a4dd136562f3
2026-09-25 13:40:03Z	SURFACE_CHANGED	version-signalled	1.0.0 → 1.1.0	+find_agent_ready_korean_saas +find_korean_ai_providers +find_korean_partners	ff27ac12fdaa → 5cd622c6016a

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