Remote MCP · Endpoint

AgentWatch MCP server

No. AgentWatch answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://agentwatch.agentwatch.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.workers.agentwatch.agentwatch/agentwatch
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
518 ms
Tools exposed
21 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Read-only watchtower for AI agents on-chain: decoded receipts, plan vs execution, Safe audits.
Listing
From the official MCP registry (active).
Recent checks of AgentWatch
CheckedResultHandshake
1 hour agoHandshake completed518 ms
1 day agoHandshake completed591 ms
4 days agoHandshake completed582 ms
6 days agoHandshake completed519 ms
9 days agoHandshake completed776 ms
11 days agoHandshake completed425 ms
13 days agoHandshake completed1.21 s
15 days agoHandshake completed554 ms
17 days agoHandshake completed606 ms
19 days agoHandshake completed564 ms
21 days agoHandshake completed326 ms
22 days agoHandshake completed600 ms
23 days agoHandshake completed604 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with AgentWatch and makes no claim about it beyond what these checks measured.