Surface history — www.constat-auto.com

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

distinct tool surfaces served

transitions observed

carried no version signal

tools on the current surface

Read this as alternation, not instability. These 4 transitions move between only 2 distinct surfaces, returning to a previously-served hash 2 times. That is the signature of more than one deployment answering the same hostname — a load balancer or a staged rollout — rather than a product changing 4 times. We are not reporting 4 changes. The consumer-facing fact is narrower and still real: the tool list you receive from this host depends on which instance answers you, and the reported version does not distinguish them.

Recorded changes

observed at (UTC)	change	version signal	reported version	tools	surface hash
2026-10-10 13:40:03Z	DESCRIPTION_CHANGED	SILENT — version string did not move	1.0.0 (unchanged)	no tool-name change recorded	e0a2126ea69c → caec8e6dd3ab
2026-10-09 13:40:04Z	DESCRIPTION_CHANGED	SILENT — version string did not move	1.0.0 (unchanged)	no tool-name change recorded	caec8e6dd3ab → e0a2126ea69c
2026-10-08 07:40:02Z	DESCRIPTION_CHANGED	SILENT — version string did not move	1.0.0 (unchanged)	no tool-name change recorded	e0a2126ea69c → caec8e6dd3ab
2026-10-08 01:40:02Z	DESCRIPTION_CHANGED	SILENT — version string did not move	1.0.0 (unchanged)	no tool-name change recorded	caec8e6dd3ab → e0a2126ea69c

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 www.constat-auto.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 www.constat-auto.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.