mcp-registry/com.xrpldashboard/xrpldashboard-mcp · v1.29.0
As of 2026-10-17 05:24 UTC, the Xrpldashboard MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 9 outages in 90 days, with a median recovery of 9 minutes.
Read-only XRP Ledger MCP tools with proof-annotation envelopes and signed daily snapshots.
Claude Code
claude mcp add --transport http xrpldashboard-mcp-server https://mcp.xrpldashboard.com/mcp?ref=anthropic
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"xrpldashboard-mcp-server": {
"type": "http",
"url": "https://mcp.xrpldashboard.com/mcp?ref=anthropic"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
19 of 19 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones.
10 parameter(s) across 9 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call.
Handshake + tools/list takes ~1,975 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 9 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.xrpldashboard%2Fxrpldashboard-mcp/fixes
{
"name": "get_amendment_status",
"description": "Return the current amendments state (enabled / in-flight /\n superseded / unrecognized-enabled) with `cross_check_status`\n derived from the responding node's feature-RPC vs Amendments\n ledger-object concurrence. Wrapped in the proof envelope.",
"inputSchema": {
"type": "object",
"title": "get_amendment_statusArguments",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_amendments",
"description": "Return the amendments block with per-amendment vote tallies.\n Mirrors /amendments.json. Distinct from get_amendment_status\n (state-only) — this tool adds live vote counts vs UNL-threshold\n per amendment. Not third-party-naming. Wrapped in the proof\n envelope.",
"inputSchema": {
"type": "object",
"title": "get_amendmentsArguments",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_amm_pool",
"description": "Return the single ranked-pool row for one AMM account from the\n amm_ranked_pools snapshot. Raises when the account is absent\n (unranked, below thresholds, or newer than the last snapshot).\n Wrapped in the proof envelope.",
"inputSchema": {
"type": "object",
"title": "get_amm_poolArguments",
"required": [
"amm_account"
],
"properties": {
"amm_account": {
"type": "string",
"title": "Amm Account"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.xrpldashboard/xrpldashboard-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.xrpldashboard/xrpldashboard-mcp"}) over MCP.
verify_snapshot_signature ~142 tokensget_token_attestation ~138 tokensget_whales ~132 tokensget_ledger_stats ~131 tokensget_tokens ~131 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.xrpldashboard%2Fxrpldashboard-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.xrpldashboard%2Fxrpldashboard-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.xrpldashboard%2Fxrpldashboard-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.xrpldashboard%2Fxrpldashboard-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fcom.xrpldashboard%2Fxrpldashboard-mcp?ref=badge :alt: MCP agent-readiness
Compare: most reliable other servers · most reliable data servers · most reliable security servers · most reliable blockchain servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-17 05:24 UTC, the Xrpldashboard MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 9 outages in 90 days, with a median recovery of 9 minutes.
Xrpldashboard MCP server advertises 19 tools, including get_amendment_status, get_amendments, get_amm_pool, get_amm_top_by_tvl, get_ledger_stats.
Point your MCP client at this streamable-http endpoint: https://mcp.xrpldashboard.com/mcp?ref=anthropic
Glimind scanned all 19 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.