Remote MCP · Endpoint

XRPL.to Token Analytics MCP server

No. XRPL.to Token Analytics answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.xrpl.to/v1/mcp

The last check completed an MCP handshake.

Registry name
io.github.xrplto/xrpl-to
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
2.19 s
Tools exposed
89 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
XRP Ledger tokens, AMM pools, NFTs, accounts and transactions: prices, holders, trades and history
Listing
From the official MCP registry (active).
Recent checks of XRPL.to Token Analytics
CheckedResultHandshake
1 hour agoHandshake completed2.19 s
9 days agoHandshake completed369 ms
10 days agoHandshake completed379 ms
11 days agoHandshake completed265 ms
12 days agoHandshake completed417 ms
14 days agoHandshake completed495 ms
14 days agoHandshake completed408 ms
15 days agoHandshake completed376 ms
17 days agoHandshake completed288 ms
19 days agoHandshake completed295 ms
21 days agoHandshake completed279 ms
24 days agoHandshake completed573 ms
26 days agoHandshake completed514 ms

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

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