Home / MCP registry index / io.github.XRPDomains/xrpname-mcp-server
XRPName
io.github.XRPDomains/xrpname-mcp-server in the official MCP registry.
Endpoint https://xrpdomains.xyz/mcp. Source: github.com/XRPDomains/xrpname-mcp-server.
The registry describes it as: XRPL domains for AI agents — availability, pricing, profiles, portfolio, and register links.
We read its 10 tools on 2026-10-21. 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
check_domains recommend_domain get_domain_profile check_tx_status check_order_status get_pending_offers get_portfolio resolve_address register_domain set_primary_domain
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-xrpdomains-xrpname-mcp-server)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.