Remote MCP · Endpoint

Asteroid XRPL Hub MCP server

No. Asteroid XRPL Hub answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://asteroidxrpl.com/mcp

The last check completed an MCP handshake.

Registry name
com.asteroidxrpl/asteroid-xrpl-hub
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
542 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read-only XRPL tools for ASTEROID: identity, market, supply, liquidity, escrows, holders, AMM quotes
Listing
From the official MCP registry (active).
Recent checks of Asteroid XRPL Hub
CheckedResultHandshake
6 hours agoHandshake completed542 ms
9 days agoHandshake completed1.01 s
10 days agoHandshake completed909 ms
11 days agoHandshake completed848 ms
12 days agoHandshake completed832 ms
14 days agoHandshake completed332 ms
14 days agoHandshake completed941 ms
15 days agoHandshake completed689 ms
17 days agoHandshake completed563 ms
19 days agoHandshake completed858 ms
22 days agoHandshake completed693 ms
24 days agoHandshake completed836 ms
26 days agoHandshake completed958 ms
28 days agoHandshake completed1.09 s

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

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