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 分

    请在仓库或注册中心条目中声明许可证。