Home / MCP registry index / io.github.XRPL-Utilities/mcp

XRPL-Utilities

io.github.XRPL-Utilities/mcp in the official MCP registry. Endpoint https://mcp.xrpl-utilities.io/mcp. Source: github.com/XRPL-Utilities/xrpl-utilities-mcp.

The registry describes it as: XRPL data tools for AI agents: wallet classifier, signals, RWA tracker, ETF flows. Pay via x402.

We read its 64 tools on 2026-11-03. 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 about every two weeks.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code
claude mcp add --transport http xrpl-utilities https://mcp.xrpl-utilities.io/mcp
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "xrpl-utilities": {
      "url": "https://mcp.xrpl-utilities.io/mcp"
    }
  }
}
VS Code
code --add-mcp '{"name":"xrpl-utilities","type":"http","url":"https://mcp.xrpl-utilities.io/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard
claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

xrpl_sentinel_scan xrpl_sentinel_scan_history xrpl_sentinel_verify_origin xrpl_pulse_recent_events xrpl_pulse_events_by_address xrpl_pulse_stream_purchase xrpl_pulse_ripple_counterparties xrpl_pulse_ripple_topology xrpl_pulse_cex_attribution xrpl_pulse_network_stats xrpl_pulse_xrpl_primitives xrpl_pulse_whale_flow_24h xrpl_pulse_exchange_flow_delta xrpl_pulse_rwa_summary xrpl_pulse_exchange_net_flow xrpl_pulse_escrow_calendar xrpl_pulse_entity_positioning xrpl_pulse_rlusd_distribution xrpl_desk_briefing xrpl_wallet_check xrpl_xrp_market_briefing xrpl_rwa_token_report xrpl_fund_flow_report xrpl_permissioned_venue_report xrpl_network_snapshot xrpl_pulse_token_health xrpl_pulse_whale_census xrpl_pulse_whale_flow_history xrpl_pulse_rwa_supply_history xrpl_pulse_xls85_totals xrpl_pulse_ripple_counterparty_graph xrpl_pulse_recent_choreographies xrpl_pulse_top_destinations xrpl_pulse_moex_xrp_index xrpl_telemetry_snapshot xrpl_telemetry_get_quote xrpl_telemetry_get_status xrpl_telemetry_get_results xrpl_telemetry_settlement_totals xrpl_telemetry_settlement_series xrpl_telemetry_dex_pair_volume xrpl_telemetry_liquidity xrpl_telemetry_exchange_flow_history xrpl_trust_list_domains xrpl_trust_get_domain xrpl_trust_credential_issuers xrpl_trust_recent_events xrpl_trust_list_operators_index xrpl_trust_operator_drilldown xrpl_trust_operator_attribution xrpl_trust_usage_summary xrpl_trust_jurisdictions xrpl_trust_permissioned_activity xrpl_vault_scan xrpl_vault_daily_flow xrpl_vault_daily_flow_history xrpl_flows_scan xrpl_flows_correlation xrpl_flows_cross_border_flow xrpl_flows_launch_impact and 4 more

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-03): be0fbb39bb36bc05. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-xrpl-utilities-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-xrpl-utilities-mcp)

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. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers

The Stall
ai.intuitek.the-stall/the-stall
200 tools, nothing matched
2026-10-22
SAP MCP Server
ai.oobeprotocol.sap.mcp/sap-mcp
200 tools, nothing matched
2026-10-22
Citiview Agent Market
com.citiviewgroup.mcp/agent-market
200 tools, nothing matched
2026-10-26
ScorpTech x402 API
com.it.scorptech/x402
200 tools, nothing matched
2026-10-26
Apex Edge — x402-paid machine services
dev.pages.nonsynthetic/apex-edge
200 tools, nothing matched
2026-10-23
x402 Factory
io.github.praneeth12098/x402-factory
200 tools, nothing matched
2026-10-26