Paxiom Receipts MCP

● Active

io.github.k-luecke/paxiom-receipts

Verify, issue, and explain Ed25519 delivery receipts (paxiom.receipt.v0) for x402 APIs.

Connect this server

One click to install, or copy the config below. Suits: Cursor · HTTP clients.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "paxiom-receipts": {
      "url": "https://api.paxiom.org/mcp"
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --transport http paxiom-receipts https://api.paxiom.org/mcp
VS Code
code --add-mcp '{"name":"paxiom-receipts","type":"http","url":"https://api.paxiom.org/mcp"}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
APIs & Integrations
Version
0.3.0
Registry
active
Published
11/18/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Looks healthy: Paxiom Receipts MCP is maintained, open source, hosted endpoint answering without a key.

Maintained
Active
Last commit 2 days ago (Nov 19, 2026), 0 open issues.
Official registry
Active
Published as io.github.k-luecke/paxiom-receipts in the official MCP registry, version 0.3.0.
Source
Open source, MIT
Public repository under the MIT licence, 0 stars, 0 forks.
Runs
Hosted by the publisher
Your client talks to api.paxiom.org: prompts and tool arguments leave your machine for that host.
Credentials
None needed to connect
The hosted endpoint completed the Serverdex initialize + tools/list handshake with no key (checked Nov 22, 2026); individual tools may still ask for one.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.

Live check

checked Nov 22, 2026, 08:08 UTCStatus history & uptime →
● Working188 msprotocol 2025-06-18v0.4.0tools

The endpoint answered the MCP handshake as "Paxiom Receipts MCP" and listed 3 tools. Answering since Nov 18, 2026.

Context cost ≈ 2.3k tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 3 tools.

Tools (3)

  • verify_receipt6 params

    Validate an Ed25519-signed paxiom.receipt.v0 API delivery receipt (JSON Schema, Ed25519 signature, signer authorization via expectedIssuerPublicKeys / expectedPayTo, JCS or raw SHA-256 output binding, expiry, and settlement trust state) and return structured JSON fields. Use this instead of explain_receipt when automated code branches on valid or trustState; use explain_receipt when presenting human-readable guidance, or get_x402_verifier_info for live on-chain settlement endpoints. Deterministic, offline, and free with no auth: invalid or tampered receipts return isError=false with valid=false and the failing trustState, omitting output caps trustState at valid_signature_only, and omitting trustedVerifierPublicKeys trusts the host counter-attestation key by default.

    Show parameters
    • receiptobjectrequiredParsed paxiom.receipt.v0 JSON envelope (decoded from Payment-Receipt or X-Paxiom-Receipt HTTP header).
    • outputOptional delivered HTTP response payload (JSON value for jcs-sha256, or UTF-8 string for raw-sha256); required to reach trustState="verified".
    • expectedIssuerPublicKeysarrayOptional pinned base64 Ed25519 seller public keys (e.g. from /.well-known/x402-keys.json). Mismatch returns trustState="unauthorized_issuer".
    • expectedPayTostringOptional expected seller payTo address from the 402 quote. Mismatch returns trustState="unauthorized_issuer".
    • trustedVerifierPublicKeysarrayOptional canonical base64 32-byte Ed25519 public keys trusted to assert settlement.checkedByVerifier=true (defaults to the host key).
    • trustedPaxiomPublicKeysarrayBackward-compatible alias for trustedVerifierPublicKeys.
  • explain_receipt6 params

    Format a plain-text trust breakdown and next-action remediation checklist for an Ed25519-signed paxiom.receipt.v0 API delivery receipt. Use this instead of verify_receipt when displaying a readable verdict to a user or operator; use verify_receipt when code needs raw check fields for programmatic gating, or get_x402_verifier_info to discover live Base USDC settlement endpoints. Runs deterministically offline for free with no auth: tampered, unauthorized, expired, or unconfirmed receipts return isError=false with an actionable diagnostic explanation rather than throwing, and omitting trustedVerifierPublicKeys trusts the host counter-attestation key by default. Pass output with the delivered HTTP response body to check SHA-256 payload binding (omitting output caps trustState at valid_signature_only).

    Show parameters
    • receiptobjectrequiredParsed paxiom.receipt.v0 JSON envelope (decoded from Payment-Receipt or X-Paxiom-Receipt HTTP header).
    • outputOptional delivered HTTP response payload; pass whenever available so SHA-256 payload binding is evaluated alongside the Ed25519 signature.
    • expectedIssuerPublicKeysarrayOptional pinned base64 Ed25519 seller public keys (e.g. from /.well-known/x402-keys.json).
    • expectedPayTostringOptional expected seller payTo address from the 402 quote.
    • trustedVerifierPublicKeysarrayOptional canonical base64 32-byte Ed25519 public keys trusted to assert settlement.checkedByVerifier=true (defaults to the host key).
    • trustedPaxiomPublicKeysarrayBackward-compatible alias for trustedVerifierPublicKeys.
  • get_x402_verifier_info

    Retrieve Paxiom Receipt Verifier reference service discovery metadata, published Ed25519 counter-attestation public keys (/.well-known/x402-keys.json), and free rate-limited public HTTP endpoints for offline verification, live Base USDC settlement verification (/v1/receipt/verify-live), and pre-payment seller safety preflight (/v1/x402/preflight). Stateless, read-only, and free with no authentication required.

Checked by Serverdex with a plain initialize + tools/list call to api.paxiom.org/mcp, no credentials, about once a day. A failed check is never a removal.

On GitHub

read Nov 22, 2026
Stars
0
Forks
0
Last push
Nov 19, 2026
License
MIT

HTMLagent-paymentsed25519fastapimcppythonreceiptstypescriptx402

From the README

Paxiom — Proof-of-Delivery Receipts & Verifier (paxiom.receipt.v0) x402 proves a payment. Paxiom proves what the payment bought. Open MIT specification, x402 v2 delivery-receipt extension draft, zero-dependency TypeScript/Node & Python SDKs, MCP servers, free public reference verification runtime (https://api.paxiom.org), and specification site (https://paxiom.org) maintained by Driftbound Labs (https://driftboundlabs.com). Shipped Packages & Free Public Reference Endpoints (v0.4.0) Quick Verification Explicit Boundaries (What v0.2.0 Checks vs. Does Not Claim) • Offline verification (verifyReceipt / POST /v1/receipt/verify) verifies schema conformance, deterministic canonical JSON (jcs-sha256) or raw byte (raw-sha256) payload digests, Ed25519 signatures, optional seller key / payTo authorization (unauthorizedissuer), and counter-attestation key pinning (trustedVerifierPublicKeys), reporting unverified on-chain hashes honestly as settlementclaimednotchecked without touching RPC. • Live verification (POST /v1/receipt/verify-live) is operated as a free, rate-limited public reference utility (and is 100% MIT self-hostable via runtime/receipt-verifier/server.mjs).…

Read the full README on GitHub →

Remotes

  • streamable-httphttps://api.paxiom.org/mcp

The most-starred APIs & Integrations servers in the index, with their live-check result.

ServerStarsLast pushLive check
OpenWork MCP Gateway24,576Nov 2026Needs sign-in
API Anything3,699Nov 2026Local / not checked
GoModel1,322Nov 2026Local / not checked
Scaleway MCP server1,027Nov 2026Local / not checked
AnythingMCP817Nov 2026Needs sign-in

Paxiom Receipts MCP: questions people ask

Is Paxiom Receipts MCP a remote or a local MCP server?
According to its entry in the official MCP registry, Paxiom Receipts MCP ships as a hosted endpoint (streamable-http) that your client connects to by URL.
Does Paxiom Receipts MCP need an API key?
Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 22, 2026. Individual tools may still ask for a key when called.
Is Paxiom Receipts MCP safe to use?
Looks healthy: Paxiom Receipts MCP is maintained, open source, hosted endpoint answering without a key. In detail — maintained: Active; official registry: Active; source: Open source, MIT; runs: Hosted by the publisher; credentials: None needed to connect. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is Paxiom Receipts MCP still maintained?
Active: the repository's last commit 2 days ago. Last push Nov 19, 2026, 0 GitHub stars, MIT licence. Read from GitHub on Nov 22, 2026.
What tools does Paxiom Receipts MCP expose?
3 tools as listed by the server itself during the live check, including verify_receipt, explain_receipt, get_x402_verifier_info. The full list with parameters is in the Live check section above.
How do I add Paxiom Receipts MCP to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
Browse all APIs & Integrations →

Add the badge to your site

Show visitors that Paxiom Receipts MCP is listed here — it’s also the link we check for a free listing.

Paxiom Receipts MCP — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-k-luecke-paxiom-receipts?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Paxiom Receipts MCP — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![Paxiom Receipts MCP — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-k-luecke-paxiom-receipts?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/io-github-k-luecke-paxiom-receipts) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/io-github-k-luecke-paxiom-receipts) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/io-github-k-luecke-paxiom-receipts)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/io-github-k-luecke-paxiom-receipts"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/io-github-k-luecke-paxiom-receipts"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/io-github-k-luecke-paxiom-receipts"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).