# Bot Crawl Checker — REST API endpoint `bot-crawl-checker`

Return which of 24 well-known crawlers (Googlebot, BingBot, GPTBot, ClaudeBot, PerplexityBot, AhrefsBot, Twitterbot and more) are allowed or blocked for a URL by the site's robots.txt, with the matching rule and user-agent group per bot.

- Category: seo
- MCP server: https://mcp.findutils.com/ (Streamable HTTP, no API keys, 120 req/min per IP)
- REST endpoint: POST https://api.findutils.com/api/tools/bot-crawl-checker/execute (no API keys, 60 req/min per IP)
- Network tool: fetches a fixed, hard-coded public upstream (never a private host).
- Reference page: https://findutils.com/api/bot-crawl-checker/
- Same tool on the other surface: https://findutils.com/mcp/bot-crawl-checker/

## Call the endpoint (verified example)

```bash
curl -X POST https://api.findutils.com/api/tools/bot-crawl-checker/execute \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://findutils.com/"
  }'

# Parameter schema
curl https://api.findutils.com/api/tools/bot-crawl-checker
```

## Input schema

| Argument | Type | Required | Description |
|---|---|---|---|
| `url` | string | yes | Public http(s) URL to check, e.g. "https://example.com/blog/post". |

Example arguments (verified):

```json
{
  "url": "https://findutils.com/"
}
```

OpenAPI 3.1 spec: https://findutils.com/api/openapi.json · Interactive docs: https://findutils.com/api/docs/

## Also an MCP tool

```bash
claude mcp add findutils --transport http https://mcp.findutils.com/
```

Then ask the client to call `findutils:bot_crawl_checker`. Full MCP reference: https://findutils.com/mcp/bot-crawl-checker/

---
Full catalog: GET https://api.findutils.com/api/tools · https://findutils.com/api/ · https://findutils.com/llms.txt