# Botcard (remote · whosthatbot.com)

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

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

## Components

- remote · `whosthatbot.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-whosthatbot-botcard/whosthatbot.md), [page](https://verifymcp.io/servers/com-whosthatbot-botcard/whosthatbot)

## Channel facts

- Endpoint: `https://whosthatbot.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2026-10-18.18`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-22.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 777 tokens (~194/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Botcard MCP server?

Botcard is a hosted endpoint at https://whosthatbot.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-whosthatbot-botcard": {
      "type": "remote",
      "url": "https://whosthatbot.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-whosthatbot-botcard --url 'https://whosthatbot.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-whosthatbot-botcard:
    url: "https://whosthatbot.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-whosthatbot-botcard": {
      "Transport": "http",
      "Url": "https://whosthatbot.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-whosthatbot-botcard -t streamable-http -u 'https://whosthatbot.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-whosthatbot-botcard": {
      "type": "http",
      "url": "https://whosthatbot.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-22 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 71, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-19 (score 70)

First indexed and scored.

## MCP tools (4)

### `check_robots` (~129 tokens)

Check a pasted robots.txt

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.

Input parameters:

- `ids` (array): Card ids to check, such as gptbot. Omit to check every card.
- `path` (string): Path to test, starting with /. Defaults to /.
- `robots_txt` (string, required): The robots.txt file contents. Not a URL.

### `list_crawlers` (~58 tokens)

List crawler cards

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` (~71 tokens)

Get one crawler card

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.

Input parameters:

- `id` (string, required): Card id, such as gptbot or google-extended.

### `suggest_robots` (~157 tokens)

Write a cited robots.txt

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.

Input parameters:

- `allow` (array): Kinds to Allow, such as search.
- `block` (array): Kinds to Disallow, such as training.
- `path` (string): Path the Allow or Disallow names. Defaults to /.
- `policy` (string): Same choice in words, such as "allow search, block training".

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-whosthatbot-botcard/whosthatbot#diagnostics

## Score history

- 2026-10-22: 72
- 2026-10-21: 71
- 2026-10-20: 71
- 2026-10-19: 70

## Common questions

### What is the Botcard MCP server?

Botcard is an MCP server listed in the public MCP registry as com.whosthatbot/botcard. Cited AI crawler registry (training, search or user fetch) plus robots.txt checks. No fetching. This page covers its hosted endpoint (https://whosthatbot.com/mcp).

### Is the Botcard MCP server safe to use?

Botcard scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Botcard MCP server expose?

Botcard exposes 4 tools: check_robots, list_crawlers, get_crawler, suggest_robots. Their descriptions and schemas cost roughly 415 tokens of context every time the server is loaded.

### Does the Botcard MCP server require authentication?

No. We connected to Botcard without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Botcard MCP server still maintained?

Botcard is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://whosthatbot.com/mcp
- Website: https://whosthatbot.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-whosthatbot-botcard/whosthatbot.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-whosthatbot-botcard/whosthatbot.json
- HTML version of this page: https://verifymcp.io/servers/com-whosthatbot-botcard/whosthatbot