Agent Watch

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

Should I use this

Quality & Safety

B
Description quality
98%
Schema completeness
49%
Naming quality
83%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~1,105Tokens (tool definitions)
~329 BTypical response size
Moderate attention impact (0.86% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

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

Remote endpoints

https://agent-watch-api-production.up.railway.app/mcp/streamable-http

What it can do

Tool inventory

Tools (8)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢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.

Input Schema

{
  "type": "object",
  "properties": {},
  "title": "aw_healthArguments"
}
🟢aw_check_endpoint(url, timeout)

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)

Input Schema

{
  "type": "object",
  "properties": {
    "url": {
      "title": "Url",
      "type": "string"
    },
    "timeout": {
      "default": 30,
      "title": "Timeout",
      "type": "integer"
    }
  },
  "required": [
    "url"
  ],
  "title": "aw_check_endpointArguments"
}
🟢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.

Input Schema

{
  "type": "object",
  "properties": {},
  "title": "aw_censusArguments"
}
🟢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.

Input Schema

{
  "type": "object",
  "properties": {},
  "title": "aw_list_monitoredArguments"
}
🟢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.

Input Schema

{
  "type": "object",
  "properties": {},
  "title": "aw_alertsArguments"
}
🟡aw_watch(email, urls, watch_token)

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

Input Schema

{
  "type": "object",
  "properties": {
    "email": {
      "title": "Email",
      "type": "string"
    },
    "urls": {
      "items": {},
      "title": "Urls",
      "type": "array"
    },
    "watch_token": {
      "default": "",
      "title": "Watch Token",
      "type": "string"
    }
  },
  "required": [
    "email",
    "urls"
  ],
  "title": "aw_watchArguments"
}
🟢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`.

Input Schema

{
  "type": "object",
  "properties": {},
  "title": "skills_list_toolArguments"
}
🟢read_skill(uri)

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`.

Input Schema

{
  "type": "object",
  "properties": {
    "uri": {
      "title": "Uri",
      "type": "string"
    }
  },
  "required": [
    "uri"
  ],
  "title": "read_skillArguments"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded8 tools
verifiedversion not recorded8 tools
verifiedversion not recorded8 tools
verifiedversion not recorded8 tools
verifiedversion not recorded8 tools
verifiedversion not recorded8 tools