# Agentwatch (remote · comiza.lighting)

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

- Trust score: 67/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-19

## Components

- remote · `comiza.lighting`: 67/100 (this document), [markdown](https://verifymcp.io/servers/lighting-comiza-agentwatch/agentwatch-mcp.md), [page](https://verifymcp.io/servers/lighting-comiza-agentwatch/agentwatch-mcp)

## Channel facts

- Endpoint: `https://comiza.lighting/agentwatch/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-19.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 638 tokens (~159/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### Claude

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

### Codex

```toml
[mcp_servers.lighting-comiza-agentwatch]
url = "https://comiza.lighting/agentwatch/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lighting-comiza-agentwatch": {
      "type": "remote",
      "url": "https://comiza.lighting/agentwatch/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lighting-comiza-agentwatch --url https://comiza.lighting/agentwatch/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  lighting-comiza-agentwatch:
    url: "https://comiza.lighting/agentwatch/mcp"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-18 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-16 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-14 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-12 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-11 (score 63, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-10 (score 62, −1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: pass → fail
- [functional improvement] Stability: unverified → 0.03
- [functional] New tool “verify_crawler_visit”
- [functional] New tool “verify_signed_request”

### 2026-08-09 (score 63)

First indexed and scored.

## MCP tools (4)

### `check_site` (~125 tokens)

Check whether AI assistants can read a 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.

Input parameters:

- `url` (string, required): Domain or URL, for example example.com

### `verify_crawler_visit` (~133 tokens)

Check whether a crawler visit was genuine

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.

Input parameters:

- `ip` (string, required): Source address from the log line.
- `user_agent` (string, required): User-Agent from the same line.

### `verify_signed_request` (~183 tokens)

Verify an HTTP Message Signature on a 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.

Input parameters:

- `headers` (object, required): Request headers, including Signature-Input, Signature and Signature-Agent.
- `method` (string): HTTP method of the captured request, uppercase. It is part of the signature base whenever the signature covers @method, so a wrong value fails verification. Defaults to GET.
- `url` (string, required): Full URL as requested; the signature covers it.

### `list_ai_crawlers` (~85 tokens)

List the AI crawlers and what each one is for

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/lighting-comiza-agentwatch/agentwatch-mcp#diagnostics

## Score history

- 2026-08-19: 67
- 2026-08-18: 67
- 2026-08-17: 66
- 2026-08-16: 66
- 2026-08-15: 65
- 2026-08-14: 65
- 2026-08-13: 64
- 2026-08-12: 64
- 2026-08-11: 63
- 2026-08-10: 62
- 2026-08-09: 63

## Links

- Remote endpoint: https://comiza.lighting/agentwatch/mcp
- Website: https://comiza.lighting/agentwatch/
- Changelog RSS feed: https://verifymcp.io/servers/lighting-comiza-agentwatch/agentwatch-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/lighting-comiza-agentwatch/agentwatch-mcp.json
- HTML version of this page: https://verifymcp.io/servers/lighting-comiza-agentwatch/agentwatch-mcp