Botcard MCP Server

by whosthatbot Your server? Claim it

answering

Botcard is answering right now. Last checked 2 min ago. It exposes 4 tools.

Cited AI crawler registry (training, search or user fetch) plus robots.txt checks. No fetching.

Uptime history 7 days of history

7 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

189 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

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

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add botcard --transport http https://whosthatbot.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://whosthatbot.com/mcp

~/.codex/config.toml

[mcp_servers.botcard]
url = "https://whosthatbot.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "botcard": {
      "url": "https://whosthatbot.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "botcard": {
      "type": "http",
      "url": "https://whosthatbot.com/mcp"
    }
  }
}

Available tools 4

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

crawler

get_crawler

Return one card by id, including the vendor source URL and the date it was read. This tool does not fetch any website. Do not send url, host, target, website, robots_url, or fetch.

crawlers

list_crawlers

List the AI crawler robots.txt tokens in this dataset. Each row names the vendor page the summary was checked against. This tool does not fetch any website. Do not send url, host, target, website, robots_url, or fetch.

robots

check_robots

Match a robots.txt file the caller pastes against Botcard's AI crawler tokens, using RFC 9309. Each row is allow or disallow plus that token's vendor stance. This tool does not fetch any website. Do not send url, host, target, website, robots_url, or fetch.

suggest

suggest_robots

Write a robots.txt from this dataset for the kinds you allow or block. Each group cites the vendor page. effect request_only means the vendor does not say the crawler obeys that line. control_token is not training. The file has no User-agent: * group. This tool does not fetch any website. Do not send url, host, target, website, robots_url, or fetch.

Endpoints

URL	Transport	State	Latency	Checked
https://whosthatbot.com/mcp	streamable-http	answering	191 ms	2 min ago

Alternatives to Botcard

same job, measured the same way

Robots Txt AI Crawler Audit

by jmshinhwa

Checks robots.txt line by line and says what each AI crawler token actually controls - training, AI

21 installs/wk local only

UAParse

by workers-mike-tusa-uaparse

Parse a User-Agent: browser, OS, device, plus bot, search crawler, AI crawler and AI agent flags.

1 tools answering

402registry

by 402registry

Does an AI crawler see your site? Free registry lookup, x402 pricing; checks paid in USDC on Base.

4 tools answering

Matchstick

by astralchemist

Checks a site build: sitemaps, structured data, robots.txt and what crawlers see.

189 installs/wk local only

AI Visibility

by lastminutedealshq

AI-search-visibility tools: check crawler access, generate llms.txt, lint robots.txt, census data.

4 tools answering

AI Visibility Checker

by krisdiallo

AI visibility checker: GPTBot vs OAI-SearchBot, robots.txt audit, raw-HTML schema. 165 crawlers.

local only

Citevana AI visibility tools

by citevana

Free MCP tools for AI-search visibility: crawler checks, page audits, and llms.txt generation.

4 tools answering

CrawlEyes MCP Server

by waiky-github

Web scraping & search for AI agents: extract, SearXNG search, rerank, robots compliance. No API key.

82 installs/wk local only

Botcard — questions

Answers built from our own checks of this server.

What can Botcard do?

It exposes 4 tools, read directly from the server on our last check. Among them: check_robots, get_crawler, list_crawlers, suggest_robots. 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 Botcard working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 189 ms. The bar chart above shows every period we have measured.

How do I connect Botcard?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Botcard need an API key?

No. Botcard completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Botcard?

It answers our handshake in 189 ms on average, which is faster than 81% 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.