Esc

Ask what any website is

From your code or your agent, with the evidence behind every answer.

Free during launch: 300 credits a month, no card. REST, MCP and an agent skill.

cURL
curl "https://api.checkanysite.com/v1/sites/wikipedia.org?checks=ai" \
  -H "Authorization: Bearer $CHECKANYSITE_API_KEY"
Python
from checkanysite import CheckAnySite

client = CheckAnySite()  # Reads the key from CHECKANYSITE_API_KEY.

site = client.sites.retrieve("wikipedia.org", checks=["ai"])
JavaScript
const url = 'https://api.checkanysite.com/v1/sites/wikipedia.org?checks=ai';
const response = await fetch(url, {
  headers: {
    Authorization: `Bearer ${process.env.CHECKANYSITE_API_KEY}`,
  },
});
const site = await response.json();
Response 200
{
  "domain": "wikipedia.org",
  "checks": [
    "ai"
  ],
  "scannedAt": "2026-11-10T09:30:06.000Z",
  "complete": true,
  "ai": {
    "level": "none",
    "builders": [],
    "patterns": []
  },
  "resultUrl": "https://checkanysite.com/site/wikipedia.org?focus=ai"
}

Give your agent CheckAnySite

Choose your client, paste one line, then ask about any website: “Was this site built with AI?”

Claude Code

Run this in a terminal, then ask Claude about any website: “Was this site built with AI?”

Terminal
claude mcp add --transport http checkanysite https://checkanysite.com/mcp \
  --header "Authorization: Bearer $CHECKANYSITE_API_KEY"

Cursor

Add the server with one click, then put your key in its place, or add it to ~/.cursor/mcp.json yourself.

Add to Cursor
~/.cursor/mcp.json
{
  "mcpServers": {
    "checkanysite": {
      "url": "https://checkanysite.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

VS Code

Add the server with one click, then put your key in its place, or add it to .vscode/mcp.json; Copilot’s agent mode can then use it.

Add to VS Code
.vscode/mcp.json
{
  "servers": {
    "checkanysite": {
      "type": "http",
      "url": "https://checkanysite.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Claude app

In Claude (desktop or web), open Settings › Connectors › Add custom connector, paste this address and choose Connect. Sign in to CheckAnySite and choose Allow: no key to copy.

Connector URL
https://checkanysite.com/mcp

Windsurf

Add the server to Windsurf’s MCP settings, then refresh its MCP list.

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "checkanysite": {
      "serverUrl": "https://checkanysite.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Codex CLI

Add the server to Codex’s settings; it reads your key from CHECKANYSITE_API_KEY.

~/.codex/config.toml
[mcp_servers.checkanysite]
url = "https://checkanysite.com/mcp"
bearer_token_env_var = "CHECKANYSITE_API_KEY"

Any MCP client

Connect over Streamable HTTP and send your key in the Authorization header. Clients that can’t send headers can add ?key= to the address instead.

Connection
URL:     https://checkanysite.com/mcp
Type:    Streamable HTTP
Header:  Authorization: Bearer YOUR_API_KEY

Using an agent without MCP? Give it the skill, and it learns when and how to call us.

Terminal
npx skills add https://checkanysite.com

Names and logos belong to their owners; they show which tools work with us.

Three ways to use it

Each way gives the same answers and uses the same key and credits.

  • REST API

    JSON over HTTPS. Get our stored result for a site, or scan it and read the result.

    https://api.checkanysite.com/v1Quickstart
  • MCP server

    Eight tools for Claude, Cursor, VS Code and any other MCP client.

    https://checkanysite.com/mcpConnect a client
  • Agent skill

    One SKILL.md file that teaches an agent without MCP when and how to call the API.

    npx skills add https://checkanysite.comInstall the skill

Credits

Free during launch. Ask only for the checks you need, and spend credits only on those.

Free during launch

300 credits a month

  • Every endpoint, the MCP server and the skill
  • Up to 5 keys sharing them, each with its own limit
  • 60 requests a minute per key, 25 new scans a day
  • No card
Get a free API key
From a stored result
1–2 credits a check, 3 for every check
With a new scan
1–6 credits a check, 15 for every check
Free
Polling a scan, reading your usage, and requests that fail
More credits
Building something bigger? Ask on your usage page and tell us what you’re building. Extra credits are free during launch.

Credits reset on the first of each month (UTC). We’ll email you at least 7 days before paid plans start or your credits change. Credits lists every check’s price.

What you can count on

Evidence, never a verdict

Every finding includes the line, header or record it came from. We never call a site safe or a scam, and what you build on us shouldn’t either.

Measured, and published

Every time we change what we look for, we test our AI builder detection on 2,263 sites whose makers we know, and publish every run, misses included (the full test).

Polite scanning

Our scanner identifies itself, follows robots.txt, and reuses recent results instead of fetching a site again.

Questions

Is it free?

Yes, during launch. Every account gets 300 credits a month with no card required, and more on request from its usage page. Paid plans will come later, and a free allowance will remain. We’ll email every account at least 7 days before paid plans start.

What does a request cost?

You pay for the checks you ask for: 1–2 credits each from a stored result, or 1–6 with a new scan, and never more than every check at once (3 stored, 15 with a new scan). Polling a scan, reading your usage and requests that fail are free.

Which agents can use it?

Any client that supports MCP over Streamable HTTP, including Claude Code, the Claude app, Cursor, VS Code with Copilot, Windsurf and Codex. Agents without MCP can use the agent skill.

Can I scan any website?

Any public domain. Our scanner identifies itself and follows robots.txt, so a site that asks bots to stay away gets a result from outside records only. We don’t check adult websites.

What do you keep about my requests?

The credits each key uses per day, and each request (its time, path, status and credits) for 7 days, so you can see them under Usage in your account. Scan results are public on our site, like every scan.

Can I build a product on it?

Yes, within the terms. Show findings as signals with their evidence, never as a verdict about a site, and keep the license of any popularity list you republish.

Your key is a minute away

Sign in with GitHub, Google or an email link. No card, no plan to pick.