dashboard learn amendments network sidechain pools whales tokens MPTs RWA RLUSD lending health methodology regulation about institutional XRP $1.0676 · self-sourced Ledger #106094279 · 4s

Connect an AI agent

Last verified: 2026-08-05

The xrpldashboard MCP server is live at https://mcp.xrpldashboard.com/mcp. Fifteen read-only tools over XRPL, every response wrapped in a proof-annotation envelope pointing back to the source of truth. Free, no account, no key. Public beta through 2026-09.

Public beta through 2026-09. Running on our own rippled full-history node from a Lenovo box in Indiana, exposed via a Cloudflare Tunnel. Session-scoped rate limit 600 tool calls / hour / session, enforced live — over-cap requests get HTTP 429 with a Retry-After hint. No throttle-then-degrade, no silent drops.

1 · The config

Claude Desktop supports remote MCP servers two ways. Either works — pick the one that matches your setup.

A · Settings → Connectors (recommended)

Open Claude Desktop → Settings → Connectors → Add custom connector.
Name: xrpldashboard
Remote MCP server URL: https://mcp.xrpldashboard.com/mcp
Auth: None (this endpoint is public.)
Save. The 15 tools appear under the xrpldashboard connector on your next new conversation.

B · Config file (mcp-remote bridge)

If your MCP client edits claude_desktop_config.json directly, or you're on a client that doesn't yet support remote MCP natively, the mcp-remote bridge works today:

{
  "mcpServers": {
    "xrpldashboard": {
      "command": "npx",
      "args": [
        "mcp-remote@latest",
        "https://mcp.xrpldashboard.com/mcp"
      ]
    }
  }
}

Restart your MCP client after saving. First run of npx mcp-remote downloads the bridge; subsequent runs are cached.

2 · Try it

Three prompts that exercise the shape of the server. One primitive read, one aggregation, and one moat demo — a signed daily snapshot you can verify without trusting us.

Primitive

"Using the xrpldashboard MCP server, get the current XRPL ledger stats. Show me the validated ledger index, close time, and build version."

→ Calls get_ledger_stats. Live rippled result, freshness ≤ 5min. Source = local_rippled in the proof envelope.

Aggregation

"Get me RLUSD's current on-XRPL supply and the 24-hour net flow. Explain the two numbers."

→ Calls get_rlusd_supply and get_rlusd_flow_24h. Second is finalized-window only — never a partial-day number reported as a full one. The freshness contract is on the envelope, not buried in a footnote.

Verify (the moat)

"Get today's signed snapshot from xrpldashboard, then verify its signature. Report the signing key, the pubkey it resolves to, and whether the envelope validates."

→ Calls get_signed_snapshot then verify_snapshot_signature. The tool re-verifies against the pinned pubkey at /.well-known/snapshots/pubkey.pem. If it validates, you now know the day's snapshot came from our key, not from something between you and us.

3 · What you get, and don't

15 read-only tools. Full inventory + freshness contract on the methodology page and machine-readable at /openapi.json.
Proof envelope on every response. Every result includes proof.source, proof.as_of, a freshness_contract, and a claims_ref you can dereference at /claims. When we can't promise strict, we return honest_partial with the reason.
No account. No key. No payment. Free for humans and identified agents at reasonable volume. Rate limit: 600 tool calls / hour / session, enforced.
What we don't do yet: write tools, custody, payments, off-chain scraping. The tools are read-only against XRPL and the on-XRPL RLUSD supply; the RLUSD Ethereum-side number is called out separately.

4 · When it breaks

HTTP 429. You hit the session limit. Wait the Retry-After seconds, or start a new client session (which starts a fresh bucket).
Endpoint unreachable. Live status at /health and /walker_health. Every rate-limit block writes a walker_health row so misuse patterns show up on the fleet health page, not silently on our side.
Something else looked wrong. Contact us. Bugs on this endpoint are the kind we want to hear about; the security page lists the disclosure preferences.