Remote MCP · Endpoint

Agent Radar MCP server

No. Agent Radar answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://agent-radar.zation1.workers.dev/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.zation/agent-radar
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
238 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search, inspect, recommend, and explain rated AI tools through Agent Radar.
Listing
From the official MCP registry (active).
Recent checks of Agent Radar
CheckedResultHandshake
1 hour agoHandshake completed238 ms
9 days agoHandshake completed262 ms
10 days agoHandshake completed488 ms
11 days agoHandshake completed222 ms
12 days agoHandshake completed324 ms
14 days agoHandshake completed247 ms
14 days agoHandshake completed211 ms
15 days agoHandshake completed231 ms
17 days agoHandshake completed279 ms
19 days agoHandshake completed289 ms
21 days agoHandshake completed372 ms
24 days agoHandshake completed165 ms
26 days agoHandshake completed247 ms
28 days agoHandshake completed423 ms

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

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