mcp-registry/io.github.k-luecke/paxiom-receipts · registry v0.3.0 · server reports v0.4.0
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clientsAs of 2026-11-22 17:55 UTC, the Paxiom Receipts MCP is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 5 minutes.
Verify, issue, and explain Ed25519 delivery receipts (paxiom.receipt.v0) for x402 APIs.
Point your MCP client at this streamable-http endpoint: https://api.paxiom.org/mcp
2 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.k-luecke%2Fpaxiom-receipts/fixes
{
"name": "explain_receipt",
"description": "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 i",
"inputSchema": {
"type": "object",
"required": [
"receipt"
],
"properties": {
"output": {
"description": "Optional delivered HTTP response payload; pass whenever available so SHA-256 payload binding is evaluated alongside the Ed25519 signature.",
"type": "string"
},
"receipt": {
"type": "object",
"description": "Parsed paxiom.receipt.v0 JSON envelope (decoded from Payment-Receipt or X-Paxiom-Receipt HTTP header)."
},
"expectedPayTo": {
"type": "string",
"description": "Optional expected seller payTo address from the 402 quote."
},
"trustedPaxiomPublicKeys": {
"type": "array",
"items": {
"type": "string"
},
"description": "Backward-compatible alias for trustedVerifierPublicKeys."
},
"expectedIssuerPublicKeys": {
"type": "array",
"items": {
"type": "string"
},
"description": "Optional pinned base64 Ed25519 seller public keys (e.g. from /.well-known/x402-keys.json)."
},
"trustedVerifierPublicKeys": {
"type": "array",
"items": {
"type": "string"
},
"description": "Optional canonical base64 32-byte Ed25519 public keys trusted to assert settlement.checkedByVerifier=true (defaults to the host key)."
}
}
},
"annotations": {
"title": "Format Human-Readable Receipt Explanation",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
},
"title": "Format Human-Readable Receipt Explanation"
}{
"name": "verify_receipt",
"description": "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. Deterministi",
"inputSchema": {
"type": "object",
"required": [
"receipt"
],
"properties": {
"output": {
"description": "Optional delivered HTTP response payload (JSON value for jcs-sha256, or UTF-8 string for raw-sha256); required to reach trustState=\"verified\".",
"type": "string"
},
"receipt": {
"type": "object",
"description": "Parsed paxiom.receipt.v0 JSON envelope (decoded from Payment-Receipt or X-Paxiom-Receipt HTTP header)."
},
"expectedPayTo": {
"type": "string",
"description": "Optional expected seller payTo address from the 402 quote. Mismatch returns trustState=\"unauthorized_issuer\"."
},
"trustedPaxiomPublicKeys": {
"type": "array",
"items": {
"type": "string"
},
"description": "Backward-compatible alias for trustedVerifierPublicKeys."
},
"expectedIssuerPublicKeys": {
"type": "array",
"items": {
"type": "string"
},
"description": "Optional pinned base64 Ed25519 seller public keys (e.g. from /.well-known/x402-keys.json). Mismatch returns trustState=\"unauthorized_issuer\"."
},
"trustedVerifierPublicKeys": {
"type": "array",
"items": {
"type": "string"
},
"description": "Optional canonical base64 32-byte Ed25519 public keys trusted to assert settlement.checkedByVerifier=true (defaults to the host key)."
}
}
},
"annotations": {
"title": "Verify Paxiom Receipt (Structured JSON)",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
},
"title": "Verify Paxiom Receipt (Structured JSON)"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.k-luecke/paxiom-receipts"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.k-luecke/paxiom-receipts"}) over MCP.
verify_receipt ~469 tokensexplain_receipt ~438 tokensget_x402_verifier_info ~142 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live.
Shows whether the server is live and its agent-readiness score; it updates within the hour.
[](https://glimind.com/server/mcp-registry%2Fio.github.k-luecke%2Fpaxiom-receipts?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.k-luecke%2Fpaxiom-receipts?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fio.github.k-luecke%2Fpaxiom-receipts.svg" alt="MCP server status"></a>
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:e9cbf9eb5d073064…, first seen 2026-11-16, included at leaf 302491 of 384,797. Version history · verify what your client received.
Compare: most reliable finance servers · most reliable payments servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp?ref=install-server"
}
}
}
A free Glimind key lets your agent check whether a server works right now before it calls it, and switch to a live one when it doesn't. No signup, no card.
As of 2026-11-22 17:55 UTC, the Paxiom Receipts MCP is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 5 minutes.
Paxiom Receipts MCP advertises 5 tools, including explain_receipt, get_x402_verifier_info, verify_receipt, verify_receipt_live, x402_preflight.
Point your MCP client at this streamable-http endpoint: https://api.paxiom.org/mcp
Glimind scanned all 3 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.