Agent Watch
v0.1.0Monitoring for the agent economy — liveness, latency, trust scoring for MCP endpoints
Endpoint health
online- Last checked
- 11/20/2026, 4:16:34 AM
- Latency
- 105 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:io.github.entradox%2Fagent-watch
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"io.github.entradox/agent-watch": {
"url": "https://agent-watch-api-production.up.railway.app/mcp/"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
8 shown · authentication unknown
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.
Schema valid · SHA-256 511eab1801ad…
View input schema
{ "type": "object", "properties": {}, "title": "aw_alertsArguments" }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.
Schema valid · SHA-256 a5288d93a6cf…
View input schema
{ "type": "object", "properties": {}, "title": "aw_censusArguments" }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)
Connections
streamable-http
https://agent-watch-api-production.up.railway.app/mcp/