Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
SPR (Sealed Payment Record)
概览
作者提供的说明(英文原文)
Seal every payment your AI agent makes as a signed record, on your own machine, with your key.
PopNx MCP 的三大支柱
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
- 用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
- 我们的基础检查i1 项中通过 1 项依据公开信息检查;尚未扫描代码
- 使用情况i尚未统计★ –
它能帮你做什么
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
- 连接方式: 在你的电脑上运行
- 传输方式: stdio
- 分类: 网店与支付
- 你需要填写:SPR_AGENT_ID, SPR_ENTITY
安装
选择你使用的 AI 应用,然后复制设置。
安装之前
- 基础检查:1 项中通过 1 项
- 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
- 需要你自己填写:
SPR_AGENT_ID,SPR_ENTITY,SPR_DIR,SPR_TIME_ZONE,SPR_BINDING
你需要
- npm已安装 Node.js(用于 npx 命令)
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"spr": {
"command": "npx",
"args": [
"-y",
"@luca-network/spr-mcp"
],
"env": {
"SPR_AGENT_ID": "your-value",
"SPR_ENTITY": "your-value",
"SPR_DIR": "your-value",
"SPR_TIME_ZONE": "your-value",
"SPR_BINDING": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add spr --env SPR_AGENT_ID=your-value --env SPR_ENTITY=your-value --env SPR_DIR=your-value --env SPR_TIME_ZONE=your-value --env SPR_BINDING=your-value -- npx -y @luca-network/spr-mcp运行前请先填写空着的值。
或者自己复制设置
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"spr": {
"command": "npx",
"args": [
"-y",
"@luca-network/spr-mcp"
],
"env": {
"SPR_AGENT_ID": "your-value",
"SPR_ENTITY": "your-value",
"SPR_DIR": "your-value",
"SPR_TIME_ZONE": "your-value",
"SPR_BINDING": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
或者自己复制设置
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"spr": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@luca-network/spr-mcp"
],
"env": {
"SPR_AGENT_ID": "your-value",
"SPR_ENTITY": "your-value",
"SPR_DIR": "your-value",
"SPR_TIME_ZONE": "your-value",
"SPR_BINDING": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
需要你填写的值
- The agent's ID, such as agt_research
- The company the agent pays for
SPR_DIRenvThe book's folder (default ./spr-books); it holds the company's private keySPR_TIME_ZONEenvThe company's time zone for accounting dates (default UTC)SPR_BINDINGenvon, to return the nonce to sign with each x402 intent
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它能做什么
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
- ✓ 通过
作者与仓库一致
注册名称已通过域名 luca.network 验证(注册中心会核实域名所有权)
- … 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
- … 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
- – 不适用
端点有响应
它在你的电脑上运行,没有互联网端点
- – 不适用
使用 OAuth 登录
在你的电脑上运行,改用本地设置
- … 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与“网店与支付”中的其他服务器比较i
- 星标数多于此分类中其他 2544 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 2544 个服务器的 85% 更新
- 基础检查结果等于或优于此分类中其他 2544 个服务器的 100%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
SPR (Sealed Payment Record) 安全吗?
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
你需要填写:SPR_AGENT_ID, SPR_ENTITY
它在我的电脑上运行还是在云端?
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
它还在维护吗?
GitHub 仓库最后更新于–,最新版本(0.2.0)于4天前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
有什么可以替代它?
同一分类中有:Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce
替代选择
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Stripe MCP
MCP server integrating with Stripe - tools for customers, products, payments, and more.
MCP Cn Commerce
8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
SPR: the Sealed Payment Record
Your AI agent pays for data, compute and services, and your finance team and auditor can't see what each payment was for. SPR records every payment your agent makes, before and after it pays, sealed with your company's own key on your own machine. Anyone can check the seals. No service has to be trusted, Luca's included.
npx -y @luca-network/spr-mcp
Free and open: Apache-2.0, with a royalty-free patent commitment (PATENTS.md).
Use it from your AI tool
Every setup below runs the same MCP server on your machine. Set SPR_AGENT_ID (your agent) and SPR_ENTITY (the company it pays for); records go to SPR_DIR.
Claude Desktop: add to claude_desktop_config.json:
{ "mcpServers": { "spr": { "command": "npx", "args": ["-y", "@luca-network/spr-mcp"],
"env": { "SPR_AGENT_ID": "agt_research", "SPR_ENTITY": "Example Co", "SPR_DIR": "/Users/you/spr-books" } } } }
Cursor: the same block in .cursor/mcp.json.
Claude Code:
claude mcp add spr -e SPR_AGENT_ID=agt_research -e SPR_ENTITY="Example Co" -- npx -y @luca-network/spr-mcp
OpenAI Agents SDK and LangChain (JavaScript):
import { SprBook, toOpenAIAgentsTools, toLangChainTools } from "@luca-network/spr-sdk";
const book = new SprBook({ dir: "./books", agentId: "agt_research", entity: "Example Co" }); const tools = toOpenAIAgentsTools(book, tool); // tool from "@openai/agents"; or toLangChainTools(book, tool)
CrewAI, Microsoft Agent Framework, Google ADK and the Claude Agent SDK (Python): each connects to the MCP server in a few lines. See examples/.
Any other MCP client: run npx -y @luca-network/spr-mcp over stdio with the two settings above.
The agent then calls record_intent before it pays, check_payment to see whether the payment is inside what it declared, goes to the payee it named and wasn't paid already, and record_settlement after it pays. Each record is sealed in the book's folder.
A merchant's book works the same way for payments received: it can keep the buyer's own sealed intent, how the buyer authenticated, and the order and processor references, and export one payment's evidence for a chargeback response (export_dispute_pack).
A record shows:
- what the agent declared before it paid: the purpose, the most it could spend, and when the permission expired;
- what was actually paid, on which rail, to whom and when;
- whether the payment stayed inside what was declared;
- for x402 payments, whether the chain itself recorded which declaration the payment was made under. The payer signs a fingerprint of the sealed intent as the payment's nonce.
This repository holds:
| Path | What it is |
|---|---|
SPEC.md | The format, draft 1 |
packages/spr | @luca-network/spr, the reference library for JavaScript and TypeScript, with no dependencies, plus the test vectors and spr-verify |
packages/spr-sdk | @luca-network/spr-sdk: seal your agents' payments locally, with withLuca(fetch) for x402 and tools for the OpenAI Agents SDK and LangChain |
packages/spr-mcp | @luca-network/spr-mcp: the same calls as an MCP server, for Claude Desktop, Cursor or your own agent (npx @luca-network/spr-mcp) |
python | spr-sdk for Python: the same format and the same books |
Seal an x402 payment in one line
import { SprBook } from "@luca-network/spr-sdk";
import { withLuca } from "@luca-network/spr-sdk/x402";
const book = new SprBook({ dir: "./books", agentId: "agt_research", entity: "Example Co" }); const pay = withLuca(book, { signer: account });
const res = await pay("https://data.example/prices", { luca: { purpose: "Market data for the pricing model", max_amount_minor: 20000, currency: "USDC" }, }); res.luca.record; // sealed, matched to its intent, bound on chain
Check anything without Luca
npx spr-verify ./books-export --key company.pem # a package, and whose it is
python -m spr ./books-export --key company.pem npx spr-verify --vectors # the library against the test vectors python -m spr --vectors # the Python SDK against the same vectors
company.pem is the company's public key, obtained from the company and never from the package (book.publicKey() gives it). Without --key the checkers show only that a package is consistent with the keys it carries, and say so.
Security problems: see SECURITY.md.
An implementation in any language conforms when it gives the same answers as packages/spr/vectors/vectors.json.
Local SPR and hosted Luca
The packages here run on your own machine and make no call to Luca. Luca's hosted service is a separate product that a book can be sent to.
| Local SPR (these packages) | Hosted Luca | |
|---|---|---|
| Where it runs | Your machine, your folder, your key | Luca's service |
| What it records | The intent before paying and the payment after, as the agent reports them | The same, plus the payment as the rail itself reports it |
| Limits it checks | The declared intent: its cap, its expiry, whether it was withdrawn and the payee it named; the same invoice paid twice. Optionally the book's own mandate.json (limits, payees, a window for repeats), which whoever keeps the folder writes, so it is reported as authority: "self-declared" | Mandates your finance team approves in Luca |
| Confirmation from the rail | None: the record is what the agent reported | The payment read from the rail, and any difference flagged |
| Accounting | None | Classification to your accounts (US GAAP, IFRS, tax), journal entries posted to your ERP, the month's close |
| Evidence | Seals anyone can check with spr-verify or python -m spr | Evidence your auditor can check, and the month's audit package |
| Cost | Free, Apache-2.0 | A Luca account |
A book moves across with one call once finance has registered its key: book.sendToLuca(). Luca checks every seal before it stores anything.
Send the book to Luca (optional)
Finance registers the book's key with Luca once (book.registerWithLuca), and then book.sendToLuca() sends the book. Luca checks every seal before it stores anything, and sending the same book again changes nothing. Write to hello@luca.network for an account.
Changes
What changed in each version, and what you may need to change on upgrading: CHANGELOG.md.
Status
This is draft 1 of the format and version 0.1 of the libraries. We expect to change things as people use them. Tell us what breaks or what's missing: open an issue, or write to hello@luca.network.
License
Apache License 2.0 for the code: see LICENSE. Luca's patent commitment, which lets anyone implement the format with or without this code, is in PATENTS.md.
Luca (luca.network) uses SPR for its hosted accounting of agent payments. That covers reading the rails, classifying to US GAAP and IFRS, posting to the ERP, labels agreed with counterparties, and the close.