Agent Watch MCP Server

by entradox Your server? Claim it

answering

Agent Watch is answering right now. Last checked 3 min ago. It exposes 8 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 51 days of history · worst day 0%

51 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

361 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 30

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

7 Oct 7 tool descriptions were rewritten aw_alerts, aw_census, aw_check_endpoint and 4 more

1 Oct 7 tool descriptions were rewritten aw_alerts, aw_census, aw_check_endpoint and 4 more

14 Sep 2 tools appeared read_skill, skills_list_tool

10 Sep 5 tool descriptions were rewritten aw_alerts, aw_census, aw_check_endpoint and 2 more

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

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

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/

Settings → Connectors → Add custom connector, then paste this address

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

{
  "servers": {
    "agent-watch": {
      "type": "http",
      "url": "https://agent-watch-api-production.up.railway.app/mcp/"
    }
  }
}

Available tools 8

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.

skill

read_skill

Read a product skill file by its skill:// URI. Args: uri: e.g. skill://<product>/<skill-name>/SKILL.md Get valid URIs from `skills_list_tool`.

skills

skills_list_tool

List this product's skills. Each entry carries the SKILL.md URI, its name and description, verbatim frontmatter, and a per-file sha256 manifest. Read a body with `read_skill`.

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	339 ms	3 min ago

Alternatives to Agent Watch

same job, measured the same way

Uk Flood Monitoring

by pipeworx-io

UK Environment Agency real-time flood-monitoring MCP.

44 tools answering

Execute bias-drift-monitor-mcp

by evozim

Premium agentic endpoint for bias-drift-monitor-mcp.

1 tools answering

Trustmodel MCP

by karlmehta

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

24 installs/wk local only

Scout Monitoring

by scoutapm

Scout Monitoring data for AI assistants: slow endpoints, traces, N+1 queries, and errors.

answering

Web

by rog0x

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

14 installs/wk local only

PageWatch - page-to-data extraction and change monitoring

by workers-zenith-ops-pagewatch

Extract prices, lists, tables, events from static pages and watch them for changes.

3 tools answering

Riveter

by codywatters

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

20 installs/wk answering

Scout Monitoring (local)

by scoutapm

Run Scout Monitoring's MCP tools locally with an API key: endpoints, traces, errors, N+1 insights.

675 installs/wk local only

Agent Watch — questions

Answers built from our own checks of this server.

What can Agent Watch do?

It exposes 8 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 and 2 more. 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 92 of 92 checks got a reply (100.0%), average response time 361 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 in the form 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 8 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 361 ms on average, which is faster than 41% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.