Spree Commerce: open-source B2B and marketplace ecommerce
Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
在云端运行
XRPLHub — XRPLScore, MPT issuer risk & payment pre-checks
概览
作者提供的说明（英文原文）
XRPL wallet scores, wallet permissions, batch send, MPT risk, screening, pre-checks. Never signs.
PopNx MCP 的三大支柱
这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。
- 用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
- 我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
- 使用情况i非常新★ –
它能帮你做什么
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
- 连接方式: 在云端运行
- 传输方式: Streamable HTTP
- 分类: 网店与支付
安装
选择你使用的 AI 应用，然后复制设置。
安装之前
- 基础检查：1 项中通过 1 项
- 在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
- 注册中心没有列出需要填写的密钥。
你需要
- 在云端运行无需安装任何东西，通过互联网连接
你用的是哪个应用？
在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude：
- 打开 Settings → Connectors
- 点击 Add custom connector
- 粘贴下面的地址，然后点击 Add
- 如果要求登录，请登录作者的服务
https://www.xrplhub.io/api/mcp在终端中运行这条命令
claude mcp add --transport http xrplhub https://www.xrplhub.io/api/mcp或者自己复制设置
粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json
{
"mcpServers": {
"xrplhub": {
"url": "https://www.xrplhub.io/api/mcp"
}
}
}浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。
或者自己复制设置
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"xrplhub": {
"type": "http",
"url": "https://www.xrplhub.io/api/mcp"
}
}
}浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。
ChatGPT 只能连接互联网上的服务器：
- 打开网页版 ChatGPT → Settings → Connectors (Apps)
- 点击 Create 或 Add（部分套餐需要先在 Advanced 中开启 Developer mode）
- 粘贴下面的地址，起个名字，然后保存
- 如果要求登录，请登录作者的服务
https://www.xrplhub.io/api/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上，无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。
它能做什么
我们还没有读取这个服务器的工具列表；我们会轮流检查各个端点。
基础检查i
我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 Dcroyalty 验证，该账户拥有此仓库
- … 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
- … 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
- … 尚未检查
端点有响应
尚未检查；我们会轮流检查各个端点
- … 尚未检查
使用 OAuth 登录
尚未检查；我们会轮流检查各个端点
- … 尚未检查
工具描述中没有隐藏指令
尚未检查；我们会在检查端点时读取工具列表
与“网店与支付”中的其他服务器比较i
- 星标数多于此分类中其他 2546 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 2546 个服务器的 50% 更新
- 基础检查结果等于或优于此分类中其他 2546 个服务器的 100%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。
常见问题
XRPLHub — XRPLScore, MPT issuer risk & payment pre-checks 安全吗？
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。
它需要哪些密钥或代码？
注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端？
它在作者的云端运行。通过互联网连接，无需安装，但你发送的内容会经过作者的服务器。
它还在维护吗？
GitHub 仓库最后更新于–，最新版本（1.18.0）于29天前进入注册中心。
哪些应用可以使用它？
支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。
有什么可以替代它？
同一分类中有：Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce
替代选择
同一分类中其他作者的服务器，按星标数排序。
如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Stripe MCP
MCP server integrating with Stripe - tools for customers, products, payments, and more.
在云端运行✓ stripe.com
MCP Cn Commerce
8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending
在你的电脑上运行
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
XRPLHub.io — backend
The production app for xrplhub.io: Next.js (App Router, TypeScript) on Vercel, Neon Postgres through Prisma, XRP Ledger reads through a rotated pool of public nodes, and Xaman / Crossmark / GemWallet for signing. There is no AI or LLM anywhere in the shipped code.
What it does
| Product | What it is |
|---|---|
| XRPLScore | A 300–850 score for an XRPL wallet, from 8 public-ledger signals (one engine, src/lib/xrplscore.ts). Free lookups may be served from a 15-minute cache; the response says so (fromCache, cacheAgeSeconds). |
| Transaction services | Paid on-chain actions (trust lines, escrows, AMM, NFT, …). We build the exact transaction; the buyer signs it in their own wallet. The count comes only from BUILDABLE_SERVICE_IDS in src/app/api/execute/serviceCatalog.ts. |
| B2B API | Keys sold for RLUSD/XRP (/api/v1/*, /api/monitor/*, /api/screen/ofac, lending endpoints). Plans in src/lib/plans.ts; quotas are hard (HTTP 429 at the limit). |
| x402 pay-per-call | Per-request payment for the score, report and screening endpoints (RLUSD via the t54 XRPL facilitator; USDC on Base via Coinbase's facilitator). |
| Continuous monitoring | Watched wallets, HMAC-signed webhooks, sparse attested observations. Once a day, not real-time. See docs/MONITORING.md. |
| OFAC screening receipts | An exact-match check against the OFAC SDN list's XRP addresses, recorded as a receipt that attests to the process only — never to an address being clean or sanctioned. |
| MPT / credential lookups | Read-only views of Multi-Purpose Token issuers and XLS-70 credentials, each labelled with its coverage. |
| Community grants | A person reviews every application; nothing is decided or paid automatically. Applications are currently paused (GRANT_APPLICATIONS_OPEN in src/lib/grantsStatus.ts) because approved grants are waiting for funds. Donations stay open. |
XRPLHub is not a bank, credit bureau, consumer reporting agency or regulated entity, and nothing it returns is legal, financial or compliance advice.
Things that are deliberately true of this codebase
- The server decides every price.
src/lib/servicePrices.tsis the only price table. Nothing the client sends about amount or currency is read. - Payments are verified on the ledger, once.
src/lib/paymentGate.tschecks a validated, successful Payment to the treasury in XRP or RLUSD from the real issuer, covering the price; each payment hash is single-use in the database. - Invoices are matched without a scan window. Checkout invoices (
src/lib/rlusd.ts) are found by exact transaction hash when known, otherwise by walking the treasury's history back to the invoice's creation — dust traffic cannot push a real payment out of view. An invoice is only closed after the ledger was read completely. - A mistyped address is rejected, not screened. Every address goes through
src/lib/address.ts(base58check). - A cached score never reaches an attestation.
scripts/check-attestation-freshness.mjsruns innpm run buildand fails if any attestation module imports the cache or fetches a cache-backed score route. - Partial data never reads as whole. A failed ledger read is a 503 or a
degraded/complete:falseflag, never a clean-looking answer. - Every judgment carries a disclaimer in its response.
- The treasury is a single-key XRPL account. It has no signer list on the ledger; nothing here may claim multi-sig protection until it does.
Layout
src/app/api/… route handlers (payments, scoring, screening, monitoring, x402, MCP, admin, cron)src/app/… the site (homepage, pricing, donate, verify pages) src/lib/… engine, pricing + payment gate, x402, monitoring, screening, MPT/credentials, watchdog prisma/schema.prisma scripts/ build gates (freshness, service parity) and operator scripts docs/ AUTONOMY.md (what runs unattended), MONITORING.md, CREDENTIAL-SPEC.md, calibration notes
Running it locally
npm installcp .env.example .env # fill in DATABASE_URL and the keys you need npx prisma db push # creates/updates tables on your Neon database npm run dev
npm run build runs the two build gates (attestation freshness, service parity), prisma generate, then next build with TypeScript errors enforced.
Main environment variables (see .env.example; anything unset degrades loudly, not silently):
| Variable | Used for |
|---|---|
DATABASE_URL | Neon Postgres |
TREASURY_ADDRESS, RLUSD_ISSUER, RLUSD_CURRENCY | Where payments go and which RLUSD counts |
XUMM_API_KEY, XUMM_API_SECRET | Xaman sign-in and payment requests |
ADMIN_API_TOKEN | Every admin route (fails closed when unset) |
CRON_SECRET | The two daily crons |
CREDENTIAL_SIGNING_SECRET | The paid off-ledger certificate (nothing is issued without it) |
ANCHOR_WALLET_SEED, MPT_ANCHOR_ENABLED | On-ledger Merkle-root anchors |
BITHOMP_API_KEY | MPT registry holder counts |
CDP_API_KEY_ID, CDP_API_KEY_SECRET | USDC-on-Base x402 facilitator |
ERROR_WEBHOOK_URL, HEALTHCHECK_PING_URL | Alerts and the external dead-man's switch |
Operations
docs/AUTONOMY.md is the source of truth for what runs unattended (two Vercel crons, 06:00 and 07:00 UTC), what expires and when, the watchdog, and what to check first after a long absence. Deploys go out on every push to main; redeploy with the Vercel build cache off.
Contact: support@xrplhub.io