dev.workers.quietworklabs.robots-check/robots-check
https://robots-check.quietworklabs.workers.dev
Registry code: 78d7169baf98eb5a
Tests whether a URL may be crawled by a given user-agent under robots.txt (RFC 9309 matching), shows which AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended and others) a site blocks, reads page-level noindex/noai directives and llms.txt, and validates XML sitemaps. Before fetching a page, call GET /v1/robots-check?url=<page>&user_agent=<your bot token> to get allowed true/false, the deciding rule and crawl-delay (RFC 9309). GET /v1/ai-crawlers?url= returns per-bot verdicts for 20 AI/search crawlers plus meta robots, X-Robots-Tag and llms.txt. GET /v1/sitemap-check?url= finds…
- endpoint
- https://robots-check.quietworklabs.workers.dev/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is dev.workers.quietworklabs.robots-check/robots-check live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is dev.workers.quietworklabs.robots-check/robots-check free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does dev.workers.quietworklabs.robots-check/robots-check have?
- 3 tools: sitemap_check, ai_crawler_access, robots_check.
- Is dev.workers.quietworklabs.robots-check/robots-check safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 3 tools
- unknown → live
Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 4 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.
through this hub
successful
what callers paid
distinct
last 2026-10-18
counted from three payers (thin, concentrated, shared-payto)
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
sitemap_check unknown 2h ago
Finds a site's sitemap (from robots.txt, else /sitemap.xml) or checks the sitemap URL given, and validates it: urlset vs sitemapindex, entry count against the 50,000 limit, lastmod format and range, relative/off-host/duplicate/http URLs, gzip support. Returns sample URLs or child sitemaps. Deterministic, no AI. Price: $0.002 USDC per call via x402 (Base); the first 5 calls per day per client are free.
{ "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "examples": [ "https://www.python.org/" ], "description": "Site URL (discovers the sitemap) or a sitemap URL" } } }arguments 15 linesai_crawler_access unknown 2h ago
AI crawler access report for a URL: robots.txt verdict for 20 tokens (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, Claude-User, Google-Extended, Applebot-Extended, PerplexityBot, Meta-ExternalAgent, CCBot, Bytespider, Amazonbot and more) grouped by training/search/user purpose, plus page meta robots, X-Robots-Tag (noindex/noai) and llms.txt presence. Deterministic, no AI. Price: $0.002 USDC per call via x402 (Base); the first 5 calls per day per client are free.
{ "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "examples": [ "https://www.theguardian.com/" ], "description": "Site or page URL" } } }arguments 15 linesrobots_check unknown 2h ago
Crawl-permission preflight for agents and scrapers: fetches the site's robots.txt and evaluates the URL for a user-agent token per RFC 9309 (group by product token else *, longest match, Allow wins ties, * and $ wildcards, 4xx=allow all, 5xx=disallow all). Returns allowed, the deciding rule and line, crawl-delay and sitemaps. Deterministic, no AI. Price: $0.001 USDC per call via x402 (Base); the first 5 calls per day per client are free.
{ "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "examples": [ "https://www.nytimes.com/section/technology" ], "description": "Page URL to test" }, "user_agent": { "type": "string", "examples": [ "GPTBot" ], "description": "Crawler product token, e.g. GPTBot or MyAgent. Default *" } } }arguments 22 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id78d7169baf98eb5a.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/78d7169baf98eb5a/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/78d7169baf98eb5a?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.