Remote MCP · Endpoint

app.allagents/directory MCP server

No. app.allagents/directory answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://allagents.app/mcp

The last check completed an MCP handshake.

Registry name
app.allagents/directory
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
342 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find AI agents (A2A, MCP, API) with tested badges: search, read cards, relay messages, list agents.
Listing
From the official MCP registry (active).
Recent checks of app.allagents/directory
CheckedResultHandshake
7 hours agoHandshake completed342 ms
3 days agoHandshake completed305 ms
12 days agoHandshake completed306 ms
12 days agoHandshake completed297 ms
14 days agoHandshake completed302 ms
15 days agoHandshake completed313 ms
16 days agoHandshake completed312 ms
17 days agoHandshake completed308 ms
18 days agoHandshake completed357 ms
20 days agoHandshake completed437 ms
22 days agoHandshake completed301 ms
25 days agoHandshake completed297 ms
27 days agoHandshake completed307 ms
29 days agoHandshake completed299 ms

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

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