What this client asked www.pathwren.workers.dev for, when, and what it got.
Every number below is from this host's own server-side request log, 2026-09-01 01:43:38Z to 2026-09-01 06:12:16Z UTC.
mcpbeat/0.1 (+https://mcpbeat.com/bot/; liveness check) mcpbeat/0.1 (+https://mcpbeat.com/bot/; metadata check) mcpbeat/0.1 (+https://mcpbeat.com/bot/)
22 request(s) from 1 distinct address(es), 4 distinct path(s), first seen 2026-09-01 01:43:38Z, last seen 2026-09-01 06:12:16Z UTC. 1 separate visit(s), counting a gap of more than 30 minutes as a new one.
It describes itself, inside its own user-agent, as liveness check
. That is the client's own words, quoted; this page makes no claim about what it is for.
| user-agent | requests | addresses | first seen | last seen |
|---|---|---|---|---|
mcpbeat/0.1 (+https://mcpbeat.com/bot/; liveness check) | 19 | 1 | 2026-09-01 01:43:38Z | 2026-09-01 06:12:16Z |
mcpbeat/0.1 (+https://mcpbeat.com/bot/; metadata check) | 2 | 1 | 2026-09-01 02:06:23Z | 2026-09-01 02:06:23Z |
mcpbeat/0.1 (+https://mcpbeat.com/bot/) | 1 | 1 | 2026-09-01 03:44:30Z | 2026-09-01 03:44:30Z |
First request to each path, oldest first.
| # | path | at (UTC) | status |
|---|---|---|---|
| 1 | /c/mcp-registry-official/mcp | 2026-09-01 01:43:38Z | 200 |
| 2 | /.well-known/oauth-protected-resource | 2026-09-01 02:06:23Z | 404 |
| 3 | /.well-known/oauth-authorization-server | 2026-09-01 02:06:23Z | 404 |
| 4 | /favicon.ico | 2026-09-01 03:44:30Z | 200 |
| path | requests | status codes | first | last |
|---|---|---|---|---|
/c/mcp-registry-official/mcp | 19 | 200×14, 202×5 | 2026-09-01 01:43:38Z | 2026-09-01 06:12:16Z |
/.well-known/oauth-authorization-server | 1 | 404×1 | 2026-09-01 02:06:23Z | 2026-09-01 02:06:23Z |
/.well-known/oauth-protected-resource | 1 | 404×1 | 2026-09-01 02:06:23Z | 2026-09-01 02:06:23Z |
/favicon.ico | 1 | 200×1 | 2026-09-01 03:44:30Z | 2026-09-01 03:44:30Z |
| path it asked for | what it got | first asked | since then |
|---|---|---|---|
/.well-known/oauth-protected-resource | 404×1 | 2026-09-01 02:06:23Z | still absent — on purpose: one of the discovery documents /mcp/doctor checks; the reason this host does not serve it is written there |
/.well-known/oauth-authorization-server | 404×1 | 2026-09-01 02:06:23Z | still absent — on purpose: one of the discovery documents /mcp/doctor checks; the reason this host does not serve it is written there |
not observed — no address list and no reverse-DNS convention is published at any URL we could read.
Checked 2026-09-01 against https://mcpbeat.com/bot/ (403 to us).
Not observed. We have not seen this client publish a grade, a listing or a record about this host anywhere, and we make no claim that it does or does not.
It names https://mcpbeat.com/bot/ in its own user-agent. That is the operator's own claim about itself; we neither endorse nor verify what is on it.
The user-agent names +https://mcpbeat.com/bot/, which is the documented way to find out what this validator wants. That page answered HTTP 403 behind a Cloudflare JavaScript challenge when we fetched it, so its published specification could not be read.
Checked 2026-09-01 against https://mcpbeat.com/bot/ (403 to us).
curl -s https://www.pathwren.workers.dev/bot/mcpbeat.json curl -s https://www.pathwren.workers.dev/data/observed-clients.json # every client, one request
JSON · markdown · all clients seen here · index as JSON
Rows come from a server-side log written before anything is served, so clients that
run no JavaScript are counted exactly like browsers. The window is the whole life of the log,
2026-09-01 01:43:38Z to 2026-09-01 06:12:16Z UTC, and it is stated on every number because a count without a window is
not a fact. Addresses are stored as salted hashes and counted, never printed. Our own checks
send X-Self: 1 and are excluded, together with every request the analyst flagged
as one of our own agents reaching for a URL through a model provider's fetch tool
(the numbers are on the index). Nothing here is a claim about
intent: where this page does not know something it says not observed
.