CrawlCheck
Trust · metrics

How CrawlCheck is used, and how often it is right.

One view of the network, the developers calling it, the trust numbers and the north-star metric, for the last 7 days. Every number links to the endpoint it came from; CrawlCheck’s own tests are counted apart and never in these figures.

North star

verified agent actions backed by a fresh signed Resolve record, by action type.

decisions issued600signed preflight decisions in the window source
decisions to verified agents 30d0decisions issued to a named AI agent calling from its operator's published ranges, 30 days source
receipts checked by outside sites 30d13receipts checked by a site CrawlCheck does not run, 30 days source
goal reachednoone verified-agent decision and one outside receipt check source
DayDecisions issuedReceipts checked by sites
2026-10-1300
2026-10-1210
2026-10-11504
2026-10-1024525
2026-10-091161
2026-10-08290
2026-10-0715953

Developers

api calls outside26,611calls to agent endpoints by anyone but CrawlCheck's own tooling, in the window (counted from 2026-10-09; earlier days read 0) source
resolve calls7,222Resolve lookups (HTTP, DNS-over-HTTPS, private prefix, staple)
preflight calls1,060preflight decisions requested
receipt checks60receipt lookups
mcp calls1,800MCP requests (POST /mcp)
active keys1licence keys that used metered calls this month (includes test and sandbox licences)
sdk downloads npm last week2,050downloads of @crawlcheck/sdk (registry downloads include mirrors and CI; they are not users) source
sdk downloads pypi last week1,576downloads of crawlcheck (registry downloads include mirrors and CI; they are not users) source

Outside calls by client: other 16771 · node 4250 · ai agent 4066 · script 652 · python sdk 532 · browser 340.

DayResolvePreflightReceiptsMCPOther v14xx5xx
2026-10-070000000
2026-10-080000000
2026-10-091330754217673971
2026-10-10193426241161695014382
2026-10-112640716147015257412515
2026-10-129777169318834810
2026-10-13341002436121190

Trust

false positive rate on appeal0share of resolved disputes where the finding was withdrawn (measured only where someone appealed; findings nobody disputed are not checked by this number) source
disputes resolved 90d1disputes resolved in 90 days (1 filed, 0 open); median turnaround 0.02 h source
trace coverage100% of findings linked to the rule span that decided them, last scans source
ObjectiveMeasuredTargetStatus
resolve availability100%99.9%met
resolve latency95.8%95%at_risk
preflight availability100%99.9%met
preflight latency81.5%95%missed
jit latency84.2%95%missed

Network

sites measured265,387distinct domains source
crawler visits148,525verified and unverified crawler requests to crawlcheck.io, last 90 days source
scans run3,527scans source
mcp servers listed40,688servers in the official MCP Registry (25,686 with a remote endpoint) source
mcp endpoints observed11,529remote endpoints sent the MCP handshake this cycle (5,663 completed it) source
customer observers0observers run by customers on their own sites source

Counts only: no caller address, key or site is stored with these numbers. Outside means not CrawlCheck's own tooling; it still includes people testing by hand. Weekly editions: /api/v1/metrics?week=YYYY-Www. Signed JSON: /api/v1/metrics (?days=1-30).