Remote MCP · Endpoint

List API For Agents MCP server

No. List API For Agents answered an MCP handshake 55 minutes ago.

UpLast checked 55 minutes ago

Server URL

https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/list-api-for-agents/mcp

The last check completed an MCP handshake.

Registry name
io.github.sadri-dridi/list-api-for-agents
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
15 ms
Tools exposed
31 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
List a public API where AI agents discover tools, after a bounded readiness check.
Listing
From the official MCP registry (active).
Recent checks of List API For Agents
CheckedResultHandshake
55 minutes agoHandshake completed15 ms
9 hours agoHandshake completed13 ms
1 day agoHandshake completed15 ms

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

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