Remote MCP · Endpoint

AgentIndex MCP server

No. AgentIndex answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp-agentindex.craftyour.site/mcp

The last check completed an MCP handshake.

Registry name
io.github.cognivis/agentindex
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
788 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Trust scores and on-chain payment receipts for x402 services.
Listing
From the official MCP registry (active).
Recent checks of AgentIndex
CheckedResultHandshake
2 hours agoHandshake completed788 ms
2 days agoHandshake completed719 ms
4 days agoHandshake completed692 ms
5 days agoHandshake completed837 ms
7 days agoHandshake completed733 ms
8 days agoHandshake completed768 ms
9 days agoHandshake completed725 ms
12 days agoHandshake completed731 ms
13 days agoHandshake completed726 ms
15 days agoHandshake completed829 ms
17 days agoHandshake completed755 ms
18 days agoHandshake completed729 ms
19 days agoHandshake completed758 ms
20 days agoHandshake completed932 ms
20 days agoHandshake completed775 ms
21 days agoHandshake completed757 ms
23 days agoHandshake completed753 ms

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

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