Remote MCP · Endpoint

AgentsIndex MCP server

No. AgentsIndex answered an MCP handshake 17 minutes ago.

UpLast checked 17 minutes ago

Server URL

https://agentsindex.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.agentsindex/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
397 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
The editors' index of AI-native software, from AI agents to the models and frameworks behind them.
Listing
From the official MCP registry (active).
Recent checks of AgentsIndex
CheckedResultHandshake
17 minutes agoHandshake completed397 ms
8 days agoHandshake completed366 ms
9 days agoHandshake completed309 ms
11 days agoHandshake completed382 ms
12 days agoHandshake completed364 ms
13 days agoHandshake completed335 ms
14 days agoHandshake completed339 ms
14 days agoHandshake completed349 ms
16 days agoHandshake completed376 ms
19 days agoHandshake completed409 ms
21 days agoHandshake completed477 ms
24 days agoHandshake completed453 ms
26 days agoHandshake completed328 ms
28 days agoHandshake completed409 ms

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

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