Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Paxiom Receipts MCP

REMOTE · API.PAXIOM.ORG

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

Available components

+3 this week 71 Trust /100

Last scanned (15 minutes ago)

Scores higher than 56% of remote servers

Reachable. Last reached 22 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security77
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 862 tokens (~287/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1
    • Server version: 0.3.0 → 0.4.0 functional
  • 18 Nov 26 0
    • Server version: 0.2.1 → 0.3.0 functional
  • 16 Nov 26 +1
    • Server version: 0.2.0 → 0.2.1 functional
  • 15 Nov 26 −2
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “explain_receipt” rewrote its description, which is the text the model reads security
    • Tool “get_x402_verifier_info” rewrote its description, which is the text the model reads security
    • Tool “verify_receipt” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • Tool “explain_receipt” now declares an output schema ▲ functional
    • Tool “get_x402_verifier_info” now declares an output schema ▲ functional
    • Tool “verify_receipt” now declares an output schema ▲ functional
    • First check of Tool coverage: 100 functional
    • Server version: 0.1.3 → 0.2.0 functional
    • “explain_receipt” added an optional parameter “expectedIssuerPublicKeys” cosmetic
    • “explain_receipt” added an optional parameter “expectedPayTo” cosmetic
    • “explain_receipt” added an optional parameter “trustedVerifierPublicKeys” cosmetic
    • “verify_receipt” added an optional parameter “expectedIssuerPublicKeys” cosmetic
    • “verify_receipt” added an optional parameter “expectedPayTo” cosmetic
    • “verify_receipt” added an optional parameter “trustedVerifierPublicKeys” cosmetic
    • “explain_receipt” reworded the description of “output” cosmetic
    • “explain_receipt” reworded the description of “receipt” cosmetic
    • “explain_receipt” reworded the description of “trustedPaxiomPublicKeys” cosmetic
    • “verify_receipt” reworded the description of “output” cosmetic
    • “verify_receipt” reworded the description of “receipt” cosmetic
    • “verify_receipt” reworded the description of “trustedPaxiomPublicKeys” cosmetic
    • Tool “explain_receipt” changed its title: Format Human-Readable Receipt Explanation cosmetic
    • Tool “get_x402_verifier_info” changed its title: Get Paxiom x402 Verifier & Preflight Metadata cosmetic
    • Tool “verify_receipt” changed its title: Verify Paxiom Receipt (Structured JSON) cosmetic
  • 14 Nov 26 70

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Nov 2026 · Probed https://api.paxiom.org/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.paxiom.org CN=WE1,O=Google Trust Services,C=US 3 Nov 2026 1 Feb 2027 ECDSA 256 ECDSA-SHA256 dbaffa16f70333df0e4dd744173d9a4b
SANs: api.paxiom.org
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of api.paxiom.org. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
org. DS published 725 8 Verified
paxiom.org. DS published 31308 13 Verified
api.paxiom.org. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.paxiom.org/mcp Verified 200
http (plaintext) http://api.paxiom.org/mcp HTTPS enforced 301 https://api.paxiom.org/mcp
MCP tools · 3 exposed · ~803 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
explain_receipt ~335

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).

NameTypeReqDescription
expectedIssuerPublicKeysarray–Optional pinned base64 Ed25519 seller public keys (e.g. from /.well-known/x402-keys.json).
expectedPayTostring–Optional expected seller payTo address from the 402 quote.
output––Optional delivered HTTP response payload; pass whenever available so SHA-256 payload binding is evaluated alongside the Ed25519 signature.
receiptobjectyesParsed paxiom.receipt.v0 JSON envelope (decoded from Payment-Receipt or X-Paxiom-Receipt HTTP header).
trustedPaxiomPublicKeysarray–Backward-compatible alias for trustedVerifierPublicKeys.
trustedVerifierPublicKeysarray–Optional canonical base64 32-byte Ed25519 public keys trusted to assert settlement.checkedByVerifier=true (defaults to the host key).
NameTypeReqDescription
explanationstringyesMulti-line human-readable trust breakdown, failed/skipped check details, and next-step remediation guidance.
receiptHashstring|nullyesHex SHA-256 digest of the canonical signing input, or null when schema validation failed.
trustStatestringyesUnderlying verification state explained in the report.
validbooleanyesTrue only when trustState reaches "verified".

No examples provided.

get_x402_verifier_info ~97

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
baseUrlstringyesHTTPS origin of the verifier API.
freeEndpointsobjectyesUnauthenticated free HTTP routes for offline verification, live settlement verification, seller preflight, and .well-known key discovery.
mcpEndpointstringyesStreamable-HTTP MCP endpoint URL.
npmPackageobjectyesLocal zero-dependency npm SDK and stdio MCP package details (@paxiom/receipts).
paidX402Endpointsobject|nullyesNull on the free public reference verifier (or custom x402 gate descriptor if enabled on a self-hosted instance).
receiptVersionstringyesSupported receipt schema version ("paxiom.receipt.v0").
servicestringyesCanonical verifier service identifier ("paxiom-receipt-verifier").
trustedPaxiomKeysarrayyesPublished Ed25519 counter-attestation public keys ({ keyId, algorithm, publicKey }).

No examples provided.

verify_receipt ~371

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.

NameTypeReqDescription
expectedIssuerPublicKeysarray–Optional pinned base64 Ed25519 seller public keys (e.g. from /.well-known/x402-keys.json). Mismatch returns trustState="unauthorized_issuer".
expectedPayTostring–Optional expected seller payTo address from the 402 quote. Mismatch returns trustState="unauthorized_issuer".
output––Optional delivered HTTP response payload (JSON value for jcs-sha256, or UTF-8 string for raw-sha256); required to reach trustState="verified".
receiptobjectyesParsed paxiom.receipt.v0 JSON envelope (decoded from Payment-Receipt or X-Paxiom-Receipt HTTP header).
trustedPaxiomPublicKeysarray–Backward-compatible alias for trustedVerifierPublicKeys.
trustedVerifierPublicKeysarray–Optional canonical base64 32-byte Ed25519 public keys trusted to assert settlement.checkedByVerifier=true (defaults to the host key).
NameTypeReqDescription
checksobjectyesPer-stage cryptographic and structural check statuses.
receiptHashstring|nullyesHex SHA-256 digest of the canonical signing input, or null if schema validation failed.
summarystringyesOne-sentence diagnostic summary of the verification outcome.
trustStatestringyesMachine-readable verification outcome classification.
validbooleanyesTrue only when trustState is "verified" (valid signature, authorized signer if pinned, matching outputHash, non-expired, and confirmed or verify_only settlement).

No examples provided.

Install

How do I install the Paxiom Receipts MCP server?

Paxiom Receipts MCP is a hosted endpoint at https://api.paxiom.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.paxiom.org

# add to Claude Code
claude mcp add --transport http k-luecke-paxiom-receipts 'https://api.paxiom.org/mcp'
Common questions

What is the Paxiom Receipts MCP server?

Paxiom Receipts MCP is listed in the public MCP registry as io.github.k-luecke/paxiom-receipts. Verify, issue, and explain Ed25519 delivery receipts (paxiom.receipt.v0) for x402 APIs. This page covers its hosted endpoint (https://api.paxiom.org/mcp).

Is the Paxiom Receipts MCP server safe to use?

Paxiom Receipts MCP scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Paxiom Receipts MCP server expose?

Paxiom Receipts MCP exposes 3 tools: verify_receipt, explain_receipt, get_x402_verifier_info. Their descriptions and schemas cost roughly 803 tokens of context every time the server is loaded.

Does the Paxiom Receipts MCP server require authentication?

No. We connected to Paxiom Receipts MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Paxiom Receipts MCP server still maintained?

Paxiom Receipts MCP is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Paxiom Receipts MCP server?

VerifyMCP ran 13 checks on Paxiom Receipts MCP, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.