XRPL Utilities

What XRPL-Utilities MCP server does

XRPL-Utilities exposes read endpoints from several XRPL-Utilities services as MCP tools for AI agents. The portfolio covers wallet activity analysis, normalized XRPL events, macro and DEX telemetry, permissioned assets, real-world assets, ETF relationships, account statements, and composite market briefings.

All 46 tools are read-only. XR-Sentinel classifies wallet activity and provides signals, label context, narratives, and an origin-verification check. XR-Pulse supplies recent events and market views such as whale movements, exchange flows, Ripple counterparties, escrow schedules, RLUSD distribution, token health, and RWA summaries. Other services cover settlement series, permissioned-domain operators, issuer flows, ETF correlations, address statements, and desk-level market posture.

How it works

The package acts as a stateless passthrough proxy. It does not hold wallets, create user accounts, or fund requests. A client can start it locally with stdio or connect to the hosted MCP endpoint at https://mcp.xrpl-utilities.io/mcp.

Free tools can be called directly. Paid tools return an x402 PaymentRequired object when no valid payment is supplied. The client signs an accepted payment option and retries the same call using _meta["x402/payment"]; the server forwards that payload to the underlying service. Clients that cannot set MCP metadata can send a base64-encoded payment payload through the payment_signature argument. Successful responses include settlement information in _meta["x402/payment-response"].

Payment rails include XRP or RLUSD on XRPL and USDC on Base mainnet. Deep-dive and feed calls cost $0.10 per call, while XR-Pulse data tools cost $0.01 per call.

Setup and configuration

For Claude Desktop, install the package on demand with npx and select stdio transport:

{
  "mcpServers": {
    "xrpl-utilities": {
      "command": "npx",
      "args": ["-y", "@xrpl-utilities/mcp", "--transport", "stdio"]
    }
  }
}

Restart the client after adding the entry. Remote clients can use the hosted /mcp endpoint. For local development, install dependencies, build the package, and start HTTP transport on port 8080:

npm install
npm run build
node dist/index.js --transport http --port 8080

MCP Inspector can connect to http://localhost:8080/mcp. MCP_BYPASS_KEY provides an optional operator-controlled bypass for demos or trusted callers. STRICT_VALIDATE=1 changes manifest validation failures from warnings to startup drift failures.

Tools and capabilities

• Classify XRPL wallet activity and inspect historical signals.
• Verify that an x402 seller controls the advertised XRPL account.
• Query XRPL events, whale flows, exchange activity, escrow, RLUSD, and token health.
• Inspect XRPL macro metrics, settlement data, and DEX pair volumes.
• Explore permissioned domains, operators, issuers, jurisdictions, and activity.
• Track RWA supply and flows, ETF relationships, account statements, and desk briefings.

Limitations and notes

The tools only read data; they do not submit XRPL transactions. Paid access requires a wallet on at least one supported payment rail and a signed payment for each paid call. XRPL payments use an XRPL Payment, while the Base option uses EIP-3009 transferWithAuthorization. The server forwards requests and does not custody payment funds or wallet credentials.

An operator bypass key is not part of the public tool schema and requires a client that permits the extra argument, such as a raw JSON-RPC request. The hosted endpoint limits failed bypass-key guesses separately from normal free and paid traffic.