Agent Watch
REMOTE · AGENT-WATCH-API-PRODUCTION.UP.RAILWAY.APP
Monitoring for the agent economy — liveness, latency, trust scoring for MCP endpoints
Available components
Last scanned (21 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 16 Oct 2026.
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 743 tokens (~82/item across 9 items; 8 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 9 Oct 26 +2
- Stability: 0.87 → pass security
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +52
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Tool “aw_alerts” rewrote its description, which is the text the model reads security
- Tool “aw_census” rewrote its description, which is the text the model reads security
- Tool “aw_check_endpoint” rewrote its description, which is the text the model reads security
- Tool “aw_list_monitored” rewrote its description, which is the text the model reads security
- Tool “aw_watch” rewrote its description, which is the text the model reads security
- Tool “read_skill” rewrote its description, which is the text the model reads security
- Tool “skills_list_tool” rewrote its description, which is the text the model reads security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Stability: unverified → 0.80 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 1 Oct 26 −51
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.73 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Probed https://agent-watch-api-production.up.railway.app/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE2,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 618edc56941aa1165ddb080bf9f799eb7c1 |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agent-watch-api-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agent-watch-api-production.up.railway.app/mcp/ | Verified | 200 | |
| http (plaintext) | http://agent-watch-api-production.up.railway.app/mcp/ | HTTPS enforced | 301 | https://agent-watch-api-production.up.railway.app/mcp/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
aw_alerts ~54
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 present but exposes no named parameters.
No output schema declared.
No examples provided.
aw_census ~102
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 present but exposes no named parameters.
No output schema declared.
No examples provided.
aw_check_endpoint ~165
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)
| Name | Type | Req | Description |
|---|---|---|---|
| timeout | integer | – | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
aw_health ~37
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 present but exposes no named parameters.
No output schema declared.
No examples provided.
aw_list_monitored ~53
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 present but exposes no named parameters.
No output schema declared.
No examples provided.
aw_watch ~153
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
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – | |
| urls | array | yes | – |
| watch_token | string | – | – |
No output schema declared.
No examples provided.
read_skill ~59
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| uri | string | yes | – |
No output schema declared.
No examples provided.
skills_list_tool ~53
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 present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Agent Watch MCP server?
Agent Watch is a hosted endpoint at https://agent-watch-api-production.up.railway.app/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · agent-watch-api-production.up.railway.app
claude mcp add --transport http entradox-agent-watch 'https://agent-watch-api-production.up.railway.app/mcp/'
What is the Agent Watch MCP server?
Agent Watch is an MCP server listed in the public MCP registry as io.github.entradox/agent-watch. Monitoring for the agent economy, liveness, latency, trust scoring for MCP endpoints. This page covers its hosted endpoint (https://agent-watch-api-production.up.railway.app/mcp/).
Is the Agent Watch MCP server safe to use?
Agent Watch scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Agent Watch MCP server expose?
Agent Watch exposes 8 tools: aw_health, aw_check_endpoint, aw_census, aw_list_monitored, aw_alerts, and 3 more. Their descriptions and schemas cost roughly 676 tokens of context every time the server is loaded.
Does the Agent Watch MCP server require authentication?
No. We connected to Agent Watch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agent Watch MCP server still maintained?
Agent Watch is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.