Paxiom Receipts MCP
Server Details
Verify, issue, and explain Ed25519 delivery receipts (paxiom.receipt.v0) for x402 APIs.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-03-26
- URL
- Repository
- k-luecke/paxiom-static
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: explain_receipt produces human-readable remediation text, verify_receipt returns structured JSON fields for programmatic gating, and get_x402_verifier_info is pure discovery metadata. Descriptions explicitly cross-reference each other with 'use X instead of Y when...' guidance, leaving no realistic chance of misselection despite explain_receipt and verify_receipt sharing the verification domain.
All three names follow a consistent snake_case verb_noun pattern (explain_receipt, verify_receipt, get_x402_verifier_info) with the resource noun clearly tied to the target artifact. get_x402_verifier_info is longer but still conforms to the same verb_noun convention.
Three tools is on the thin side but appropriate for a narrow receipt-verification service where each tool maps to a genuine consumption mode (human, code, discovery). Nothing is redundant, though the surface is small enough that it feels close to minimal.
The core lifecycle is covered: discover keys/endpoints, verify a receipt, and explain the verdict. The notable gap is that live on-chain settlement verification and pre-payment preflight exist only as external HTTP endpoints surfaced through discovery metadata, not as callable tools, forcing agents to leave the MCP surface for those workflows.
Available Tools
3 toolsexplain_receiptFormat Human-Readable Receipt ExplanationARead-onlyIdempotentInspect
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).
Inputs: receipt (required), output, expectedPayTo, trustedPaxiomPublicKeys, +2 more. Returns: valid, trustState, explanation, receiptHash
get_x402_verifier_infoGet Paxiom x402 Verifier & Preflight MetadataARead-onlyIdempotentInspect
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.
Inputs: no named parameters. Returns: baseUrl, service, npmPackage, mcpEndpoint, +4 more
verify_receiptVerify Paxiom Receipt (Structured JSON)ARead-onlyIdempotentInspect
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.
Inputs: receipt (required), output, expectedPayTo, trustedPaxiomPublicKeys, +2 more. Returns: valid, checks, summary, trustState, +1 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Ed25519 receipts over work artifacts: issue and verify offline, no account, no chain, no network.
Post-quantum, tamper-evident receipts for agent actions. Ed25519 + ML-DSA-65, offline verify.
x402 provider rankings + Ed25519-signed payment receipts + signature verification (3 tools).
Authorize and prove autonomous x402/AP2 agent payments with cryptographic receipts.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceProvides tools to look up providers, fetch receipts, and verify Ed25519 signatures for x402 payments on Base and Solana, with no API key needed for basic operations.7 npm-
- FlicenseNot gradedqualityCmaintenanceEnables auditing x402 payment logs against delivery logs to issue signed proof-of-delivery receipts and verify payer spend health.-
- AlicenseAqualityBmaintenanceEnables MCP-compatible clients to cryptographically verify CCS receipts using Ed25519 signatures and integrity checks, without API keys or rate limits.3581 npmCreative Commons Zero v1.0 Universal
- AlicenseAqualityCmaintenanceEnables agents to issue and publicly verify Ed25519-signed receipts for their actions via the ActSeal API, supporting action input/output hashes plus optional policy and idempotency metadata.2MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.