Remote MCP · Endpoint

com.cerberusindex/cerberus-index MCP server

No. com.cerberusindex/cerberus-index answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://cerberusindex.com/mcp

The last check completed an MCP handshake.

Registry name
com.cerberusindex/cerberus-index
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
205 ms
Tools exposed
20 tools
Uptime, last 30 days
94.7% from 19 checks
Described by its publisher as
XRPL token rug-checks, issuer reputation & AMM data for AI agents. Pay-per-call USDC via x402.
Listing
From the official MCP registry (active).
Recent checks of com.cerberusindex/cerberus-index
CheckedResultHandshake
1 hour agoHandshake completed205 ms
19 hours agoHandshake completed225 ms
2 days agoHandshake completed208 ms
3 days agoHandshake completed210 ms
4 days agoHandshake completed207 ms
5 days agoHandshake completed208 ms
6 days agoHandshake completed255 ms
8 days agoHandshake completed221 ms
10 days agoHandshake completed208 ms
13 days agoHandshake completed241 ms
15 days agoHandshake completed280 ms
17 days agoHandshake completed330 ms
19 days agoHandshake completed207 ms
21 days agoHandshake completed207 ms
23 days agoHandshake completed207 ms
25 days agoFailed - the request timed out—
27 days agoHandshake completed209 ms
28 days agoHandshake completed240 ms
29 days agoHandshake completed201 ms

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

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 com.cerberusindex/cerberus-index and makes no claim about it beyond what these checks measured.