_ registry / mcp http-sse · checked 1m ago

xrpldashboard-mcp

https://mcp.xrpldashboard.com

Registry code: 6d59559195d74883

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.xrpldashboard.com/mcp?ref=anthropic
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is xrpldashboard-mcp live?
Yes — it answered the hub's last check (checked 1m ago). It answered 100% of checks over the last 30 days.
Is xrpldashboard-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does xrpldashboard-mcp have?
19 tools: get_signed_snapshot, verify_snapshot_signature, get_amm_pool, get_token_attestation, get_rwa_pools, get_tokens, get_rlusd_supply, get_whales, ….
Is xrpldashboard-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.4%· all time 99.4%

latency
552ms

last good check

priced tools
0

of 19 tools

_ answered our checks, 90 days 353 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
topic
crypto & onchain onchain analytics
used for
  • get xrp ledger amendment status
  • list top amm pools by tvl
  • get rlusd supply
  • track xrp whale events
  • verify a signed ledger snapshot
takes → gives
text → data
tools
19 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 19 tools
15 open 4 never probed 15 of 19 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_rwa_pools reads open 14h ago

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

    mcp-tool

    {
  "type": "object",
  "title": "get_rwa_poolsArguments",
  "properties": {}
}
    arguments 5 lines
  • get_tokens reads open 14h ago

    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.

    mcp-tool

    {
  "type": "object",
  "title": "get_tokensArguments",
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 100
    }
  }
}
    arguments 11 lines
  • get_rlusd_supply reads open 17h ago

    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.

    mcp-tool

    {
  "type": "object",
  "title": "get_rlusd_supplyArguments",
  "properties": {}
}
    arguments 5 lines
  • get_whales reads open 10h ago

    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.

    mcp-tool

    {
  "type": "object",
  "title": "get_whalesArguments",
  "properties": {}
}
    arguments 5 lines
  • get_ledger_stats reads open 1m ago

    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.

    mcp-tool

    {
  "type": "object",
  "title": "get_ledger_statsArguments",
  "properties": {}
}
    arguments 5 lines
  • get_unl_status reads open 14h ago

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

    mcp-tool

    {
  "type": "object",
  "title": "get_unl_statusArguments",
  "properties": {}
}
    arguments 5 lines
  • get_whale_watchlist reads open 10h ago

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

    mcp-tool

    {
  "type": "object",
  "title": "get_whale_watchlistArguments",
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 25
    }
  }
}
    arguments 11 lines
  • get_mpt_snapshot reads open 1m ago

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

    mcp-tool

    {
  "type": "object",
  "title": "get_mpt_snapshotArguments",
  "properties": {}
}
    arguments 5 lines
  • get_pools reads open 1m ago

    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.

    mcp-tool

    {
  "type": "object",
  "title": "get_poolsArguments",
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 50
    }
  }
}
    arguments 11 lines
  • get_rwa_families reads open 17h ago

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

    mcp-tool

    {
  "type": "object",
  "title": "get_rwa_familiesArguments",
  "properties": {}
}
    arguments 5 lines
  • get_rlusd_flow_24h reads open 17h ago

    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.

    mcp-tool

    {
  "type": "object",
  "title": "get_rlusd_flow_24hArguments",
  "properties": {}
}
    arguments 5 lines
  • get_whale_events reads open 10h ago

    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.

    mcp-tool

    {
  "type": "object",
  "title": "get_whale_eventsArguments",
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 25
    }
  }
}
    arguments 11 lines
  • get_amendments reads open 6h ago

    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.

    mcp-tool

    {
  "type": "object",
  "title": "get_amendmentsArguments",
  "properties": {}
}
    arguments 5 lines
  • get_amendment_status reads open 6h ago

    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.

    mcp-tool

    {
  "type": "object",
  "title": "get_amendment_statusArguments",
  "properties": {}
}
    arguments 5 lines
  • get_amm_top_by_tvl reads open 6h ago

    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.

    mcp-tool

    {
  "type": "object",
  "title": "get_amm_top_by_tvlArguments",
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 10
    }
  }
}
    arguments 11 lines
  • get_signed_snapshot reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "title": "get_signed_snapshotArguments",
  "required": [
    "date_str"
  ],
  "properties": {
    "date_str": {
      "type": "string",
      "title": "Date Str"
    }
  }
}
    arguments 13 lines
  • verify_snapshot_signature reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "title": "verify_snapshot_signatureArguments",
  "required": [
    "envelope"
  ],
  "properties": {
    "envelope": {
      "type": "object",
      "title": "Envelope",
      "additionalProperties": true
    }
  }
}
    arguments 14 lines
  • get_amm_pool reads unknown 3h ago

    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.

    mcp-tool

    {
  "type": "object",
  "title": "get_amm_poolArguments",
  "required": [
    "amm_account"
  ],
  "properties": {
    "amm_account": {
      "type": "string",
      "title": "Amm Account"
    }
  }
}
    arguments 13 lines
  • get_token_attestation reads unknown 3h ago

    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.

    mcp-tool

    {
  "type": "object",
  "title": "get_token_attestationArguments",
  "required": [
    "currency",
    "issuer"
  ],
  "properties": {
    "issuer": {
      "type": "string",
      "title": "Issuer"
    },
    "currency": {
      "type": "string",
      "title": "Currency"
    }
  }
}
    arguments 18 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 6d59559195d74883.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/6d59559195d74883/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/6d59559195d74883/badge.svg)](https://brick.blue/agent/6d59559195d74883?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.