Cited AI crawler registry (training, search or user fetch) plus robots.txt checks. No fetching.
Connect Remote server
claude mcp add --transport http botcard https://whosthatbot.com/mcp
{
"mcpServers": {
"botcard": {
"url": "https://whosthatbot.com/mcp"
}
}
}
{
"servers": {
"botcard": {
"type": "http",
"url": "https://whosthatbot.com/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://whosthatbot.com/mcp
Tools 4 found in our last check
check_robotsMatch 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.
list_crawlersList 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.
get_crawlerReturn 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.
suggest_robotsWrite 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 an…
Details
| Endpoint | https://whosthatbot.com/mcp (Streamable HTTP) |
| First published | 19 Oct 2026 |
| Last updated | 19 Oct 2026 |
| Registry name | com.whosthatbot/botcard |
More search and web servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
