NestDaddy

Botcard

com.whosthatbot/botcard · v2026-10-18.18

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

Connect Remote server

Terminal
claude mcp add --transport http botcard 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"
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://whosthatbot.com/mcp

Tools 4 found in our last check

  • 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.

  • 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.

  • 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.

  • 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 an…

Details

Endpointhttps://whosthatbot.com/mcp (Streamable HTTP)
First published19 Oct 2026
Last updated19 Oct 2026
Registry namecom.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.