Paxiom Receipts MCP server
io.github.k-luecke/paxiom-receiptsk-lueckestreamable-httpv0.3.0Scanned
Verify, issue, and explain Ed25519 delivery receipts (paxiom.receipt.v0) for x402 APIs.
3 tools: 3 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Paxiom Receipts MCP server can do
The Paxiom Receipts MCP server is published by the GitHub account k-luecke. It has 3 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
1 tool brings in text other people can write (get_x402_verifier_info).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 18, 2026, version 0.3.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Only reads 3Show 3 read-only tools
explain_receiptFormat a plain-text trust breakdown and next-action remediation checklist for an Ed25519-signed paxiom.receipt.v0 API delivery receipt.No findings
Why it is in this group
- The name "explain_receipt" says "explain": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- title: Format Human-Readable Receipt Explanation
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_x402_verifier_infoRetrieve Paxiom Receipt Verifier reference service discovery metadata, published Ed25519 counter-attestation public keys (/.well-known/x402-keys.json), and free rate-limited public…Reads text others writeNo findings
Why it is in this group
- The name "get_x402_verifier_info" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "retrieve" and "http": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get Paxiom x402 Verifier & Preflight Metadata
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
verify_receiptValidate an Ed25519-signed paxiom.receipt.v0 API delivery receipt (JSON Schema, Ed25519 signature, signer authorization via expectedIssuerPublicKeys / expectedPayTo, JCS or raw SHA…No findings
Why it is in this group
- The description's first verb is "validate": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Verify Paxiom Receipt (Structured JSON)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 15, 2026, 13:19 UTC, unchanged since Nov 15, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.paxiom.org/mcp: tools/list returned 3 tools to an anonymous client, including verify_receipt (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools3 changed.~3 changedView diff
- Changed:explain_receiptOnly readstitledescriptioninputSchemaannotations
- Changed:get_x402_verifier_infoOnly readstitledescriptionannotations
- Changed:verify_receiptOnly readstitledescriptioninputSchemaannotations
Install
Pinned to version 0.3.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http paxiom-receipts https://api.paxiom.org/mcpclaude mcp add --transport http paxiom-receipts https://api.paxiom.org/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__paxiom-receipts__verify_receipt",
"mcp__paxiom-receipts__explain_receipt",
"mcp__paxiom-receipts__get_x402_verifier_info"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as paxiom-receipts. Review it before you use it.
Capability tags behind 1 rule
- mcp__paxiom-receipts__get_x402_verifier_info untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.k-luecke/paxiom-receipts/verify?hash=6cdef3b62756cf8abc26a9b2da0eacdd16e17faf24824689a19f4d1cfba28e29" | jq -e '.changed == false'Pinned hash 6cdef3b62756, from Nov 18, 2026, 19:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.k-luecke/paxiom-receipts/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.k-luecke/paxiom-receipts)Source: MCP Registry · repository. Synced Nov 18, 2026, 19:17 UTC.
Paxiom Receipts MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Paxiom Receipts MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the Paxiom Receipts MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Paxiom Receipts MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Paxiom Receipts MCP server have?
- 3 tools: 3 read. verify_receipt, explain_receipt and get_x402_verifier_info.
Does the Paxiom Receipts MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Paxiom Receipts MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Paxiom Receipts MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.