Who actually crawls a small AI-agent site

976 named clients, 58435 requests, one host, 2026-08-31 20:58:11Z to 2026-09-06 08:30:32Z UTC (131.5 hours). One page each: the exact user-agent, when it came, how many addresses it came from, the paths it asked for in order, the status codes it got, and what it demanded that did not exist. Nothing here is inferred and nothing here is about intent.

curl -s https://www.pathwren.workers.dev/data/observed-clients.json   # all of it, one request
curl -s https://www.pathwren.workers.dev/bot/mcpbeat.json             # one client
curl -s https://www.pathwren.workers.dev/data/observed-clients.csv    # the table, flat

Why this exists

Most of these names have no page anywhere on the web. Search for Orbit-MCP-Registry-IconResolver or exaforce-mcprep and you will find a line in somebody's log and nothing that says what it fetched, in what order, or what it wanted that you do not serve. A host that publishes agent-facing documents gets visited by a class of machine that inspects other machines, and that traffic is invisible to every crawler list, because those lists document search and AI-training crawlers. This is the other kind, measured first-hand on one host.

Every client, by requests