Xrpl Utilities

@XRPL-Utilities

About Xrpl Utilities

MCP server for the XRPL-Utilities portfolio. 11 tools across four services:

#xrpl #ripple #xrp #rlusd #x402 #payments #on-chain #blockchain #ai-agents #finance

Config

Add this server to your MCP-compatible client using the configuration below.

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

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Xrpl Utilities?

Xrpl Utilities is a pay-per-call MCP server that supplies XRPL on-chain data to AI agents. It exposes eleven tools backed by four backend services (XR‑Sentinel, XR‑Pulse, XR‑Telemetry, XR‑Trust). Every paid call settles on XRPL mainnet via x402 v2 — no API keys, no subscriptions, and no rate‑limit‑then‑upsell.

How to use Xrpl Utilities?

Install in Claude Desktop by adding the server configuration to claude_desktop_config.json with the command npx -y @xrpl-utilities/mcp --transport stdio. For remote use, point any MCP client to https://mcp.xrpl-utilities.io/mcp with streamable‑http transport. Paid tools require a payment_signature argument containing an x402 v2 payment header.

Key features of Xrpl Utilities

Wallet classification via XR‑Sentinel with activity scores and signals.
Normalized signal feed (XR‑Pulse) mixing news, whale activity, and permissioned events.
XR‑Telemetry macro snapshot of XRP supply, liquidity, and active float.
XR‑Trust directory for permissioned‑asset domains and credential issuers.
Pay‑per‑call model settled inline on XRPL mainnet.
Stateless passthrough proxy; holds no wallets and runs no proprietary logic.

Use cases of Xrpl Utilities

Classify any XRPL wallet by on‑chain activity pattern and get a reasoning narrative.
Monitor a time‑ordered stream of XRP‑related news, whale payments, and permissioned‑domain events.
Retrieve a one‑shot macro snapshot of XRPL total supply, AMM‑locked XRP, and DEX orderbook depth.
Enumerate all PermissionedDomain objects on XRPL and drill down into specific domains.
Explore credential issuer aggregations and permissioned‑DEX trade economics.

FAQ from Xrpl Utilities

How does payment work without API keys?

Every paid tool requires a payment_signature argument: a base64‑JSON‑encoded x402 v2 header signing an XRPL Payment. The server forwards it as a PAYMENT‑SIGNATURE HTTP header. $0.10 USD (in XRP or RLUSD) lands on the operator wallet per successful call, settled inline via the t54 facilitator.

What tools are available?

Eleven tools with the xrpl_ prefix: xrpl_sentinel_scan, xrpl_sentinel_scan_history, xrpl_pulse_recent_events, xrpl_telemetry_snapshot, xrpl_telemetry_get_quote, xrpl_telemetry_get_status, xrpl_telemetry_get_results, xrpl_trust_list_domains, xrpl_trust_get_domain, xrpl_trust_credential_issuers, and xrpl_trust_recent_events.

Can I use Xrpl Utilities remotely without installing the server?

Yes. Any MCP client can connect to https://mcp.xrpl-utilities.io/mcp using streamable‑http (with SSE). The same tools and auth model apply; no installation is needed.

Is the server stateless?

Yes. The MCP server holds no wallets, takes no cut, and runs no proprietary logic. It is a thin MIT‑licensed proxy that translates MCP tool calls into HTTP requests against the four underlying

Frequently asked questions

How does payment work without API keys?

Every paid tool requires a `payment_signature` argument: a base64‑JSON‑encoded x402 v2 header signing an XRPL Payment. The server forwards it as a `PAYMENT‑SIGNATURE` HTTP header. $0.10 USD (in XRP or RLUSD) lands on the operator wallet per successful call, settled inline via the t54 facilitator.

What tools are available?

Eleven tools with the `xrpl_` prefix: `xrpl_sentinel_scan`, `xrpl_sentinel_scan_history`, `xrpl_pulse_recent_events`, `xrpl_telemetry_snapshot`, `xrpl_telemetry_get_quote`, `xrpl_telemetry_get_status`, `xrpl_telemetry_get_results`, `xrpl_trust_list_domains`, `xrpl_trust_get_domain`, `xrpl_trust_credential_issuers`, and `xrpl_trust_recent_events`.

Can I use Xrpl Utilities remotely without installing the server?

Yes. Any MCP client can connect to `https://mcp.xrpl-utilities.io/mcp` using streamable‑http (with SSE). The same tools and auth model apply; no installation is needed.

Is the server stateless?

Yes. The MCP server holds no wallets, takes no cut, and runs no proprietary logic. It is a thin MIT‑licensed proxy that translates MCP tool calls into HTTP requests against the four underlying