# Paxiom Receipts MCP (remote · api.paxiom.org)

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

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-22

## Components

- remote · `api.paxiom.org`: 71/100 (this document), [markdown](https://verifymcp.io/servers/k-luecke-paxiom-receipts/api.md), [page](https://verifymcp.io/servers/k-luecke-paxiom-receipts/api)

## Channel facts

- Endpoint: `https://api.paxiom.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-22.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

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

### Claude

```bash
claude mcp add --transport http k-luecke-paxiom-receipts 'https://api.paxiom.org/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "k-luecke-paxiom-receipts": {
      "url": "https://api.paxiom.org/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "k-luecke-paxiom-receipts": {
      "type": "http",
      "url": "https://api.paxiom.org/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.k-luecke-paxiom-receipts]
url = "https://api.paxiom.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "k-luecke-paxiom-receipts": {
      "type": "remote",
      "url": "https://api.paxiom.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add k-luecke-paxiom-receipts --url 'https://api.paxiom.org/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  k-luecke-paxiom-receipts:
    url: "https://api.paxiom.org/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "k-luecke-paxiom-receipts": {
      "Transport": "http",
      "Url": "https://api.paxiom.org/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add k-luecke-paxiom-receipts -t streamable-http -u 'https://api.paxiom.org/mcp'
```

### Other

```json
{
  "mcpServers": {
    "k-luecke-paxiom-receipts": {
      "type": "http",
      "url": "https://api.paxiom.org/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 71, +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.

### 2026-11-19 (score 70, +1)

- [functional] Server version: 0.3.0 → 0.4.0

### 2026-11-18 (score 69, 0)

- [functional] Server version: 0.2.1 → 0.3.0

### 2026-11-16 (score 69, +1)

- [functional] Server version: 0.2.0 → 0.2.1

### 2026-11-15 (score 68, −2)

- [security] 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
- [functional regression] Schema quality: pass → fail
- [functional improvement] Stability: unverified → 0.03
- [functional improvement] Tool “explain_receipt” now declares an output schema
- [functional improvement] Tool “get_x402_verifier_info” now declares an output schema
- [functional improvement] Tool “verify_receipt” now declares an output schema
- [functional] First check of Tool coverage: 100
- [functional] Server version: 0.1.3 → 0.2.0
- [cosmetic] “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)

### 2026-11-14 (score 70)

First indexed and scored.

## MCP tools (3)

### `verify_receipt` (~371 tokens)

Verify Paxiom Receipt (Structured JSON)

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.

Input parameters:

- `expectedIssuerPublicKeys` (array): Optional pinned base64 Ed25519 seller public keys (e.g. from /.well-known/x402-keys.json). Mismatch returns trustState="unauthorized_issuer".
- `expectedPayTo` (string): 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".
- `receipt` (object, required): Parsed paxiom.receipt.v0 JSON envelope (decoded from Payment-Receipt or X-Paxiom-Receipt HTTP header).
- `trustedPaxiomPublicKeys` (array): Backward-compatible alias for trustedVerifierPublicKeys.
- `trustedVerifierPublicKeys` (array): Optional canonical base64 32-byte Ed25519 public keys trusted to assert settlement.checkedByVerifier=true (defaults to the host key).

Output parameters:

- `checks` (object): Per-stage cryptographic and structural check statuses.
- `receiptHash` (string|null): Hex SHA-256 digest of the canonical signing input, or null if schema validation failed.
- `summary` (string): One-sentence diagnostic summary of the verification outcome.
- `trustState` (string): Machine-readable verification outcome classification.
- `valid` (boolean): True only when trustState is "verified" (valid signature, authorized signer if pinned, matching outputHash, non-expired, and confirmed or verify_only settlement).

### `explain_receipt` (~335 tokens)

Format Human-Readable Receipt Explanation

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

Input parameters:

- `expectedIssuerPublicKeys` (array): Optional pinned base64 Ed25519 seller public keys (e.g. from /.well-known/x402-keys.json).
- `expectedPayTo` (string): 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.
- `receipt` (object, required): Parsed paxiom.receipt.v0 JSON envelope (decoded from Payment-Receipt or X-Paxiom-Receipt HTTP header).
- `trustedPaxiomPublicKeys` (array): Backward-compatible alias for trustedVerifierPublicKeys.
- `trustedVerifierPublicKeys` (array): Optional canonical base64 32-byte Ed25519 public keys trusted to assert settlement.checkedByVerifier=true (defaults to the host key).

Output parameters:

- `explanation` (string): Multi-line human-readable trust breakdown, failed/skipped check details, and next-step remediation guidance.
- `receiptHash` (string|null): Hex SHA-256 digest of the canonical signing input, or null when schema validation failed.
- `trustState` (string): Underlying verification state explained in the report.
- `valid` (boolean): True only when trustState reaches "verified".

### `get_x402_verifier_info` (~97 tokens)

Get Paxiom x402 Verifier & Preflight Metadata

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.

Output parameters:

- `baseUrl` (string): HTTPS origin of the verifier API.
- `freeEndpoints` (object): Unauthenticated free HTTP routes for offline verification, live settlement verification, seller preflight, and .well-known key discovery.
- `mcpEndpoint` (string): Streamable-HTTP MCP endpoint URL.
- `npmPackage` (object): Local zero-dependency npm SDK and stdio MCP package details (@paxiom/receipts).
- `paidX402Endpoints` (object|null): Null on the free public reference verifier (or custom x402 gate descriptor if enabled on a self-hosted instance).
- `receiptVersion` (string): Supported receipt schema version ("paxiom.receipt.v0").
- `service` (string): Canonical verifier service identifier ("paxiom-receipt-verifier").
- `trustedPaxiomKeys` (array): Published Ed25519 counter-attestation public keys ({ keyId, algorithm, publicKey }).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/k-luecke-paxiom-receipts/api#diagnostics

## Score history

- 2026-11-22: 71
- 2026-11-21: 71
- 2026-11-20: 70
- 2026-11-19: 70
- 2026-11-18: 69
- 2026-11-17: 69
- 2026-11-16: 69
- 2026-11-15: 68
- 2026-11-14: 70

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

## Links

- Remote endpoint: https://api.paxiom.org/mcp
- Repository: https://github.com/k-luecke/paxiom-static
- Website: https://paxiom.org/receipts.html
- Changelog RSS feed: https://verifymcp.io/servers/k-luecke-paxiom-receipts/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/k-luecke-paxiom-receipts/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/k-luecke-paxiom-receipts/api.json
- HTML version of this page: https://verifymcp.io/servers/k-luecke-paxiom-receipts/api
