Can this crawler be verified at all, and how?

Before you read anything into a miss from /tools/verify-crawler: which crawlers can be verified by published prefix, which document forward-confirmed reverse DNS instead (with the exact two dig commands to run), and which publish no verification method at all — with the mirror's own counts and fetch dates.

Copy this

curl -s 'https://www.pathwren.workers.dev/tools/verification-methods?crawler=claudebot&s=client-dossiers'

The one row for ClaudeBot: its verification method, the operator URL it comes from, how many prefixes this host mirrors for it and when they were last fetched.

Run it in a browser — it answers JSON with access-control-allow-origin: *, so fetch() works from any page with no proxy.

No setup at all

No account, no key, no token, no handshake, no session.
GET (and HEAD). Anything else answers 405 with an Allow header and points at the MCP endpoint.
Cacheable: max-age=3600, a strong ETag, and a 304 when you send it back.
Asked with no parameters at all it answers 200 with its own specification, so walking /tools/ never costs you a 400.
CC0-1.0. Nothing is logged about you beyond the request line this host publishes about every client, including itself.

Parameters

parameter	required	what it is
`crawler` · `operator`, `q`	no	Crawler slug, name, operator or user-agent substring. Omit for the whole tally.

The same tool over MCP

This endpoint holds no copy of the logic: it calls verification_methods on the crawler-ip-verifier MCP server in-process, through that server's own JSON-RPC envelope. One implementation, two doors — an answer that changes here changed there.

curl -s https://www.pathwren.workers.dev/mcp/netcheck \
  -H 'content-type: application/json' \
  -H 'accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"verification_methods","arguments":{}}}'

What it will not do

Reverse DNS is never performed here — no request leaves this host — so the command is handed back, labelled as not run.
It fetches nothing. No argument here or on the MCP tool behind it takes a URL, and neither makes any outbound request: every answer comes out of files this host already publishes.

Also here

The other 7 endpoints, one page each.
123 clients that actually crawled this host, 2026-08-31 20:58:11Z to 2026-09-02 04:57:09Z UTC, one page each.
/data/observed-clients.json — that whole set in one request.