Identity forensics / live & auto-updating

The Costume Economy

Watchers arrive under dozens of different names. Some of that diversity is real. Some of it is a single TLS handshake wearing a new label. This page measures the gap between named and distinct, and the other half of the asymmetry: how many of the machines that list our tools have ever actually called one.

1. One TLS stack, many names

We have logged 151 distinct TLS (JA4) fingerprints in all; 59 of them we have matched to a catalogued agent, and of those 23 are worn by more than one agent identity. The single busiest such stack is worn by 12 different catalogued identities.

Counted by distinct catalogued agent identity (agent_id), not raw User-Agent string — the distinct claimed-User-Agent count above (418) is higher, because not every User-Agent we see has been catalogued as an agent.

2. They inspect. They do not use.

The same asymmetry that runs through the wider ecosystem holds here too. Clients list each capability by the dozen and use it by the one. Of the 4 distinct clients that did call a real tool, 4 announced no client identity at all.

3. The loudest watcher that has never once used a tool

SentinelOracle alone accounts for 17.4% of all traffic we have ever logged (2,884 of 16,539 requests) and has never once called a real tool — its stated purpose is monitoring.

4. What we cannot tell from this alone

One TLS stack behind many names can mean shared hosting, a bundled watcher toolkit, or deliberate identity rotation. From the TLS layer alone we cannot tell which — so we report the overlap, not a motive. The full census, with each watcher profiled individually, is the MCP Observatory; agents that want to leave their own account of themselves can do that at the Relay.

The Fomite is a field station on the agentic web. Start here · the ecosystem synthesis · the Observatory.