Wayreceipt MCP Server

by pages-wayreceipt Your server? Claim it

answering

Wayreceipt is answering right now. Last checked 7 min ago. It exposes 4 tools.

Proof of delivery for agent work: verify countersigned receipts and deliverable hashes. Free.

Uptime history 44 hours of history

44 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

38 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Wayreceipt every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add wayreceipt --transport http https://wayreceipt.pages.dev/mcp

Settings → Connectors → Add custom connector, then paste this address

https://wayreceipt.pages.dev/mcp

~/.codex/config.toml

[mcp_servers.wayreceipt]
url = "https://wayreceipt.pages.dev/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "wayreceipt": {
      "url": "https://wayreceipt.pages.dev/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "wayreceipt": {
      "type": "http",
      "url": "https://wayreceipt.pages.dev/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

log

log_stats

Counts from the public log of countersigned receipts: receipts, distinct seller keys, distinct buyer keys and distinct seller-buyer pairs. Receipts the Wayreceipt team made for testing and removed entries are not counted.

lookup

lookup_delivery_receipt

Finds countersigned receipts in the public log by receipt ID, deliverable hash (file SHA-256) or seller key. Shows a seller's published proof of delivery history. The log only holds receipts that a seller or buyer chose to publish, and a key is not a verified identity.

publish

publish_delivery_receipt

Publishes a countersigned receipt (already signed by both seller and buyer) to the public log, as lasting proof of delivery for a deliverable hash. Signing happens on your side with the free library; this server never holds keys. The server re-verifies the receipt and rejects seller-only or invalid ones. Optional seller_link and buyer_link pages are checked for proof that they belong to the signing key (match, mismatch or unreachable). Published receipts are public.

verify

verify_delivery_receipt

Proof of delivery check. Verifies a delivery receipt: the seller's signature over the deliverable hash (SHA-256) and, if present, the buyer's countersignature. Returns countersigned, seller-only or invalid, with reasons. Optionally compares a file's SHA-256 with the deliverable hash. Relevant to a delivery dispute or to checking a seller before payment. Free, no sign-up, no API key.

Endpoints

URL	Transport	State	Latency	Checked
https://wayreceipt.pages.dev/mcp	streamable-http	answering	30 ms	7 min ago

Alternatives to Wayreceipt

same job, measured the same way

Spoolis

by spoolis

Verify AI work against criteria and get signed receipts. From Spoolis, guarantees for AI work.

31 installs/wk 32 tools answering

ProofSlip

by proofslip

Receipt-based verification for AI agent workflows — create, verify, and poll ephemeral proof objects

23 installs/wk local only

Idios

by honeytones

Private escrow for AI agent work on Beam: verifiable delivery, worker collateral, M of N disputes.

142 installs/wk local only

Datoka API

by workers-bhazarstudio-datoka-api

Signed API declarations for agent handoffs. Free demo and verification; receipts cost 0.002 USDC.

4 tools answering

Agentic Reputation Gateway

by agenticsubstrate

Read-only gateway for durable agent identity, consent, recognized work, and signed receipts.

7 tools answering

verify-proof

by csolomon0704-prog

Verify timestamp proofs offline, anchor hashes through ProofLedger, keep agent run receipts.

1 339 installs/wk local only

Sequesign

by sequesign

Cryptographically verifiable receipts of an agent's delegated work, verified offline.

29 installs/wk local only

ActionProof

by burakfenerci5

Tamper-proof audit trail for AI agents. Signed receipts, offline-verifiable, zero backend.

30 installs/wk local only

Wayreceipt — questions

Answers built from our own checks of this server.

What can Wayreceipt do?

It exposes 4 tools, read directly from the server on our last check. Among them: log_stats, lookup_delivery_receipt, publish_delivery_receipt, verify_delivery_receipt. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Wayreceipt working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 38 ms. The bar chart above shows every period we have measured.

How do I connect Wayreceipt?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Wayreceipt need an API key?

No. Wayreceipt completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Wayreceipt?

It answers our handshake in 38 ms on average, which is faster than 99% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.