XRPName
REMOTE · XRPDOMAINS.XYZ · 2 COMPONENTS
XRPL domains for AI agents — availability, pricing, profiles, portfolio, and register links.
Available components
Last scanned (20 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1364 tokens (~136/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Oct 26 0
- Server version: 0.3.2 → 0.3.3 functional
- 16 Oct 26 +7
- Authorization: unverified → partial ▲ security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 21 Sept 26 0
- Server version: 0.3.1 → 0.3.2 functional
- 19 Sept 26 0
- Server version: 0.1.6 → 0.3.1 functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://xrpdomains.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=xrpdomains.xyz | CN=WE1,O=Google Trust Services,C=US | 25 Oct 2026 | 23 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 8fee0b70020875f51315d48385c65e58 |
| SANs: xrpdomains.xyz, *.xrpdomains.xyz | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of xrpdomains.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| xrpdomains.xyz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://xrpdomains.xyz/mcp | Verified | 200 | |
| http (plaintext) | http://xrpdomains.xyz/mcp | HTTPS enforced | 301 | https://xrpdomains.xyz/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_domains ~160
Check 1 to 25 XRPL domains for registration status and cost. Use for questions like "is <name>.xrp taken?", "how much does <name>.xrp cost?", "who owns <name>.xrp?", or to verify availability before registering. Accepts .xrp, .xrpl, .xrpfi, .rlusd TLDs (defaults to .xrp when omitted). Returns availability, price in XRP and RLUSD, owner address, profile metadata if registered, and a web URL for the user to register if available. Also returns invalid_domains for inputs that fail validation.
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | List of domains to check. Each may include or omit the TLD; defaults to .xrp. |
No output schema declared.
No examples provided.
check_order_status ~106
Check the backend order status for a domain you tried to register on xrpdomains.xyz. Returns whether payment landed, the offer was created, the mint completed, or it failed at a step. Use when a user asks "did my X.xrp registration go through?" or "what's the status of my order?". This is deeper than check_domains (which only shows availability).
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain whose order to check, e.g. "alice.xrp". |
No output schema declared.
No examples provided.
check_tx_status ~70
Check the validation status of an XRPL transaction by hash. Use after send_signed_tx to confirm whether the transaction was validated on-ledger. Returns status (pending, validated, failed, not_found) and engine result code.
| Name | Type | Req | Description |
|---|---|---|---|
| tx_hash | string | yes | 64-character hex XRPL transaction hash |
No output schema declared.
No examples provided.
get_domain_profile ~143
Get the full public profile of a single XRPL domain — owner, NFT token ID, metadata, avatar, fullname, description, social handles, linked chain addresses, and optionally the on-chain ownership history (pass include_history=true). Use when the user asks "show me X.xrp", "what does X.xrp link to?", "who owns X.xrp?", or "show me the history of X.xrp". Returns null fields gracefully if no profile is set.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to look up, e.g. "alice.xrp" |
| include_history | boolean | – | Include the on-chain ownership timeline (transfers, marketplace sales). |
No output schema declared.
No examples provided.
get_pending_offers ~142
Get all pending XRPL domain operations for a wallet — incoming offers (someone offered the wallet a domain), outgoing offers (the wallet listed a domain), and paid-but-not-yet-minted orders the user can still complete. Use when the user asks "do I have any pending transfers?", "what offers are waiting on me?", or before suggesting an accept/cancel/continue-mint action. Requires an XRPL r... address.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | XRPL r... address of the wallet to query (e.g. "rPT1Sjq2YGrBMTttX4GZHjKu9dyfzbpAYe"). |
No output schema declared.
No examples provided.
get_portfolio ~178
List all XRPL domains owned by a wallet address. Use when the user asks "what domains do I own?", "show me my domains", or wants to see another wallet's holdings. Returns each domain with its TLD, length, primary flag, subname flag, and quick-action URLs. (nftoken_id, image, and mint time are not included here — use get_domain_profile for one domain.) Requires an XRPL r... address.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | XRPL r... address whose domains to list. |
| filter_tld | string | – | Filter by TLD, e.g. ".xrp", ".xrpfi", ".rlusd", or "all". |
| limit | integer | – | Max domains to return. |
| sort | string | – | Sort order. "recent" keeps the backend order. |
No output schema declared.
No examples provided.
recommend_domain ~154
Get AI-recommended domain suggestions for a keyword or theme (e.g. "tom", "crypto", "defi"). Returns creative name + TLD combos with a category, each cross-checked for availability, priced, and given a register link. Use when a user asks "suggest names", "find me a domain about X", or "give me some .xrp ideas".
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many suggestions to return. |
| query | string | yes | Keyword or theme to base suggestions on, e.g. "tom" or "crypto". |
| tlds | array | – | TLDs to include (without dots), e.g. ["xrp","xrpfi"]. Omit for all. |
No output schema declared.
No examples provided.
register_domain ~133
Get the link to register a .xrp / .xrpl / .xrpfi / .rlusd domain on xrpdomains.xyz. Registration is completed in the browser — the website handles the order and the user signs in their wallet there (the MCP does NOT build or broadcast the payment). Use when the user says "register X.xrpfi" or "buy X.xrp". Pass refcode if a referral applies.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to register, e.g. "coolname.xrpfi". |
| refcode | string | – | Optional referral code to embed in the registration link. |
No output schema declared.
No examples provided.
resolve_address ~165
Reverse resolution: given an XRPL address, return its primary XRPName (if set) and the full list of names owned by the wallet. Use when the user says "who owns [address]?", "look up this wallet", or "what names does [address] have?", or when chained with get_domain_profile to explore a wallet. Returns found:false if the address owns no XRPName.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | XRPL classic address, e.g. "rLhi87eXFZNueP4Kg1jUuHmm7pWZBoT3Yn". |
| include_history | boolean | – | If true, include per-domain nftoken_id and mint date. |
| limit | integer | – | Maximum number of domains to return (cap 200). |
No output schema declared.
No examples provided.
set_primary_domain ~113
Get the link to set a domain as your wallet's primary (the name shown by default for your address). Setting primary is completed in the browser — the website handles it and your wallet signs there (the MCP does NOT build or broadcast the transaction). Use when the user says "make X.xrp my primary" or "set X.xrpfi as my main domain". The wallet must already own the domain.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to set as primary, e.g. "alice.xrp". |
No output schema declared.
No examples provided.
How do I install the XRPName MCP server?
XRPName is a hosted endpoint at https://xrpdomains.xyz/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · xrpdomains.xyz
claude mcp add --transport http xrpdomains-xrpname-mcp-server 'https://xrpdomains.xyz/mcp'
What is the XRPName MCP server?
XRPName is an MCP server listed in the public MCP registry as io.github.XRPDomains/xrpname-mcp-server. XRPL domains for AI agents, availability, pricing, profiles, portfolio, and register links. This page covers its hosted endpoint (https://xrpdomains.xyz/mcp).
Is the XRPName MCP server safe to use?
XRPName scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the XRPName MCP server expose?
XRPName exposes 10 tools: check_domains, recommend_domain, get_domain_profile, check_tx_status, check_order_status, and 5 more. Their descriptions and schemas cost roughly 1,364 tokens of context every time the server is loaded.
Does the XRPName MCP server require authentication?
No. We connected to XRPName without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the XRPName MCP server still maintained?
XRPName is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.