Home / MCP registry index / io.tooloracle/xrploracle
io.tooloracle/xrploracle
io.tooloracle/xrploracle in the official MCP registry.
Endpoint https://feedoracle.io/xrpl/mcp/. Source: github.com/ToolOracle/xrploracle.
The registry describes it as: XRPLOracle - 31 XRP Ledger tools: payments, DEX, AMM, hooks, NFTs, validators, DIDs.
We read its 31 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
xrpl_overview xrpl_rlusd xrpl_account_intel xrpl_dex_orderbook xrpl_amm_pools xrpl_payment_intel xrpl_token_check xrpl_escrow_monitor xrpl_nft_intel xrpl_nft_offers xrpl_trust_lines xrpl_server_state xrpl_gateway_balances xrpl_path_find xrpl_ledger_data xrpl_compliance_check xrpl_rlusd_supply xrpl_rlusd_cci xrpl_rlusd_integrity xrpl_rlusd_holders xrpl_rlusd_service xrpl_rlusd_anchor xrpl_rlusd_webhook xrpl_rlusd_enterprise xrpl_iso20022 xrpl_rwa_scoring xrpl_quantum_join xrpl_beacon_pulse xrpl_settlement_status xrpl_escrow_create xrpl_escrow_check
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-tooloracle-xrploracle)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.