mcp-registry/lighting.comiza/agentwatch · v1.0.0
As of 2026-10-27 05:10 UTC, the Comiza Agentwatch MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 13.2 hours.
Check if ChatGPT, Claude and Perplexity can reach, read and quote a website.
Point your MCP client at this streamable-http endpoint: https://comiza.lighting/agentwatch/mcp
4 of 4 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Flighting.comiza%2Fagentwatch/fixes
{
"name": "check_site",
"description": "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 ",
"inputSchema": {
"type": "object",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"description": "Domain or URL, for example example.com"
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Check whether AI assistants can read a site"
}{
"name": "list_ai_crawlers",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true
},
"title": "List the AI crawlers and what each one is for"
}{
"name": "verify_crawler_visit",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"ip",
"user_agent"
],
"properties": {
"ip": {
"type": "string",
"description": "Source address from the log line."
},
"user_agent": {
"type": "string",
"description": "User-Agent from the same line."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Check whether a crawler visit was genuine"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/lighting.comiza/agentwatch"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/lighting.comiza/agentwatch"}) over MCP.
verify_signed_request ~286 tokensverify_crawler_visit ~205 tokenscheck_site ~190 tokenslist_ai_crawlers ~129 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Flighting.comiza%2Fagentwatch?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Flighting.comiza%2Fagentwatch?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Flighting.comiza%2Fagentwatch.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Flighting.comiza%2Fagentwatch.svg :target: https://glimind.com/server/mcp-registry%2Flighting.comiza%2Fagentwatch?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:6443714a696384ee…, first seen 2026-10-17, included at leaf 3783 of 77,539. Version history · verify what your client received.
Compare: most reliable web servers · most reliable knowledge servers · most reliable security servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-27 05:10 UTC, the Comiza Agentwatch MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 13.2 hours.
Comiza Agentwatch MCP server advertises 4 tools, including check_site, list_ai_crawlers, verify_crawler_visit, verify_signed_request.
Point your MCP client at this streamable-http endpoint: https://comiza.lighting/agentwatch/mcp
Glimind scanned all 4 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.