Agent Watch MCP Server

by entradox Your server? Claim it

answering

Agent Watch is answering right now. Last checked 3 min ago. It exposes 6 tools.

Monitoring for the agent economy — liveness, latency, trust scoring for MCP endpoints

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 5 days of history · worst day 0%

5 days agonow

100.0%

Uptime 24h

93 of 93 checks

Tools

read from the server

356 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 9

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 7 September 2026. No other catalogue keeps this.

8 Sep a tool description was rewritten aw_watch

8 Sep a tool changed the parameters it asks for aw_watch

7 Sep 6 tool descriptions were rewritten aw_alerts, aw_census, aw_check_endpoint and 3 more

7 Sep a tool changed version

Agent Watch does not always answer

Over the last week it answered 74.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add agent-watch --transport http https://agent-watch-api-production.up.railway.app/mcp/

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "agent-watch": {
      "url": "https://agent-watch-api-production.up.railway.app/mcp/"
    }
  }
}

~/.codex/config.toml

[mcp_servers.agent-watch]
url = "https://agent-watch-api-production.up.railway.app/mcp/"

.cursor/mcp.json

{
  "mcpServers": {
    "agent-watch": {
      "url": "https://agent-watch-api-production.up.railway.app/mcp/"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "agent-watch": {
      "url": "https://agent-watch-api-production.up.railway.app/mcp/"
    }
  }
}

Available tools 6

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

alerts

aw_alerts

Show dead endpoints across the monitored registry (alive=false). Returns up to 500 dead endpoints with names. Use after aw_census or aw_list_monitored to get the actionable dead list. Read-only.

census

aw_census

Full-census summary of the official MCP registry: 7,454 endpoints probed with real MCP handshakes. Returns alive/dead/unknown counts and percentages. States: alive = MCP initialize succeeded; dead = no answer; unknown = answered but auth-gated (401/403/402) or redirecting — liveness unprovable without credentials. Use to quantify how much of the MCP ecosystem is actually reachable.

endpoint

aw_check_endpoint

Probe an MCP or HTTP-402 endpoint now and get its trust verdict. Performs a real MCP initialize handshake (not a ping), measures p50/p95 latency, counts tools, hashes the tool schema (for drift detection), and checks RFC 9728 auth metadata. Returns: alive (bool), name, tool_count, latency_p50_ms, tool_schema_hash, auth_metadata_present, and error detail when dead. Use before wiring any new MCP server into your client. Args: url: the MCP or HTTP-402 endpoint URL to probe (e.g. https://host/mcp/) timeout: probe timeout in seconds (default 30)

health

aw_health

Liveness check for the Agent Watch API. Returns ok, service name, and version. Call this first to verify connectivity before using other tools.

monitored

aw_list_monitored

List all endpoints in the Agent Watch census with their registry names. Returns count and the full endpoint list (URLs). Combine with aw_alerts to find which of these are dead. Read-only.

watch

aw_watch

Add endpoints to your personal watchlist (probed immediately, then every 6h). Plan-limited by the email used at checkout: free 5, Builder ($19/mo) 50, Team ($99/mo) 500 endpoints. Alerts fire on alive→dead transitions and tool-schema drift. Already-watched URLs are returned without re-probing. Args: email: the email your subscription is under (free tier works too) urls: endpoint URLs to add to your watchlist watch_token: issued at registration, delivered in your onboarding email — required

Endpoints

URL	Transport	State	Latency	Checked
https://agent-watch-api-production.up.railway.app/mcp/	streamable-http	answering	332 ms	3 min ago

Alternatives to Agent Watch

same job, measured the same way

Trustmodel MCP

by karlmehta

Score any AI for trust across 10 dimensions; evaluate, monitor & govern LLMs and agents.

36 installs/wk local only

Web

by rog0x

Web scraping, search, monitoring, and HTML-to-markdown for AI agents

27 installs/wk local only

Riveter

by codywatters

MCP server for Riveter's enrichment, scraping, and monitoring API

80 installs/wk answering

MCP Kafka

by dockndevai

Apache Kafka monitoring & management for AI agents (with consumer lag) — governed.

76 installs/wk local only

Okareo

by okareo

Simulation, evaluation and monitoring for voice agents.

answering

Safeship

by safeship

API monitoring from your editor. Checks the JSON your endpoints return, not just the status code.

answering

LastPing

by lastping

Monitoring that agents set up for themselves — cron jobs, CI/CD pipelines and AI agent runs.

36 tools answering

Docker MCP Server

by friendlygeorge

MCP server for Docker — containers, health checks, Compose, logs, monitoring for AI agents

70 installs/wk local only

Agent Watch — questions

Answers built from our own checks of this server.

What can Agent Watch do?

It exposes 6 tools, read directly from the server on our last check. Among them: aw_alerts, aw_census, aw_check_endpoint, aw_health, aw_list_monitored, aw_watch. 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 Agent Watch working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 93 of 93 checks got a reply (100.0%), average response time 356 ms. The bar chart above shows every period we have measured.

Is Agent Watch still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

How do I connect Agent Watch?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Agent Watch need an API key?

No. Agent Watch completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Agent Watch?

It answers our handshake in 356 ms on average, which is faster than 46% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.