Is the Dcroyalty Xrplhub MCP server down?

mcp-registry/io.github.dcroyalty/xrplhub · v1.18.0

healthy
Last checked 2026-10-19 02:16 UTC · handshake 189ms

As of 2026-10-19 02:16 UTC, the Dcroyalty Xrplhub MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
3,731
outages (90d)
0
tools
21

Free XRPL wallet creditworthiness scores, ready-to-sign txjson for 35 XRPL actions, and more.

Install Dcroyalty Xrplhub MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http dcroyalty-xrplhub-mcp-server https://www.xrplhub.io/api/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "dcroyalty-xrplhub-mcp-server": {
      "type": "http",
      "url": "https://www.xrplhub.io/api/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (71/100)

C (71/100): 0 error(s), 6 warning(s) across 21 tool(s); ~4,613 tokens of tool definitions.
Scores higher than 7% of 15,343 MCP servers Glimind has audited.
Its tool list costs an agent ~4,613 tokens per session — more than 60% of servers.
71 → 71 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions87
Safety hints9
Token cost100
Client compatibility70
Protocol40
Reliability85
Stability34

What to fix (7)

21 of 21 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. How to fix →

Tools: check_domain_eligibility, check_mpt_risk, check_service_health, check_wallet_permissions, check_xrpl_score and 16 more

3 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: precheck_payment, prepare_batch_send, submit_grant_application

1 parameter(s) across 1 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. How to fix →

Tools: prepare_batch_send

Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.

Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →

Handshake + tools/list takes ~1,860 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.

In the last 30 days: 3 tool(s) removed and 9 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

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. How to fix →

Auto-fix: 17 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.dcroyalty%2Fxrplhub/fixes

check_domain_eligibility 1 change 
{
  "name": "check_domain_eligibility",
  "description": "Check whether an XRPL account holds a credential that satisfies a PermissionedDomain (XLS-80d) — the question every domain operator and every would-be participant actually asks before a real transaction. Live against a validated mainnet ledger. Eligibility is OR: any ONE accepted, unexpired credential matching the domain's AcceptedCredentials is enough. Params: wallet_address (r..., required), domain_id (64-hex DomainID, the PermissionedDomain ledger index, required). Free, no signup.",
  "inputSchema": {
    "type": "object",
    "required": [
      "wallet_address",
      "domain_id"
    ],
    "properties": {
      "domain_id": {
        "type": "string",
        "description": "The PermissionedDomain's ledger index — 64 hex characters"
      },
      "wallet_address": {
        "type": "string",
        "description": "XRPL classic address to check (starts with r)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
check_mpt_risk 1 change 
{
  "name": "check_mpt_risk",
  "description": "Get the risk view of one XLS-33 Multi-Purpose Token issuance before touching it: what the issuer CAN DO to a holder (clawback, freeze, require-auth, whether it's transferable at all) plus the issuer's XRPLScore. Free. For the full issuer picture — account age, xrp-ledger.toml-verified domain, credentials held (live ledger reads) — GET /api/x402/usdc/mpt/{id} pays $0.01 USDC on Base via x402. Every response states its source and returns 'unknown', never 'does not exist', when an issuance isn't fo",
  "inputSchema": {
    "type": "object",
    "required": [
      "issuance_id"
    ],
    "properties": {
      "issuance_id": {
        "type": "string",
        "description": "The MPTokenIssuanceID — 48 hexadecimal characters (XLS-33, 192-bit)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
check_service_health 1 change 
{
  "name": "check_service_health",
  "description": "Check whether the XRPLHub money path is working BEFORE you pay: database, Xaman, both x402 facilitators (t54 RLUSD + CDP USDC-on-Base), the on-ledger anchor config, the credential signing secret, and alerting. Returns overall \"ok\" | \"warn\" | \"down\" plus a per-component list. Poll this if a prior paid call failed. No params. Free, no signup.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

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/io.github.dcroyalty/xrplhub"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.dcroyalty/xrplhub"}) over MCP.

Passed

Largest tool definitions

Static 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:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.dcroyalty%2Fxrplhub.svg)](https://glimind.com/server/mcp-registry%2Fio.github.dcroyalty%2Fxrplhub?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fio.github.dcroyalty%2Fxrplhub?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.dcroyalty%2Fxrplhub.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.dcroyalty%2Fxrplhub.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.dcroyalty%2Fxrplhub?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:b8f36afea3d2fc0f…, first seen 2026-10-17, included at leaf 3226 of 24,365. Version history · verify what your client received.

Tools (21)

Compare: most reliable security servers · most reliable finance servers · most reliable data servers · most reliable other servers · most reliable payments servers

Know before your agent calls it

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.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

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"
    }
  }
}

FAQ

Is the Dcroyalty Xrplhub MCP server down right now?

As of 2026-10-19 02:16 UTC, the Dcroyalty Xrplhub MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Dcroyalty Xrplhub MCP server provide?

Dcroyalty Xrplhub MCP server advertises 21 tools, including check_domain_eligibility, check_mpt_risk, check_service_health, check_wallet_permissions, check_xrpl_score.

How do I install Dcroyalty Xrplhub MCP server?

Point your MCP client at this streamable-http endpoint: https://www.xrplhub.io/api/mcp

Is the Dcroyalty Xrplhub MCP server safe to connect to an AI agent?

Glimind scanned all 21 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.

Operator of Dcroyalty Xrplhub MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

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. Maintainers: alerts, deploy attestation and monthly reports.

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.

Feedback
Help us improve