SPR (Sealed Payment Record) runs on your own machine — the client starts it, so there is no endpoint to ping. 742 installs a week from npm. Last commit 2 Nov 2026.
Seal every payment your AI agent makes as a signed record, on your own machine, with your key.
What the code does
We read the source, 22 h ago · rules 995398eba69f
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
subprocess.run(["icacls", path, "/inheritance:r", "/grant:r", f"{os.environ.get('USERNAME', '')}:F"], check=True, capture_output=True)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Nothing serious here today
Today is the operative word: we check SPR (Sealed Payment Record) every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add spr-mcp -e 'SPR_AGENT_ID=<SPR_AGENT_ID>' -e 'SPR_ENTITY=<SPR_ENTITY>' -- npx -y @luca-network/spr-mcp{
"mcpServers": {
"spr-mcp": {
"command": "npx",
"args": [
"-y",
"@luca-network/spr-mcp"
],
"env": {
"SPR_AGENT_ID": "<SPR_AGENT_ID>",
"SPR_ENTITY": "<SPR_ENTITY>"
}
}
}
}[mcp_servers.spr-mcp]
command = "npx"
args = ["-y", "@luca-network/spr-mcp"]
env = { SPR_AGENT_ID = "<SPR_AGENT_ID>", SPR_ENTITY = "<SPR_ENTITY>" }{
"mcpServers": {
"spr-mcp": {
"command": "npx",
"args": [
"-y",
"@luca-network/spr-mcp"
],
"env": {
"SPR_AGENT_ID": "<SPR_AGENT_ID>",
"SPR_ENTITY": "<SPR_ENTITY>"
}
}
}
}{
"servers": {
"spr-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@luca-network/spr-mcp"
],
"env": {
"SPR_AGENT_ID": "<SPR_AGENT_ID>",
"SPR_ENTITY": "<SPR_ENTITY>"
}
}
}
}Put your own values in place of
<SPR_AGENT_ID> (The agent's ID, such as agt_research), <SPR_ENTITY> (The company the agent pays for).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
SPR_DIR (The book's folder (default ./spr-books); it holds the company's private key), SPR_TIME_ZONE (The company's time zone for accounting dates (default UTC)), SPR_BINDING (on, to return the nonce to sign with each x402 intent).
Alternatives to SPR (Sealed Payment Record)
same job, measured the same wayMarketplace and payment rail for AI agents: list, buy and settle with signed receipts.
Web search for agents, one x402 payment: real results, provider failover, signed receipt. $0.01.
Keyless hosted MCP: pre-signature x402 payment verdict (GO/HOLD/STOP) with a signed receipt.
Check before you pay. Prove to get paid. Signed answers on any agent, against your own bar.
Agent payments, API key vaulting, and governed mandates. Agents spend within user-defined limits.
Your AI pays with a TunaPay prepaid card. You approve each payment in Telegram or on tunapay.ai.
Read-only machine payment preflight using dated MEO evidence, with explicit unknowns.
Verify your agent's x402 payment flow for free on Base Sepolia testnet before real money moves.
SPR (Sealed Payment Record) — questions
Answers built from our own checks of this server.