# Answer Checkup MCP server

> Scan a website for AI crawler access, llms.txt, schema and metadata, and get a 0 to 100 AI readiness score.

- Listing: https://mcp.tc/i/answer-checkup
- Connect: use the server's own URL `https://answercheckup.com/mcp` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: none
- Category: [Marketing & SEO](https://mcp.tc/c/marketing-seo)
- Vendor: Answer Checkup
- Homepage: <https://answercheckup.com/>

## About

Answer Checkup runs a free technical scan of a website to show whether AI search engines can read it. It checks robots.txt rules for AI crawlers (GPTBot, OAI-SearchBot, ChatGPT-User, PerplexityBot, ClaudeBot, Google-Extended, CCBot), llms.txt, schema.org JSON-LD, title and meta description, content in raw HTML, and the sitemap. It returns a score from 0 to 100 and a grade.

The server is hosted at a streamable HTTP endpoint and needs no sign-in or API key. The scan result includes a link to unlock the detailed checks and prioritized fixes as a paid add-on.

## What it can do

- Check robots.txt rules for major AI crawlers
- Detect llms.txt and schema.org JSON-LD
- Review title, meta description and sitemap
- Verify content is present in raw HTML
- Get a 0 to 100 score with a grade

## Tools (3)

- `scan_site`: Scans a URL for AI crawler rules, llms.txt, schema, metadata, raw HTML content and sitemap…
- `get_report`: Paid: the Lite report for 29 USDC (default) or the Full report for 49 USDC (tier "full"), via x402 (scheme exact). (can modify or delete data)
- `get_scan_details`: Paid: 2.99 USDC via x402 (scheme exact), the same $2.99 scan details as on the website. (can modify or delete data)

## Example prompts

- "Scan example.com and tell me if AI crawlers can read it."
- "Run an AI readiness check on my company website."
- "Is GPTBot blocked by robots.txt on example.com?"
- "Does example.com have llms.txt and schema markup?"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http answer-checkup https://answercheckup.com/mcp
```

2. Start Claude Code and type `/mcp`. **answer-checkup** should show as connected.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **Answer Checkup** and paste this URL:

```url
https://answercheckup.com/mcp
```

3. Click **Add**. Its tools appear in the chat’s tools menu.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Answer%20Checkup&connectorUrl=https%3A%2F%2Fanswercheckup.com%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://answercheckup.com/mcp` and click **Add**.

3. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://answercheckup.com/mcp` as the server URL, then for authentication choose **No authentication**.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=answer-checkup&config=eyJ1cmwiOiJodHRwczovL2Fuc3dlcmNoZWNrdXAuY29tL21jcCJ9>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "answer-checkup": {
      "url": "https://answercheckup.com/mcp"
    }
  }
}
```

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=answer-checkup&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fanswercheckup.com%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"answer-checkup","type":"http","url":"https://answercheckup.com/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "answer-checkup": {
      "type": "http",
      "url": "https://answercheckup.com/mcp"
    }
  }
}
```

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "answer-checkup": {
      "serverUrl": "https://answercheckup.com/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add answer-checkup --url https://answercheckup.com/mcp
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.answer-checkup]
url = "https://answercheckup.com/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http answer-checkup https://answercheckup.com/mcp
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "answer-checkup": {
      "type": "http",
      "url": "https://answercheckup.com/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://answercheckup.com/mcp`.

## Recent changes

- 2026-10-28 05:41 UTC: 2 tools added. Source: automatic check. Worth a look: a new tool is marked destructive. Added: get\_report, get\_scan\_details.
- 2026-10-17 19:40 UTC: 1 tool changed. Source: automatic check. Changed: scan\_site.
- 2026-10-17 07:24 UTC: Tracking started: 1 tool read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/answer-checkup#history (Atom feed: https://mcp.tc/i/answer-checkup/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 0.2.0
- MCP protocol version: 2025-11-25
- Last checked: 2026-11-18 (reachable)
- Listed: 2026-10-17
- Updated: 2026-10-28

---
Source: https://mcp.tc/i/answer-checkup (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
