Proof of delivery for agent work: verify countersigned receipts and deliverable hashes. Free.
Connect Remote server
claude mcp add --transport http wayreceipt https://wayreceipt.pages.dev/mcp
{
"mcpServers": {
"wayreceipt": {
"url": "https://wayreceipt.pages.dev/mcp"
}
}
}
{
"servers": {
"wayreceipt": {
"type": "http",
"url": "https://wayreceipt.pages.dev/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://wayreceipt.pages.dev/mcp
Tools 4 found in our last check
verify_delivery_receiptProof 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…
lookup_delivery_receiptFinds 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.
log_statsCounts 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.
publish_delivery_receiptPublishes 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 se…
Details
| Endpoint | https://wayreceipt.pages.dev/mcp (Streamable HTTP) |
| First published | 23 Oct 2026 |
| Last updated | 23 Oct 2026 |
| Registry name | dev.pages.wayreceipt/wayreceipt |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
