XRPName
NPM · @XRPNAME/XRPNAME-MCP · 2 COMPONENTS · SCANNED SEP 21
XRPL domains for AI agents — availability, pricing, profiles, portfolio, and register links.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects fastify 4.29.1, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 48 of 166 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1194 tokens (~132/item across 9 items; 9 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 Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
How do I install the XRPName MCP server?
XRPName runs locally as an npm package, launched with npx -y @xrpname/xrpname-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @xrpname/xrpname-mcp
claude mcp add xrpdomains-xrpname-mcp-server -- npx -y @xrpname/xrpname-mcp
{
"mcpServers": {
"xrpdomains-xrpname-mcp-server": {
"command": "npx",
"args": [
"-y",
"@xrpname/xrpname-mcp"
]
}
}
} {
"servers": {
"xrpdomains-xrpname-mcp-server": {
"command": "npx",
"args": [
"-y",
"@xrpname/xrpname-mcp"
]
}
}
} codex mcp add xrpdomains-xrpname-mcp-server -- npx -y @xrpname/xrpname-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xrpdomains-xrpname-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@xrpname/xrpname-mcp"
],
"enabled": true
}
}
} openclaw mcp add xrpdomains-xrpname-mcp-server --command npx --arg -y --arg @xrpname/xrpname-mcp
mcp_servers:
xrpdomains-xrpname-mcp-server:
command: "npx"
args: ["-y", "@xrpname/xrpname-mcp"] {
"McpServers": {
"xrpdomains-xrpname-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@xrpname/xrpname-mcp"
]
}
}
} assistant mcp add xrpdomains-xrpname-mcp-server -t stdio -c npx -a -y @xrpname/xrpname-mcp
{
"mcpServers": {
"xrpdomains-xrpname-mcp-server": {
"command": "npx",
"args": [
"-y",
"@xrpname/xrpname-mcp"
]
}
}
} 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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −2
- Stability: pass → 0.83 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.77 functional
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 21 Sept 2026 · Analysed npm/@xrpname/xrpname-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 5 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-444r-cwp2-x5xf | CVE-2026-3635 | medium | CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N | yes |
| GHSA-jx2c-rxcm-jvmq | CVE-2026-25223 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-mrq3-vjjr-p77c | CVE-2026-25224 | low | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-w2qp-rph6-63g4 | CVE-2026-18504 | medium | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N | yes |
| GHSA-c96f-x56v-gq3h | CVE-2026-47219 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 166 packages
| Packages resolved | 166 |
|---|---|
| Stale | 48 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 ~155
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, pricing, 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.
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.
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 npm package (@xrpname/xrpname-mcp).
Is the XRPName MCP server safe to use?
XRPName scores 79 out of 100 on VerifyMCP. We recorded 5 known advisories against it as of 21 September 2026. It declares no install or post-install scripts. 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 9 tools: check_domains, recommend_domain, get_domain_profile, check_tx_status, check_order_status, and 4 more. Their descriptions and schemas cost roughly 1,194 tokens of context every time the server is loaded.
Is the XRPName MCP server still maintained?
XRPName is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the XRPName MCP server under?
XRPName declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.