MCP.Market

xrpldashboard MCP server

online · 100% uptime
by xrpldashboard.com·com.xrpldashboard/xrpldashboard-mcp·v2.0.0
No reviews yet

Read-only XRP Ledger MCP tools with proof-annotation envelopes and signed daily snapshots.

A91/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A91/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed xrpldashboard yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

xrpldashboard tools (19)

write = sends, deletes, buys or posts
  • get_amendment_statusFree

    Return the current amendments state (enabled / in-flight / superseded / unrecognized-enabled) with `cross_check_status` derived from the responding node's feature-RPC vs Amendments ledger-object concurrence. Wrapped in the proof envelope.

  • get_amendmentsFree

    Return the amendments block with per-amendment vote tallies. Mirrors /amendments.json. Distinct from get_amendment_status (state-only) — this tool adds live vote counts vs UNL-threshold per amendment. Not third-party-naming. Wrapped in the proof envelope.

  • get_amm_poolFree

    Return the single ranked-pool row for one AMM account from the amm_ranked_pools snapshot. Raises when the account is absent (unranked, below thresholds, or newer than the last snapshot). Wrapped in the proof envelope.

  • get_amm_top_by_tvlFree

    Return the top-N ranked AMM pools by tvl_usd from the same snapshot /pools reads. NULL-tvl rows sort last. Wrapped in the proof envelope.

  • get_ledger_statsFree

    Return the last-validated ledger stats (index, close time, server state, load factor, complete range, build). Wrapped in the xrpldashboard proof envelope; envelope source is derived from the actual URL host (`local_rippled` for loopback / private LAN, `remote_rippled:<host>` otherwise) — never hardcoded.

  • get_mpt_snapshotFree

    Return the MPT snapshot dict (issuances / by_class / total). Not third-party-naming — no dispute_contact_url. Wrapped in the proof envelope.

  • get_poolsFree

    Return AMM pools ranked by TVL, broader list contract than get_amm_top_by_tvl (default limit=50 vs 10). Mirrors /pools.json. Same source snapshot (amm_ranked_pools). Third-party-naming — data payload includes `dispute_contact_url`. Wrapped in the proof envelope.

  • get_rlusd_flow_24hFree

    Return the last finalized 24h XRPL net-change from rlusd_supply_history. freshness_contract='finalized_only' is the machine-readable form of the R1/R2 finalized-window rule. cross_check_status derived from stored vs supply-diff pair. Wrapped in the proof envelope.

  • get_rlusd_supplyFree

    Return the current cross-chain RLUSD supply (Ethereum + XRPL) from the same PG mirror /rlusd reads. Honest-partial when either chain errored. Wrapped in the proof envelope.

  • get_rwa_familiesFree

    Return every rwa_family row with attributed pool count. Data payload includes `dispute_contact_url`. Wrapped in the proof envelope.

  • get_rwa_poolsFree

    Return every attributed RWA pool with provenance + TVL. Data payload includes `dispute_contact_url`. Wrapped in the proof envelope.

  • get_signed_snapshotFree

    Return the Ed25519-signed daily snapshot for `date_str` (ISO YYYY-MM-DD) wrapped in the proof envelope. Absence raises — the walker has not produced this date yet, or the date predates the chain start.

  • get_token_attestationFree

    Return the attestation tier (verified / self-described / null) for one (currency, issuer) pair. Data payload includes `dispute_contact_url` — first tool to name a third party. Wrapped in the proof envelope.

  • get_tokensFree

    Return the top-N tokens by trades_30d, joined against attestation tier + warning flags. Mirrors /tokens.json's data path (token_category_current JOIN token_facts). Third-party- naming — data payload includes `dispute_contact_url`. Wrapped in the proof envelope.

  • get_unl_statusFree

    Return the current UNL composition (both published lists, overlap, expiry-days). Honest-partial when a list fetch fails. Wrapped in the proof envelope.

  • get_whale_eventsFree

    Return the last N XRP-denominated whale events + tagged-watchlist events (trustset excluded). Same feed the homepage globe pulse reads. Wrapped in the proof envelope.

  • get_whale_watchlistFree

    Return the last N tagged-watchlist events (type='tagged'), floored at TAGGED_XRP_FLOOR_DROPS for XRP-denominated rows. Wrapped in the proof envelope.

  • get_whalesFree

    Return the whales_summary rollup cells (per-tier × per-filter body metadata). Mirrors /whales.json. Live stream on wss://wss.xrpldashboard.com — this tool returns generation stats + body length, not the live payload. Third-party-naming — data payload includes `dispute_contact_url`. Wrapped in the proof envelope.

  • verify_snapshot_signatureFree

    Stateless verification: re-derive the leaf hash, check the Ed25519 signature against the pinned pubkey, check the audit path against the claimed chain root. Accepts full MCP envelope or bare signed payload. Wrapped in the proof envelope.

Public scan report

scanner v0.1.10 · 2026-10-30 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 669ms20/20
  • Tool poisoning19 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityendpoint served from the registry-verified namespace domain8/10
Overall 91/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How xrpldashboard compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
91/100
higher than 85% of 48,255 servers
Tools
19
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
215 ms
faster than 61% of 30,031 servers

What its tools let an agent do: 19 read

Install xrpldashboard in Claude Code, Cursor or VS Code

claude mcp add --transport http xrpldashboard-mcp https://mcp.xrpldashboard.com/mcp?ref=anthropic
Add to Cursor

What the publisher says

From the xrpldashboard repository's README, as published. We do not edit it. Read it on GitHub

xrpldashboard

Public XRPL analytics with a built-in truth-audit system. Live at xrpldashboard.com.

What this is

Three things make this repo different from "another blockchain dashboard":

  1. Every headline number has a claim record. CLAIMS.yaml enumerates the public numeric claims across /rlusd, /whales, /coverage, and /analytics, each tied to its source function and freshness contract. scripts/claims_check.sh runs before pushes.
  2. A four-layer audit catches stale numbers before readers do. See docs/TRUTHAUDITDESIGN.md. Retro-tested against the last nine real incidents: 9 of 9 caught. The first live catch (an RLUSD partial-day bug) surfaced within hours instead of the 53 days it had previously gone unnoticed.
  3. Daily signed snapshots. Ed25519-signed, Merkle-chained. /signed-snapshots and .well-known/snapshots/.json let anyone verify a number as-of a date without trusting the site.

Quick links: /methodology · /signed-snapshots · docs/TRUTHAUDITDESIGN.md

Agent tier (MCP)

Live public MCP endpoint: https://mcp.xrpldashboard.com/mcp — streamable-HTTP, protocol version 2025-06-18, no auth. Fifteen read-only tools over XRPL and the on-XRPL RLUSD supply, every response wrapped in a proof-annotation envelope with source, asof, freshnesscontract, and a claims_ref back to /claims. Public beta through 2026-09.

Connect in 60 seconds — copy-paste config for Claude Desktop or any MCP client:

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

Or add it as a Custom Connector in Claude Desktop → Settings → Connectors with URL https://mcp.xrpldashboard.com/mcp and auth None. Full onboarding page (three sample prompts, honest limits, 429 shape): /connect.

  • Session rate limit: 600 tool calls / hour / session, enforced live (HTTP 429 + Retry-After on breach). See mcpsessionrate_limit.py.
  • Discovery manifest: /.well-known/agents.json · /llms.txt · /openapi.json.
  • Verifiable moat: getsignedsnapshot + verifysnapshotsignature — pin the Ed25519 pubkey at /.well-known/snapshots/pubkey.pem and verify a day's snapshot without trusting us.
  • Backing infra: our own rippled full-history node (Ubuntu box in Indiana → Cloudflare Tunnel), source at mcpserver.py and mcptools_*.py.

Design doc: docs/AGENTTIERDESIGN.md.

Pages

37 public pages, organized as:

  • Money flow: /whales, /pools, /tokens, /token/, /mpts, /mpt/, /rlusd, /lending
  • Institutional & regulatory: /institutional, /regulation, /rwa, /credentials, /amendments, /sidechain
  • Coverage & audit: /coverage, /methodology, /signed-snapshots, /verify, /walker-health, /health
  • Reader tools: /check, /wallet/, /network, /learn, /price-data, /help/already-sent-money
  • Trust & meta: /about, /security, /privacy, /terms, /subprocessors, /contact

Architecture

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

xrpldashboard: common questions

Is xrpldashboard MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the xrpldashboard safety report
How do I install xrpldashboard?
It runs remotely at mcp.xrpldashboard.com. 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 xrpldashboard need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is xrpldashboard maintained?
The last commit was 5 days ago (2026-10-30). The latest release is v2.0.0.
Is xrpldashboard up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does xrpldashboard compare with other MCP servers?
safety score 91/100 (higher than 85% of 48,255 servers); tools 19 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.