Surface history — tradingstrategies.work

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

distinct tool surfaces served

transitions observed

carried no version signal

tools on the current surface

12 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-10 19:40:03Z	DESCRIPTION_CHANGED	SILENT — version string did not move	1.13.0 (unchanged)	no tool-name change recorded	7b7ccfcf6d0c → 0c535debe7b1
2026-10-10 19:40:03Z	PARAMS_CHANGED	SILENT — version string did not move	1.13.0 (unchanged)	no tool-name change recorded	a8082378dae2 → 41592cda8e24
2026-10-08 01:40:02Z	DESCRIPTION_CHANGED	SILENT — version string did not move	1.13.0 (unchanged)	no tool-name change recorded	24237c4018c0 → 7b7ccfcf6d0c
2026-10-08 01:40:02Z	PARAMS_CHANGED	SILENT — version string did not move	1.13.0 (unchanged)	no tool-name change recorded	8351ecb7a555 → a8082378dae2
2026-10-06 19:40:03Z	DESCRIPTION_CHANGED	SILENT — version string did not move	1.13.0 (unchanged)	no tool-name change recorded	9162cd5e584d → 24237c4018c0
2026-10-06 13:40:04Z	DESCRIPTION_CHANGED	SILENT — version string did not move	1.13.0 (unchanged)	no tool-name change recorded	ad06294571a2 → 9162cd5e584d
2026-10-05 13:40:03Z	DESCRIPTION_CHANGED	SILENT — version string did not move	1.13.0 (unchanged)	no tool-name change recorded	e852c3de687b → ad06294571a2
2026-10-05 13:40:03Z	PARAMS_CHANGED	SILENT — version string did not move	1.13.0 (unchanged)	no tool-name change recorded	9bfdbfb42e76 → 8351ecb7a555
2026-10-02 19:40:04Z	PARAMS_CHANGED	SILENT — version string did not move	1.13.0 (unchanged)	no tool-name change recorded	—
2026-10-02 13:40:02Z	PARAMS_CHANGED	SILENT — version string did not move	1.13.0 (unchanged)	no tool-name change recorded	—
2026-09-28 07:40:03Z	PARAMS_CHANGED	SILENT — version string did not move	1.13.0 (unchanged)	no tool-name change recorded	—
2026-09-25 19:40:04Z	SURFACE_CHANGED	SILENT — version string did not move	1.13.0 (unchanged)	+arena_call_extended +arena_get_max_pain_history	cc1f5b16dc95 → 6790f3b1ee66

Display this record

The badge reflects what we observed, including when that is unflattering. We offer it either way on purpose — a mark you can only display when it flatters you is an advertisement, and nobody can rely on an advertisement.

Free, no account, no attribution fee. The image updates itself as the record changes.

Markdown — for a README

[![Still OS surface record](https://stillosdigitalholdings.com/surface/badge/tradingstrategies.work.svg)](https://stillosdigitalholdings.com/surface/tradingstrategies.work)

HTML

<a href="https://stillosdigitalholdings.com/surface/tradingstrategies.work"><img src="https://stillosdigitalholdings.com/surface/badge/tradingstrategies.work.svg" alt="Still OS surface record"></a>

Is this your server? We will watch this surface continuously and tell you the moment it changes — the version string, which tools moved, and the hash before and after. You do not get a better record by asking; the record is whatever we observe. Monitor this surface.

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

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

Elsewhere in this record set

We publish a separate trust and dependency assessment for this same host: tradingstrategies.work — operator dossier. That one grades the published artifact; this one records what the endpoint actually served.

Index of everything covered: all observed hosts · machine-readable: changes feed (JSON), Atom, sitemap.

Other hosts observed around the same time

mcp.ludo.ai · nova.civai.co · mcp.dropenginehq.com · exchange-production-9123.up.railway.app · api.xdata.kr · youspot.com · mcp.foxform.app · aspern.org · compensationprofessional.com · mcpconnector-gtlizqtvza-uw.a.run.app · askmatchbox.com · mcp.jojapi.com

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.