Home / MCP registry index / io.github.Dcroyalty/xrplhub
XRPLHub — XRPLScore, MPT issuer risk & payment pre-checks
io.github.Dcroyalty/xrplhub in the official MCP registry.
Endpoint https://www.xrplhub.io/api/mcp. Source: github.com/Dcroyalty/XRPLHub.io.
The registry describes it as: XRPL wallet scores, wallet permissions, batch send, MPT risk, screening, pre-checks. Never signs.
We read its 21 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
issue_score_credential check_xrpl_score get_account_credentials get_issuer_credentials check_mpt_risk search_mpts get_issuer_mpts check_service_health verify_mpt_registry check_domain_eligibility submit_grant_application donate_to_community_fund screen_address_ofac get_monitoring_info verify_attestation get_lending_exposure get_underwriting_inputs precheck_payment check_wallet_permissions prepare_batch_send get_lending_history
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-dcroyalty-xrplhub)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.