VerifyMCP-OwnersBot

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-08-31 23:12:20Z to 2026-09-01 04:12:18Z UTC.

VerifyMCP-OwnersBot/1.0 (+https://verifymcp.io/docs/build/owners-json)

5 request(s) from 1 distinct address(es), 5 distinct path(s), first seen 2026-08-31 23:12:20Z, last seen 2026-09-01 04:12:18Z UTC. 4 separate visit(s), counting a gap of more than 30 minutes as a new one, median 60.0 minutes between them.

The user-agent strings, exactly as they arrived

user-agentrequestsaddressesfirst seenlast seen
VerifyMCP-OwnersBot/1.0 (+https://verifymcp.io/docs/build/owners-json)512026-08-31 23:12:20Z2026-09-01 04:12:18Z

What it asked for, in the order it asked

First request to each path, oldest first.

#pathat (UTC)status
1/mcp/.well-known/owners.json2026-08-31 23:12:20Z404
2/.well-known/owners.json2026-08-31 23:12:20Z404
3/c/mcp-registry-official/mcp/.well-known/owners.json2026-09-01 02:12:20Z200
4/c/mcp-registry-official/mcp/triage/.well-known/owners.json2026-09-01 03:12:18Z404
5/c/mcp-registry-official/mcp/doctor/.well-known/owners.json2026-09-01 04:12:18Z404

Everything it asked for

pathrequestsstatus codesfirstlast
/.well-known/owners.json1404×12026-08-31 23:12:20Z2026-08-31 23:12:20Z
/c/mcp-registry-official/mcp/.well-known/owners.json1200×12026-09-01 02:12:20Z2026-09-01 02:12:20Z
/c/mcp-registry-official/mcp/doctor/.well-known/owners.json1404×12026-09-01 04:12:18Z2026-09-01 04:12:18Z
/c/mcp-registry-official/mcp/triage/.well-known/owners.json1404×12026-09-01 03:12:18Z2026-09-01 03:12:18Z
/mcp/.well-known/owners.json1404×12026-08-31 23:12:20Z2026-08-31 23:12:20Z

What it asked for that did not exist

path it asked forwhat it gotfirst askedsince then
/mcp/.well-known/owners.json404×12026-08-31 23:12:20Zanswers 200 since 2026-09-01 00:35:07Z
/.well-known/owners.json404×12026-08-31 23:12:20Zanswers 200 since 2026-09-01 00:35:07Z
/c/mcp-registry-official/mcp/triage/.well-known/owners.json404×12026-09-01 03:12:18Zstill absent
/c/mcp-registry-official/mcp/doctor/.well-known/owners.json404×12026-09-01 04:12:18Zstill absent

What it got, and what it sent

Status codes
404×4, 200×1
Accept headers
application/json
Bytes served
8289
Attributed to a channel
mcp-registry-official (3)
Our instrument classed it
agent×5 — 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. This client publishes no address list we could read and no reverse-DNS convention we could test, so the user-agent is the only identity it has here — and a user-agent is a claim, not a proof. Anyone can send this string.

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://verifymcp.io/docs/build/owners-json in its own user-agent. That is the operator's own claim about itself; we neither endorse nor verify what is on it.

Its user-agent points at https://verifymcp.io/docs/build/owners-json, which is the document it came to read. It asked this host for /mcp/.well-known/owners.json before that file existed; the log below shows when the same path started answering 200.

Checked 2026-09-01 against its own user-agent string, and our request log.

This page as data

curl -s https://www.pathwren.workers.dev/bot/verifymcp-ownersbot.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

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-08-31 23:12:20Z to 2026-09-01 04:12:18Z 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.