mcpbeat Sign in

Agentwatch MCP Server

answering

Agentwatch is answering right now. Last checked 9 min ago. It exposes 4 tools.

Check if ChatGPT, Claude and Perplexity can reach, read and quote a website.

Uptime history 85 days of history · worst day 77%
85 days agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
285 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Agentwatch every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add agentwatch --transport http https://comiza.lighting/agentwatch/mcp
Settings → Connectors → Add custom connector, then paste this address
https://comiza.lighting/agentwatch/mcp
~/.codex/config.toml
[mcp_servers.agentwatch]
url = "https://comiza.lighting/agentwatch/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "agentwatch": {
      "url": "https://comiza.lighting/agentwatch/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "agentwatch": {
      "type": "http",
      "url": "https://comiza.lighting/agentwatch/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

verify
verify_crawler_visit
Given the IP address and User-Agent from a log line, say whether that visit really came from the crawler it claims to be. Checks the address against the vendor's own published ranges where they exist, and falls back to forward-confirmed reverse DNS. On one ordinary server's logs, 14% of requests claiming to be Googlebot were not Google. Use this before anyone writes a firewall rule based on a user agent string, because that string is a claim and not proof.
verify_signed_request
Verify a Web Bot Auth signature (RFC 9421, Ed25519) on a captured request. Unlike an address check, this proves who sent that exact request: it fetches the signer's published key directory, rebuilds the signature base from the covered components, and checks the signature. Use it when a request carries Signature-Input and Signature headers. Returns 'unsigned' when they are absent, and 'cannot_verify' rather than 'invalid' whenever the limitation is on our side.
crawlers
list_ai_crawlers
The robots.txt tokens used by the major assistants, separated by purpose: the ones that build the index answers come from, the ones that fetch a page live when a person asks, and the ones that only collect training data. Blocking the last group costs no visibility; blocking the first two removes a site from the answers. Use this before writing or editing a robots.txt.
site
check_site
Fetch a website the way ChatGPT, Claude, Perplexity, Google and Copilot fetch it, and report what stops them. Checks robots.txt per crawler with the deciding line number, makes real requests as each crawler to catch firewall and CDN rules that robots.txt cannot express, and measures whether the page carries readable text without JavaScript. Use this before advising anyone on why their site does not appear in AI answers: the usual cause is one of these three and none of them are visible from the outside.

Endpoints

URLTransportStateLatencyChecked
https://comiza.lighting/agentwatch/mcp streamable-http answering 234 ms 9 min ago

Alternatives to Agentwatch

same job, measured the same way
A
Agentready
by puluceno

Can ChatGPT, Claude and Perplexity reach and read a website? Score, problems found and fixes.

1 tools answering
Rankli: AI search readiness
by rankli-www

Checks if ChatGPT, Claude, Gemini and Perplexity can reach and read a website, with ranked fixes.

1 tools answering
AI Readiness
by epistemedeus

Check if a website is visible to AI search (ChatGPT, Perplexity, Claude) and get per-gap fixes.

local only
TraceFlow Lens
by traceflowlabs-lens

SEO and GEO audit: check if a site can be read and cited by Google, ChatGPT, Perplexity and Claude.

answering
AI Readiness (hosted)
by samedaydesk

Check if a website is visible to AI search (ChatGPT, Perplexity, Claude). No install.

7 tools answering
GEO Scanner
by agundur

Checks whether a website is readable and citable by AI systems (ChatGPT, Claude, Perplexity, etc.)

2 tools answering
CueScout
by telman03

Check if ChatGPT or Perplexity names a brand for a buying question, and if AI bots can read a site.

14 tools answering
Nodpick AI readiness
by nodpick

Free AI-readiness audit: can ChatGPT, Claude and Perplexity read and cite a site? Fix snippets.

5 tools answering

Agentwatch — questions

Answers built from our own checks of this server.

What can Agentwatch do?
It exposes 4 tools, read directly from the server on our last check. Among them: check_site, list_ai_crawlers, verify_crawler_visit, verify_signed_request. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Agentwatch working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 285 ms. The bar chart above shows every period we have measured.
How do I connect Agentwatch?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Agentwatch need an API key?
No. Agentwatch completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Agentwatch?
It answers our handshake in 285 ms on average, which is faster than 50% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.