Home / MCP registry index / com.asteroidxrpl/asteroid-xrpl-hub
Asteroid XRPL Hub
com.asteroidxrpl/asteroid-xrpl-hub in the official MCP registry.
Endpoint https://asteroidxrpl.com/mcp.
The registry describes it as: Read-only XRPL tools for ASTEROID: identity, market, supply, liquidity, escrows, holders, AMM quotes
We read its 15 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
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
discover_asset get_asset_identity verify_asset get_market_state get_supply_state get_liquidity_state verify_liquidity_lock get_escrow_schedule get_holder_distribution get_swap_quote get_project_info get_token_stats get_liquidity_stats get_escrow_stats get_price_history
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-asteroidxrpl-asteroid-xrpl-hub)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.