Remote MCP · Endpoint

Agent Tested MCP server

No. Agent Tested answered an MCP handshake 28 minutes ago.

UpLast checked 28 minutes ago

Server URL

https://agenttested.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.agenttested/agent-tested
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
450 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Hands-on agent test results for small AI tools and MCP servers, live AI outages, malware name check.
Listing
From the official MCP registry (active).
Recent checks of Agent Tested
CheckedResultHandshake
28 minutes agoHandshake completed450 ms
10 days agoHandshake completed495 ms
11 days agoHandshake completed1.01 s
11 days agoHandshake completed205 ms
13 days agoHandshake completed358 ms
14 days agoHandshake completed276 ms
15 days agoHandshake completed486 ms
16 days agoHandshake completed283 ms
17 days agoHandshake completed283 ms
19 days agoHandshake completed908 ms
21 days agoHandshake completed134 ms
24 days agoHandshake completed306 ms
26 days agoHandshake completed110 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 Agent Tested and makes no claim about it beyond what these checks measured.