Other · Remote MCP server
Agentwatch
Check if ChatGPT, Claude and Perplexity can reach, read and quote a website.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
lighting.comiza/agentwatch- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-08-09
- Updated
- 2026-08-09
- Publisher
- lighting.comiza · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via the domain comiza.lighting · how
- Listed under
- OpenAI MCP servers, Perplexity MCP servers
- Website
- comiza.lighting/agentwatch/
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://comiza.lighting/agentwatch/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- agentwatch 1.0.0 · protocol 2025-06-18
- Tools discovered
- 4:
check_site,verify_crawler_visit,verify_signed_request,list_ai_crawlers - Checked on
- 2026-10-05
How to connect Agentwatch
Agentwatch is a remote MCP server: there is nothing to install. Its endpoint is https://comiza.lighting/agentwatch/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from lighting.comiza
| Server | Runs |
|---|---|
| HookjarPublic webhook inboxes for agents. Receive OAuth redirects, payment callbacks and CI notifications. | Remote · HTTPLive check: ✓ handshake |
More other servers
| Server | Runs |
|---|---|
| AgentUtility Model RouterMCP server for the @agentutility model-router cluster - pay-per-call x402 tools, no API keys, USDC… | Local · stdio |
| AgentUtility ProoflayerMCP server for the @agentutility prooflayer cluster - pay-per-call x402 tools, no API keys, USDC… | Local · stdio |
| AgentUtility SynthforgeMCP server for the @agentutility synthforge cluster - pay-per-call x402 tools, no API keys, USDC… | Local · stdio |
| AgentVaultDiscover, verify, and connect to AI agents with E2E encrypted messaging and trust scoring. | Local · stdio |
| AgentWork Outcome RouterWhen your agent is stuck, call route_blocked_outcome for one evidence-backed completion route-free. | Remote · HTTPLive check: ✓ handshake |
| AgentWork OutcomesBuy a finished outcome through services, agents, marketplaces, humans, tools, or swarms. | Remote · HTTPLive check: ✓ handshake |
| AgentWorld DiscoveryRead-only AgentWorld discovery: join instructions, activities, public stats, and Reason Lab. | Remote · HTTPLive check: ✓ handshake |
| AgentWorld DiscoveryRead-only discovery for AgentWorld WORLD, A2A onboarding and the separate MARKET service economy. | Remote · HTTPLive check: ✓ handshake |