Surface history — fo.flocore.tech

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

distinct tool surfaces served

transitions observed

carried no version signal

tools on the current surface

10 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-06 19:40:03Z	DESCRIPTION_CHANGED	SILENT — version string did not move	1.0.0 (unchanged)	no tool-name change recorded	365420273c83 → f4312e5ef347
2026-10-06 19:40:03Z	PARAMS_CHANGED	SILENT — version string did not move	1.0.0 (unchanged)	no tool-name change recorded	e8b0703653aa → a1eeaf867eb3
2026-10-05 07:40:03Z	DESCRIPTION_CHANGED	SILENT — version string did not move	1.0.0 (unchanged)	no tool-name change recorded	b95119bce123 → 365420273c83
2026-10-04 19:40:04Z	DESCRIPTION_CHANGED	SILENT — version string did not move	1.0.0 (unchanged)	no tool-name change recorded	1d20ae6e09d7 → b95119bce123
2026-10-04 01:12:58Z	DESCRIPTION_CHANGED	SILENT — version string did not move	1.0.0 (unchanged)	no tool-name change recorded	e50ccbb9a926 → 1d20ae6e09d7
2026-10-01 13:40:04Z	PARAMS_CHANGED	SILENT — version string did not move	1.0.0 (unchanged)	no tool-name change recorded	—
2026-10-01 07:40:03Z	SURFACE_CHANGED	SILENT — version string did not move	1.0.0 (unchanged)	−flocore_ask −flocore_create_ticket −flocore_gate_action −flocore_list_tenants −flocore_list_tickets −flocore_mesh_lanes −flocore_ontology_entities −flocore_orch_board −flocore_queue_summary −flocore_recall −flocore_sandbox_approve	5e80060c0eeb → 4dddb5bf8510
2026-09-30 19:40:03Z	SURFACE_CHANGED	SILENT — version string did not move	1.0.0 (unchanged)	+flocore_gate_action +flocore_sandbox_approve	a8b132d14080 → 5e80060c0eeb
2026-09-30 07:40:03Z	PARAMS_CHANGED	SILENT — version string did not move	1.0.0 (unchanged)	no tool-name change recorded	—
2026-09-29 13:40:02Z	SURFACE_CHANGED	SILENT — version string did not move	1.0.0 (unchanged)	+flocore_support_ask	939477e7ede2 → a8b132d14080

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/fo.flocore.tech.svg)](https://stillosdigitalholdings.com/surface/fo.flocore.tech)

HTML

<a href="https://stillosdigitalholdings.com/surface/fo.flocore.tech"><img src="https://stillosdigitalholdings.com/surface/badge/fo.flocore.tech.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 fo.flocore.tech.

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 fo.flocore.tech. 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: fo.flocore.tech — 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

trysonar.app · agent-embassy.fly.dev · aemb.pro · pagos.andreax.dev · app.emailchaser.com · app.revdoku.com · agent-utilities.agent-utilities.workers.dev · www.fulfiller.com · games.thisisdelightful.com · gblin-mcp.gblin-mcp-worker.workers.dev · worklore.dev · www.hemmabo.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.