XRPL-Utilities MCP server
online · 100% uptimeio.github.XRPL-Utilities/mcp·v0.2.243XRPL data tools for AI agents: wallet classifier, signals, RWA tracker, ETF flows. Pay via x402.
not scanned yet
0 stars213 downloads/wk
Reviews
Write oneNobody has reviewed XRPL-Utilities yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
XRPL-Utilities tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How XRPL-Utilities compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 89/100
- higher than 80% of 48,243 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 162 ms
- faster than 72% of 30,027 servers
- Downloads a week
- 213
- more than 76% of 12,306 servers with a package
Release history: 21 versions in the registry since 2026-09-06, latest 2026-11-04, typically several a day.
Install XRPL-Utilities in Claude Code, Cursor or VS Code
claude mcp add --transport http mcp https://mcp.xrpl-utilities.io/mcp
What the publisher says
From the XRPL-Utilities repository's README, as published. We do not edit it. Read it on GitHub
@xrpl-utilities/mcp
Model Context Protocol server for the XRPL-Utilities™ portfolio. Exposes the read endpoints of all six services as MCP tools so AI agents can discover and use them, either locally via stdio (Claude Desktop, MCP Inspector, etc.) or remotely via the hosted endpoint at mcp.xrpl-utilities.io.
Services covered
17 tools total, all read-only. Every paid call is settled via x402 v2 on the XRPL mainnet through the t54 facilitator.
Auth model
The MCP server is a stateless passthrough proxy. It does not hold wallets, manage user accounts, or subsidize calls.
For paid tools (every endpoint at $0.10 USD), the caller supplies a payment_signature argument: a base64-JSON-encoded x402 v2 payment header signing an XRPL Payment that matches one of the requirements returned by an unauthenticated probe. The server forwards it as the PAYMENT-SIGNATURE header on the underlying call.
If you don't supply payment_signature, the underlying service returns its real 402 Payment Required challenge listing three payment options: XRP and RLUSD on XRPL via the t54 facilitator, or USDC on Base mainnet via the Coinbase x402 facilitator. The MCP server passes that back to the LLM as a structured error so it can sign and retry against whichever rail its wallet supports.
Operators can set MCPBYPASSKEY on the server to enable an opt-in bypass for friendlies / demos. The caller passes the matching key as bypasskey in the tool args.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
XRPL-Utilities: common questions
- Is XRPL-Utilities MCP server safe?
- Yes, by our scan: it is graded A (89/100). Read the XRPL-Utilities safety report
- How do I install XRPL-Utilities?
- It runs remotely at mcp.xrpl-utilities.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does XRPL-Utilities need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is XRPL-Utilities maintained?
- The last commit was 45 days ago (2026-09-21). The latest release is v0.2.243.
- Is XRPL-Utilities up?
- 100% of our last 8 checks got an answer. We check remote servers about four times a day.
- How does XRPL-Utilities compare with other MCP servers?
- safety score 89/100 (higher than 80% of 48,243 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 162 ms (faster than 72% of 30,027 servers). Full comparison.