Remote MCP · Endpoint

N9T2 XRPL Agent Gateway MCP server

No. N9T2 XRPL Agent Gateway answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://x402.n9t2.com/mcp

The last check completed an MCP handshake.

Registry name
com.n9t2/xrpl-agent-gateway
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
881 ms
Tools exposed
22 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Agent-native XRPL infrastructure: 19 paid MCP tools, x402 USDC on Base, non-custodial XRPL actions.
Listing
From the official MCP registry (active).
Recent checks of N9T2 XRPL Agent Gateway
CheckedResultHandshake
1 hour agoHandshake completed881 ms
2 days agoHandshake completed813 ms
5 days agoHandshake completed767 ms
7 days agoHandshake completed796 ms
9 days agoHandshake completed785 ms
11 days agoHandshake completed870 ms
13 days agoHandshake completed810 ms
15 days agoHandshake completed781 ms
17 days agoHandshake completed890 ms
19 days agoFailed - the server returned an HTTP error—
20 days agoHandshake completed846 ms
21 days agoHandshake completed814 ms
23 days agoHandshake completed1.30 s

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 12 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 N9T2 XRPL Agent Gateway and makes no claim about it beyond what these checks measured.