Remote MCP · Endpoint

AgentWatchr MCP server

Yes, as of 4 days ago: the server returned an HTTP error.

DownLast checked 4 days ago

Server URL

https://agentwatchr.com/mcp

The last check failed: the server returned an HTTP error.

Registry name
com.agentwatchr/evidence-index
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
4 tools
Uptime, last 30 days
90.9% from 11 checks
Described by its publisher as
Read-only agent identity index with provenance, historical evidence and explained coverage.
Listing
From the official MCP registry (active).
Recent checks of AgentWatchr
CheckedResultHandshake
4 days agoFailed - the server returned an HTTP error—
7 days agoHandshake completed677 ms
16 days agoHandshake completed933 ms
17 days agoHandshake completed3.85 s
19 days agoHandshake completed1.77 s
20 days agoHandshake completed2.65 s
21 days agoHandshake completed5.14 s
22 days agoHandshake completed2.86 s
22 days agoHandshake completed705 ms
24 days agoHandshake completed658 ms
27 days agoHandshake completed672 ms

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

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 AgentWatchr and makes no claim about it beyond what these checks measured.