Skip to content
Agentwatch logo

Agentwatch MCP server

Which MCP servers are Agentwatch's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to Agentwatch

Whose server it is
  • Registry namelighting.comiza/agentwatchverified in the MCP registry

The registry name sits under comiza.lighting. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools4
  • Server calls itselfagentwatch
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 163 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: Check whether AI crawlers actually receive your pages; Compare crawler access with robots.txt rules and firewall blocks; Test whether page text survives without JavaScript.
  • Checked on 1 of the 7 days it takes to judge reliability.

Once connected

  • For "Check whether AI crawlers actually receive your pages", the likely first call is check_site.
  • For "Compare crawler access with robots.txt rules and firewall blocks", the likely first call is check_site.
  • For "Test whether page text survives without JavaScript", the likely first call is check_site.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • What an agent can do with it3 of 3 use cases
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer490 ms
  • Space in an agent's context≈ 732 tokensthe definitions of all its tools (4), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Typed results0 of 4 toolsdeclared outputSchema: results come typed, read once
  • Not saying whether it only reads or can destroy: 4 of 4

What an agent can do with it

  • can do · Check whether AI crawlers actually receive your pages
  • can do · Compare crawler access with robots.txt rules and firewall blocks
  • can do · Test whether page text survives without JavaScript

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers4 tools · read 2026-10-26
  • 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…

  • 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…

  • 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…

  • 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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "agentwatch": {
      "type": "http",
      "url": "https://comiza.lighting/agentwatch/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http comiza https://comiza.lighting/agentwatch/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://comiza.lighting/agentwatch/mcp as a custom connector in the settings.

Other servers listed as Agentwatch's
  • lighting.comiza/hookjaranswers, 6 toolsverified in the MCP registry

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.