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-14 06:17:00Z UTC.
mcpbeat/0.1 (+https://mcpbeat.com/bot/; liveness check) mcpbeat/0.1 (+https://mcpbeat.com/bot/) mcpbeat/0.1 (+https://mcpbeat.com/bot/; metadata check)
8466 request(s) from 2 distinct address(es), 10 distinct path(s), first seen 2026-09-01 01:43:38Z, last seen 2026-09-14 06:17:00Z UTC. 8 separate visit(s), counting a gap of more than 30 minutes as a new one, median 738.8 minutes between them.
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) | 8460 | 2 | 2026-09-01 01:43:38Z | 2026-09-14 06:17:00Z |
mcpbeat/0.1 (+https://mcpbeat.com/bot/) | 4 | 1 | 2026-09-01 03:44:30Z | 2026-09-07 03:48:00Z |
mcpbeat/0.1 (+https://mcpbeat.com/bot/; metadata check) | 2 | 1 | 2026-09-01 02:06:23Z | 2026-09-01 02:06:23Z |
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 |
| 5 | /c/mcp-registry-official/mcp/netcheck | 2026-09-02 01:33:46Z | 200 |
| 6 | /c/mcp-registry-official/mcp/doctor | 2026-09-02 01:33:46Z | 200 |
| 7 | /c/mcp-registry-official/mcp/triage | 2026-09-02 01:33:46Z | 200 |
| 8 | /c/mcp-registry-official/mcp/robots | 2026-09-02 01:33:46Z | 200 |
| 9 | /c/mcp-registry-official/mcp/lint | 2026-09-03 01:25:59Z | 200 |
| 10 | /c/mcp-registry-official/mcp/markdown | 2026-09-07 01:39:27Z | 200 |
| path | requests | status codes | first | last |
|---|---|---|---|---|
/c/mcp-registry-official/mcp | 1364 | 200×1242, 202×122 | 2026-09-01 01:43:38Z | 2026-09-14 06:17:00Z |
/c/mcp-registry-official/mcp/robots | 1273 | 200×1166, 202×107 | 2026-09-02 01:33:46Z | 2026-09-14 06:17:00Z |
/c/mcp-registry-official/mcp/triage | 1268 | 200×1165, 202×103 | 2026-09-02 01:33:46Z | 2026-09-14 06:17:00Z |
/c/mcp-registry-official/mcp/netcheck | 1263 | 200×1167, 202×96 | 2026-09-02 01:33:46Z | 2026-09-14 06:17:00Z |
/c/mcp-registry-official/mcp/doctor | 1258 | 200×1150, 202×108 | 2026-09-02 01:33:46Z | 2026-09-14 06:17:00Z |
/c/mcp-registry-official/mcp/lint | 1215 | 200×1128, 202×87 | 2026-09-03 01:25:59Z | 2026-09-14 06:17:00Z |
/c/mcp-registry-official/mcp/markdown | 819 | 200×761, 202×58 | 2026-09-07 01:39:27Z | 2026-09-14 06:17:00Z |
/favicon.ico | 4 | 200×4 | 2026-09-01 03:44:30Z | 2026-09-07 03:48:00Z |
/.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 |
| 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: No |
/.well-known/oauth-authorization-server | 404×1 | 2026-09-01 02:06:23Z | still absent — on purpose: No |
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).
A question about this page, answered by a call you can make right now — no key, no account, no JSON-RPC, nothing to assemble. The query string is already filled in with this page's own subject.
curl -s 'https://www.pathwren.workers.dev/tools/classify-ua?ua=mcpbeat%2F0.1%20%28%2Bhttps%3A%2F%2Fmcpbeat.com%2Fbot%2F%3B%20liveness%20check%29&s=client-dossiers'
/tools/classify-ua?ua=mcpbeat%2F0.1%20%28%2Bhttps%3A%2F%2Fmcpbeat.com%2Fbot%2F%3B%20liveness%20check%29Every parameter above is a value the endpoint reads, not an address it visits: nothing is fetched on your behalf. Called without any parameter, each endpoint returns its own specification instead of an error. All of them.
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 · check a crawler yourself, no key
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-14 06:17:00Z 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
.