mcpbeat

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-03 06:25:38Z 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)

456 request(s) from 1 distinct address(es), 9 distinct path(s), first seen 2026-09-01 01:43:38Z, last seen 2026-09-03 06:25:38Z UTC. 6 separate visit(s), counting a gap of more than 30 minutes as a new one, median 664.5 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.

The user-agent strings, exactly as they arrived

What it asked for, in the order it asked

First request to each path, oldest first.

Everything it asked for

What it asked for that did not exist

What it got, and what it sent

Status codes

200×388, 202×66, 404×2

Accept headers

application/json, text/event-stream, image/*

Bytes served

1222432

Attributed to a channel

mcp-registry-official (451)

Our instrument classed it

crawler×400, agent×56 — that is our classifier's label from the user-agent, not the operator's, and it has been wrong before.

How to verify it is really them

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).

What it publishes about you afterwards

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.

Its own documentation

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).

This page as data

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

Method, and what this page will not say

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-03 06:25:38Z 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.