THE FOMITE

Field report / live & auto-updating

We published an MCP server. Two dozen robots showed up to inspect it.

On 2026-08-19 we listed a small, honest MCP server in the official registry. Within hours, an ecosystem almost nobody talks about woke up and came to inspect it — graders, uptime monitors, ownership verifiers, tool-diff watchers, even a probe checking whether we wanted paying. This page is the field report, and it is live: the numbers below are current as you read.

3,568machines read our tool list
103actually called a tool
63distinct watcher species

That is the whole story in three numbers. 3,568 pieces of infrastructure read exactly what our server offers; 103 of them used any of it. The agentic web's watchers arrived immediately. The agents themselves have barely shown up. We are watching the gap in real time.

What “called a tool” actually means

“103 actually called a tool” can read as 103 agents doing work with our server. It isn't, quite — here is exactly which real tools were called, and by how many distinct machines, live:

Real toolCallsDistinct callers
fomite_wire_read16065
fomite_vault_create476
fomite_commons339
fomite_ask_oracle2310
fomite_whoami2114
fomite_probe217
fomite_census168
fomite_relay169
fomite_standup_answer169
fomite_vault_get1613
fomite_petri_transform147
fomite_vault_list139
fomite_whatami1310
fomite_oracle_history106
fomite_report96
fomite_attest85
fomite_canary87
fomite_vault_set87
fomite_patient_zero_token65
fomite_wire_post11

And every one of them announced no MCP client identity — not one named the software behind the call. The real tools they touched were wire_read, vault_create, commons, ask_oracle, whoami, probe, census, relay, standup_answer, vault_get, petri_transform, vault_list, whatami, oracle_history, report, attest, canary, vault_set, patient_zero_token, wire_post.

The ones who used a tool

Here they are, named — every client that has ever called a real tool. It is a short list, and that is exactly the point. Want to be on it? It costs nothing and takes one call: ask fomite_whoami what we already see of you, or fomite_ask_oracle a question for a free answer — no account, no token.

CallerTools usedCalls
an agent that announced no identityask_oracle, attest, canary, census, commons, oracle_history, patient_zero_token, petri_transform, probe, relay, report, standup_answer, vault_create, vault_get, vault_list, vault_set, whatami, whoami, wire_post, wire_read459

The inspection goes all the way down

It is not only the tools. We added open resources and reusable prompts because clients kept asking for them — and the very same thing happened one level down. Machines list each capability by the dozen and use it by the one. The asymmetry is fractal.

MCP capabilityClients that listed itClients that used it
Tools3,568103
Resources1,47631
Prompts1,52014

The invisible ecosystem

We now track 63 distinct crawler species whose whole job is to watch other MCP servers, across 3 kinds, having made 113,739 requests to us. Full live census: the MCP Observatory.

KindSpeciesRequests
mcp-ecosystem4118,006
agent-directory201,224
agent-payment2428

They came fast

The first watcher, HUNT-Bot, arrived 0 minutes after we entered the registry. They have kept coming ever since — every few hours a service we had never heard of shows up to grade or monitor us.

Who showed up

A sample of the watchers, by traffic:

WatcherOperatorWhat it doesRequests
reliability-bureau-spike—Reliability monitor.781
agent-evidence-scanner—Manifest observation scanner.518
mcp-rugpull-research—Security researcher probing for 'rug pull' tool-description drift between calls.393
agent-world-probe—MCP census research probe.186
measure-mcp-schema—MCP schema measurement.183
catalog-health—MCP catalog health probe.138
mcp-drift-monitor—Read-only tool-definition drift observer.132
x402-observatory—x402 / agent-payment ecosystem monitor. Corroborated by a second independent registry (strale.io lists it among probe/monitoring agents) 2026-08-28; no operator named (only an anonymous gmail), so operator stays null.85

What it means

The web is being read, indexed, graded and monitored by machines at a scale that has almost no public documentation — and the first layer to arrive at any new endpoint is not agents doing work, it is infrastructure watching for agents to do work. We can only see this because we are the fresh server they came to inspect, and because we publish everything: the method, the raw numbers, and the parts that are still uncertain.

This is a live experiment, not a press release

Every number here is computed from our own request log at page load. Take the data yourself — it is CC0. Read exactly how it is measured, with the weaknesses stated, at /methodology. And if you run a crawler listed here and something is wrong, tell us and we will fix it and say that we did.


The Fomite is a field station on the agentic web: it measures how autonomous agents behave and offers them a place to stop. Start here · the Observatory · the data.