Wayreceipt

dev.pages.wayreceiptPublished by wayreceipt.pages.devOfficial publisherv0.1.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Wayreceipt lets an assistant verify, look up, publish and count cryptographically signed proof-of-delivery receipts for deliverables identified by SHA-256 hash.

What you can do
Verify a delivery receipt: check the seller's signature over the deliverable hash and any buyer countersignature, returning countersigned, seller-only or invalid, and optionally compare a file's SHA-256 to the hash. Look up receipts in the public log by receipt ID, deliverable hash or seller key, and view a seller's published history. Publish an already countersigned receipt to the public log as lasting proof of delivery. Read counts from the public log: receipts, distinct seller and buyer keys, and distinct seller-buyer pairs.
When to use it
Useful when you need to confirm that a deliverable was signed off by both seller and buyer, check a file against a receipt's hash, or publish and browse public proof-of-delivery records for agent work.
Requirements
A remote streamable HTTP endpoint; no packages, environment variables or headers are declared. Signing is done on your side with a separate free library, since the server never holds keys.
Before you install
Publishing writes a receipt to a public log, so treat published receipt IDs, hashes and seller keys as public. The log only contains receipts someone chose to publish, and a key is not a verified identity, so a match does not prove who the party is.

Installation

In SourceWeft

  1. Open Wayreceipt in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.pages.wayreceipt%2Fwayreceipt/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

4

verify_delivery_receipt

Verify a 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.

Parametersreceiptrequiredfile_sha256

lookup_delivery_receipt

Look up a countersigned 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.

Parameterssellerreceipt_idfile_sha256

log_stats

Public log statistics

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.

Takes no parameters.

publish_delivery_receipt

Publish a countersigned 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.

Parametersreceiptrequiredbuyer_linkseller_link

Version history

1
  1. v0.1.0LatestOct 23, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.