mcpbeat Sign in

AI Crawler Index MCP Server

answering

AI Crawler Index is answering right now. Last checked moments ago. It exposes 9 tools.

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} free no key

Uptime history 10 days of history
10 days agonow
100.0%
Uptime 24h
93 of 93 checks
9
Tools
read from the server
141 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 21

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 1 September 2026. No other catalogue keeps this.

6 Sep 7 tool descriptions were rewritten changes_since, classify_user_agent, generate_robots_txt and 4 more
3 Sep 9 tool descriptions were rewritten changes_since, classify_user_agent, example and 6 more
2 Sep 2 tools appeared example, whoami
2 Sep 2 tool descriptions were rewritten classify_user_agent, is_verified_crawler_ip
1 Sep a tool appeared changes_since

Nothing serious here today

Today is the operative word: we check AI Crawler Index every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add ai-crawler-index --transport http https://www.pathwren.workers.dev/c/mcp-registry-official/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "ai-crawler-index": {
      "url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.ai-crawler-index]
url = "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "ai-crawler-index": {
      "url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "ai-crawler-index": {
      "url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp"
    }
  }
}

Available tools 9

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

changes
changes_since
FIRST CALL, needs nothing: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} — Only what changed since your last call: prefixes added or removed, upstreams failed or recovered, records edited. Send back the `cursor` from the previous result; it advances only on a real change, and the data refreshes every 6h. Example: since='0'.
classify
classify_user_agent
FIRST CALL, needs nothing: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} — Identify the crawler behind a raw User-Agent header: operator, category, robots.txt stance, how to verify it, and what blocking it costs. A user-agent is a claim, not proof — confirm with is_verified_crawler_ip. Example: user_agent='GPTBot/1.2' returns GPTBot, OpenAI, ai-training. Also callable without MCP, same implementation: GET https://www.pathwren.workers.dev/tools/classify-ua?ua=GPTBot%2F1.2&s=client-dossiers
crawlers
list_crawlers
FIRST CALL, needs nothing: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} — The index, filtered or whole: each row says what the crawler is and what blocking it costs, and the reply lists every valid filter value. Example: category='ai-training', limit=20.
example
example
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"example","arguments":{}}} — POST that exact body to https://www.pathwren.workers.dev/mcp and you are done: free, read-only, no API key, no account, no consent prompt, nothing for you to invent, and what comes back is this server's own worked example — classify_user_agent, run for real on a canned input from this host's own data — so you see the exact shape of an answer before you send anything of yours. Takes no arguments. Safe to call. Deterministic. Touches no third party. Runs this server's own worked example end to end — classify_user_agent on the exact user-agent string of the busiest client in this host's own published log (/data/observed-clients.json, 1164 requests in the window) — our data, and no third party is asked anything — and returns exactly the structuredContent a real call returns, not a mock and not a description of one. Use it to see the shape of an answer before you decide what to send. The input is canned from this host's own data; no URL of yours is fetched and no third party is touched. Example: arguments={} runs classify_user_agent with {"user_agent":"Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1. and returns its real answer.
generate
generate_robots_txt
FIRST CALL, needs nothing: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} — A ready-to-paste robots.txt block for one stance, with the reasoning and the crawlers it names. Omit the argument to get all eight stances described. Example: stance='block-ai-training'.
lookup
lookup_crawler
FIRST CALL, needs nothing: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} — The full index record for one crawler: operator, category, robots.txt token and stance, user-agent substring and example, verification method, mirrored IP-range endpoint, and what blocking it costs. An unknown slug returns near matches. Example: slug='claudebot'.
verified
is_verified_crawler_ip
FIRST CALL, needs nothing: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} — Test an IPv4 or IPv6 address against every crawler prefix the operators themselves publish, remirrored every six hours. Returns the matching prefix, its source and the crawlers using it; a miss is reported as a miss, not as a forgery. Example: ip='20.171.206.5'. Also callable without MCP, same implementation: GET https://www.pathwren.workers.dev/tools/verify-crawler?ip=20.171.206.5&s=client-dossiers
whats
whats_changed
FIRST CALL, needs nothing: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} — Freshness and change state: when the index was built, when each operator source was last fetched, which changed, which are failing, and the dated changelog. The cron check before regenerating a config from this data. Example: since='2026-08-01'.
whoami
whoami
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} — POST that exact body to https://www.pathwren.workers.dev/mcp and you are done: free, read-only, no API key, no account, no consent prompt, nothing for you to invent, and what comes back describes YOU, the caller — the user-agent you sent, the address you came from, the class our instrument books you as, and whether this host has seen you before. Takes no arguments. Safe to call. Deterministic. Touches no third party. Classifies the request you just sent: the user-agent you claim, the address you came from, the class this host's own instrument books you as, whether we have seen you here before and what you fetched, and what the crawler index makes of the user-agent you sent, and whether the address you came from is inside a prefix its operator publishes — both run through this server's own classify_user_agent and is_verified_crawler_ip, on the same data a stranger can curl. Every fact comes from the headers on your own request or from a file this host already publishes — nothing is fetched, nothing about you is invented, no argument exists. Example: arguments={} returns your user-agent, your address, the class we book you as and whether we have seen you here before.

Endpoints

URLTransportStateLatencyChecked
https://www.pathwren.workers.dev/c/mcp-registry-official/mcp streamable-http answering 234 ms 0 min ago

Alternatives to AI Crawler Index

same job, measured the same way
Crawler Log Triage
by workers-pathwren-www

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} free no key

9 tools answering
Crawler IP Verifier - real Googlebot or fake
by workers-pathwren-www

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} free no key

9 tools answering
Metalift
by metalift-ai

Metalift MCP for AI agents: web search (2 credits), scrape, crawl, and map tools

57 installs/wk local only
AgentScrape
by hshintelligence

Pay-per-call web scraping for AI agents via x402 on Base USDC. Six tools, no signup.

6 tools answering
Crawlbit
by amati032-dev

Four free tools to check if AI engines can find, read and recognise a site. No API key.

33 installs/wk local only
WebLens
by weblens

Scrape, crawl, map and extract the web. Pay per call in USDC, no account or API key.

36 tools answering
CRW Web Scraper
by us

Open-source web scraper for AI agents with scrape, crawl, and map tools

local only
AI-First Scraper
by yubinkim444

Three MCP tools: fetch_page, fetch_pages_batch, search_web. Ad-free Markdown for AI agents.

151 installs/wk local only

AI Crawler Index — questions

Answers built from our own checks of this server.

What can AI Crawler Index do?
It exposes 9 tools, read directly from the server on our last check. Among them: changes_since, classify_user_agent, example, generate_robots_txt, is_verified_crawler_ip, list_crawlers and 3 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is AI Crawler Index working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 93 of 93 checks got a reply (100.0%), average response time 141 ms. The bar chart above shows every period we have measured.
How do I connect AI Crawler Index?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does AI Crawler Index need an API key?
No. AI Crawler Index completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 9 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is AI Crawler Index?
It answers our handshake in 141 ms on average, which is faster than 77% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.