XRPName
XRPName is an MCP server published by XRPDomains, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-25.
Does XRPName support the current MCP specification (2026-07-28)?
Not yet confirmed. XRPName is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-25.
Is XRPName a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for XRPName (as of 2026-08-25).
How do I connect to XRPName?
XRPName is available via a hosted remote endpoint at https://xrpdomains.xyz/mcp, the package npm:@xrpname/xrpname-mcp, the official MCP Registry under io.github.XRPDomains/xrpname-mcp-server, the source repository at https://github.com/xrpdomains/xrpname-mcp-server. Authentication: none. Transports: sse-legacy.
What tools does XRPName expose?
XRPName exposes 10 tools, including check_domains, recommend_domain, get_domain_profile, check_tx_status, check_order_status, get_pending_offers (last verified 2026-08-25).
Does XRPName support MCP revision 2025-11-25?
Yes. XRPName supports MCP revision 2025-11-25 (checked 2026-08-25).
When were XRPName's facts last verified?
2026-08-25. Each fact on this page links to the sources used to verify it.
Which tools does XRPName expose?
10 tools verified.
check_domainsrecommend_domainget_domain_profilecheck_tx_statuscheck_order_statusget_pending_offersget_portfolioresolve_address
XRPL domains for AI agents — availability, pricing, profiles, portfolio, and register links.
Which MCP spec revisions does XRPName support?
XRPName has 1 verified spec-support record. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-11-25 | Supported | Source |
How widely adopted is XRPName?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
Repository and package signals for XRPName
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Stars
- 1
- Forks
- 0
- Last pushed
- (51 days ago)
- Created
- Open issues
- 0
- Primary language
- TypeScript
- Continuous integration
- Present
- Tests
- Present
- Security policy
- None
Package (npm) as of
- Latest version
0.2.1- Last published
- First published
- Releases
- 9
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 8
- Unpacked size
- 307 KB
- Registry signature
- Signed
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: endpoint-probe
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.XRPDomains/xrpname-mcp-server at version 0.1.1 - lists remote endpoint https://xrpdomains.xyz/mcp and repository https://github.com/xrpdomains/xrpname-mcp-server - accessed
- Endpoint probe of https://xrpdomains.xyz/mcp - declined server/discover; negotiated 2025-11-25 via the legacy initialize handshake; tools/list returned 10 tools - accessed
- Endpoint probe of https://xrpdomains.xyz/mcp - declined server/discover; negotiated 2025-11-25 via the legacy initialize handshake; tools/list returned 10 tools - accessed