English Français العربية

XRPLink

Registre officiel Finance et paiements

Verify XRP payments on Flare FDC. Agents subscribe or pay per attestation via x402 on XRPL.

Code source Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http xrplink 'https://xrp-link.com/mcp'
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "xrplink": {
            "type": "http",
            "url": "https://xrp-link.com/mcp"
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. XRPLink — Cryptographically Verified XRP Payment Receipts
  2. Quick Start
  3. Project Status
  4. Server Modes
  5. Tech Stack & Dependencies
  6. API Endpoints
  7. MCP Tools
  8. Network Configuration
  9. Architecture
  10. Contributing
  11. License

Generate tamper-proof, independently verifiable receipts for any XRP payment. XRPLink attests XRP transactions through Flare's FDC protocol and provides a shareable receipt with a cryptographic Merkle proof. Built for compliance, audit, and merchant reconciliation.

Live at https://xrp-link.com

Quick Start

# Visit the hosted app
open https://xrp-link.com

# Or run locally
git clone <repo-url>
cd xrplink
npm install
cp .env.example .env
# Edit .env with your private key and API key
npm run start:rest

Project Status

Live on Flare mainnet. End-to-end pipeline validated: XRP tx → verifier API → FdcHub → DA Layer proof → on-chain verification.

MilestoneStatus
Mainnet deployment✅ Live (PaymentVerifierMainnet at 0xA10034...e14b)
End-to-end pipeline validated✅ Complete — XRP tx attested on mainnet
User auth (signup/login)✅ Complete
Receipt pages✅ Complete — shareable at /receipt/:txHash
Dashboard✅ Complete — API key, usage stats, receipt history
REST API✅ Complete — verify, status, webhooks, health
API key auth + rate limiting✅ Complete
Subscription tiers✅ Complete — free/paid/pro
MCP Server✅ Complete — 5 tools, 4 prompts, 5 resources
Hardhat test suite✅ Complete — 8 tests passing
Open source✅ BUSL-1.1 (source-available)

Server Modes

CommandWhat starts
npm startMCP server (stdio) + REST API
npm run start:mcpMCP server only
npm run start:restREST API only

Tech Stack & Dependencies

DepVersionPurpose
hardhat^3.9.1Solidity dev environment
ethers5.8.0EVM interaction
tsx^4.23.0TypeScript script runner
dotenv^17.4.2.env config
express^5.2.1HTTP API server
@flarenetwork/flare-periphery-contracts^0.1.52FDC protocol interfaces
@modelcontextprotocol/sdk^1.29.0MCP server framework

API Endpoints

MethodPathAuthDescription
POST/auth/signupPublicCreate account + free API key
POST/auth/loginPublicLog in and get a session token
GET/meBearer tokenCurrent user info and API keys
GET/healthPublicServer status and network info
GET/dashboardPublicHTML user dashboard
GET/receipt/:txHashPublicView a receipt (HTML)
POST/api/v1/verify/xrp-paymentAPI keyAttest an XRP tx
GET/api/v1/status/:idAPI keyCheck attestation by UUID
GET/api/v1/status-by-tx/:txHashAPI keyCheck attestation by txHash
POST/api/v1/webhooksAPI keyRegister webhook callback
POST/billing/subscribeBearer tokenUpgrade subscription
GET/billing/portalBearer tokenManage billing
GET/mcp/resourcesPublicList MCP resources
GET/mcp/promptsPublicList MCP prompts

MCP Tools

ToolDescription
verify_xrp_paymentSubmit txHash for FDC attestation
get_attestation_statusCheck attestation by UUID
lookup_attestation_by_txFind attestation by txHash
get_attestation_by_roundList attestations by round ID
get_server_infoServer + network info

Connect via stdio: npm run start:mcp

Network Configuration

ParamCoston2 (Testnet)Flare Mainnet
RPChttps://coston2-api.flare.networkhttps://flare-api.flare.network
Chain ID11414
FdcHub0x48aC463d7975828989331F4De43341627b9c5f1D0xc25c749DC27Efb1864Cb3DADa8845B7687eB2d44
FdcVerification0x906507E0B64bcD494Db73bd0459d1C667e14B9330x9394c7A36b3Da8de1b4F27cdD0a554dA4Fa7132d
DA Layerhttps://ctn2-data-availability.flare.networkhttps://flr-data-availability.flare.network
Verifier APIhttps://fdc-verifiers-testnet.flare.networkhttps://fdc-verifiers-mainnet.flare.network
Source IDtestXRPXRP
First Voting Round16584300001658430000
Attestation fee1 test FLR20 FLR

Architecture

┌───────────────────────┐
│     User dApp         │  (Flare EVM)
│  (PaymentVerifier.sol)│
└────────┬──────────────┘
         │ verifyXRPPayment(proof)
         ▼
┌───────────────────────┐
│  FdcVerification      │  (enshrined FDC protocol contract)
│  (via ContractRegistry)│
└────────┬──────────────┘
         │
    ┌────┴────┐
    │ DA Layer│──── Proof + response
    └────┬────┘
         │
    ┌────┴────┐
    │ Verifier│──── ABI-encoded request with MIC
    └────┬────┘
         │
    XRP Testnet / Mainnet

Key data flow:

  1. XRP tx happens on XRP Ledger
  2. Verifier API fetches tx details, computes MIC, returns ABI-encoded request
  3. Request submitted to FdcHub on Flare with FLR fee
  4. FDC providers independently verify the XRP tx, reach consensus (90s round)
  5. Merkle root stored onchain via Relay contract
  6. DA Layer serves attestation response + Merkle proof
  7. Smart contract verifies proof against onchain Merkle root via FdcVerification

Contributing

See CONTRIBUTING.md. All contributions welcome — bug fixes, feature requests, docs improvements, and test additions.

XRPLink is source-available (BUSL-1.1) and built for the Flare ecosystem. Non-commercial use, evaluation, and personal use are free. Running XRPLink as a commercial service requires a license from the Licensor.

License

BUSL-1.1 — see LICENSE. Converts to MIT after four years.

Questions fréquentes

Qu'est-ce que XRPLink ?

Verify XRP payments on Flare FDC. Agents subscribe or pay per attestation via x402 on XRPL.

Comment installer XRPLink ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http xrplink 'https://xrp-link.com/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour XRPLink ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

XRPLink est-il open source ?

Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.

Qui maintient XRPLink ?

Il est publié par joverman. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.