Remote MCP · Endpoint

Agent Account Index MCP server

No. Agent Account Index answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://agent-account-index.vercel.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.mycelium-being/agent-account-index
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
83 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Can an AI agent hold an account at a service? Verdict, owner of record, quoted terms clause.
Listing
From the official MCP registry (active).
Recent checks of Agent Account Index
CheckedResultHandshake
1 hour agoHandshake completed83 ms
19 hours agoHandshake completed53 ms
2 days agoHandshake completed560 ms
3 days agoHandshake completed58 ms
4 days agoHandshake completed70 ms
5 days agoHandshake completed451 ms
6 days agoHandshake completed59 ms
8 days agoHandshake completed47 ms
10 days agoHandshake completed457 ms
13 days agoHandshake completed59 ms
15 days agoHandshake completed591 ms
18 days agoHandshake completed560 ms
19 days agoHandshake completed654 ms
21 days agoHandshake completed63 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 Agent Account Index and makes no claim about it beyond what these checks measured.