XRPLink

io.github.joverman由 GitHub 帳號 joverman 發布v0.3.0更新於 Oct 26, 2026

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

已驗證Streamable HTTP可網頁執行金融安全與監控

概覽

AI 產生的概覽

在 Flare FDC 上對 XRP 付款進行認證並產生可驗證收據，讓助理提交交易雜湊並查詢認證狀態。

可以做什麼
  • 提交 XRP 交易雜湊以申請 FDC 認證
  • 依 UUID 或交易雜湊查詢認證狀態
  • 讀取伺服器與網路資訊
  • 使用內建提示與資源完成收據與驗證流程
適用情境
當你需要為法遵、稽核或商戶對帳取得某筆 XRP 付款確實發生的密碼學證明，並希望由助理發起認證並追蹤狀態時適用。
執行需求
可使用 xrp-link.com 的遠端端點，或在本地以 Node.js 與 npm 安裝並設定 .env 檔。託管服務需註冊登入並以 API 金鑰呼叫認證介面；本地執行需在 .env 中提供私鑰與 API 金鑰。認證需支付 FLR 費用（Flare 主網每筆 20 FLR，Coston2 測試網為測試 FLR）。
安裝前請注意
認證會消耗 Flare 主網 FLR 費用，且存在付費訂閱方案。本地設定要求在 .env 中填寫私鑰，請使用專用的低價值金鑰。提交交易雜湊會建立認證紀錄，還可註冊 webhook 接收結果。僅能證明最近 14 天內的原生 XRP 付款。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 XRPLink，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.joverman%2Fxrplink/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "xrplink": {
      "type": "http",
      "url": "https://xrp-link.com/mcp"
    }
  }
}

README

XRPLink — Cryptographically Verified XRP Payment Receipts

[License: BUSL-1.1]

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

bash
# Visit the hosted appopen https://xrp-link.com
# Or run locallygit clone <repo-url>cd xrplinknpm installcp .env.example .env# Edit .env with your private key and API keynpm 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/healthPublicLiveness ({"status":"ok"})
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 HTTPS webhook for an attestation this key owns
POST/billing/subscribeBearer tokenUpgrade subscription
GET/billing/portalBearer tokenManage billing
GET/mcp/resourcesPublicList MCP resource metadata (no bodies)
GET/mcp/promptsPublicList MCP prompts
POST/api/v1/keys/rotateSession cookieRegenerate the signed-in user's API key
POST/api/v1/dashboard/verifySession cookieAttest from the dashboard without pasting a key
GET/api/v1/dashboard/status/:idSessionPoll a dashboard attestation the user owns
GET/PUT/POST/DELETE/api/v1/admin/*X-Admin-KeyOperator-only (disabled if ADMIN_API_KEY is unset)

MCP Tools

ToolDescription
verify_xrp_paymentSubmit txHash for FDC attestation
get_attestation_statusCheck attestation by UUID (public subset unless owning key)
lookup_attestation_by_txFind attestation by txHash (public subset unless owning key)
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

Lookback: Flare's XRPPayment attestation (IXRPPayment lutlimit 0x127500) can only prove native XRP Payments from the last 14 days. Older hashes still exist on XRPL, but the hosted verifier returns INVALID: TRANSACTION DOES NOT EXIST. XRPLink preflights the ledger and returns TX_TOO_OLD instead of a misleading FdcHub error. Failed prepares do not consume monthly quota.

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.

來源：README.md，提交 8578281

工具

0
SourceWeft 尚未讀取此伺服器的工具。

版本歷史

1
  1. v0.3.0最新Oct 26, 2026

評分

已滿足適用檢查項的 75%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分

    請讓伺服器在無憑證時回應 tools/list，或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。