@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 MCP_BYPASS_KEY on the server to enable an opt-in bypass for friendlies / demos. The caller passes the matching key as _bypass_key in the tool args. Rate-limited at the proxy layer.

Use it

Locally via Claude Desktop (stdio)

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

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

Restart Claude Desktop. The 17 tools should appear with the prefix xrpl_. Ask Claude to "scan the wallet rXXX with XR-Sentinel" or "list permissioned domains on XRPL" and the tool calls flow through.

Remotely (HTTP/SSE)

Point any MCP client at https://mcp.xrpl-utilities.io/mcp. Same tool list, same auth model.

What you need to actually pay

To avoid 402 challenges on every call, your client needs to:

1. Hold a wallet on at least one of the supported rails:

an XRPL wallet with XRP (and optional RLUSD trustline) OR an EVM wallet with USDC on Base mainnet.

1. On each paid tool call, sign a payment matching one of the

accepts entries from a prior probe. XRPL rails take an XRPL Payment; the Base rail takes an EIP-3009 transferWithAuthorization.

1. Pass the base64-JSON-encoded envelope as payment_signature.

Reference implementations: x402-xrpl covers the XRPL rails. The official x402 package (with [evm] extras) covers the Base USDC rail. Both are useful as templates in any language.

Local dev

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

Point MCP Inspector at http://localhost:8080/mcp to walk through tool definitions interactively.

Releases

Releases are cut by tag push. The Release workflow builds, validates that package.json version matches the tag, publishes to npm with sigstore provenance, then mirrors the same version to the official MCP Registry via GitHub OIDC (no extra secrets needed).

npm version patch       # or minor / major
git push --follow-tags  # pushes commit + tag, CI does the rest

The published artifact appears at npmjs.com/package/@xrpl-utilities/mcp within ~90 seconds. Provenance attestation is visible on the package page as a green check. The MCP Registry entry lives at registry.modelcontextprotocol.io under the reverse-DNS name io.github.XRPL-Utilities/mcp.

License

MIT. Full portfolio at xrpl-utilities.com.