Wayreceipt

dev.pages.wayreceipt/wayreceiptwayreceipt.pages.devstreamable-httpv0.1.0Scanned 1 hour ago

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

4 tools: 1 do something that can't be undone, 1 change things and 2 only read.

Reads private data · 1
Reads text others write · 2
Can send data out · 1
2 findings

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

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.

4 tools

Can't be undone 1Sends, pays, publishes or merges: once done, it cannot be taken back.Claude Code: ask

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.Reads text others writeCan send data out1 finding
Why it is in this group
- The name "publish_delivery_receipt" says "publish": a word for a change that another call does not undo.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe name "publish_delivery_receipt" says "publish": it sends or publishes something to other people.
Findings
- Info
  The input schema at properties.receipt.description mentions "Credential".
  Matched text
  inputSchema.properties.receipt.description: "...eceipt delivery receipt (W3C Verifiable Credential 2.0 with eddsa-jcs-2022 proofs)."
  What this check looks for
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true

Changes things 1Creates or changes something that can be changed back.Claude Code: ask

verify_delivery_receiptProof of delivery check.Reads text others write1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
  The input schema at properties.receipt.description mentions "Credential".
  Matched text
  inputSchema.properties.receipt.description: "...eceipt delivery receipt (W3C Verifiable Credential 2.0 with eddsa-jcs-2022 proofs)."
  What this check looks for
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true

Only reads 2Looks things up and changes nothing.Show 2 read-only tools

log_statsCounts from the public log of countersigned receipts: receipts, distinct seller keys, distinct buyer keys and distinct seller-buyer pairs.No findings
Why it is in this group
- The name "log_stats" says "log": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
lookup_delivery_receiptFinds countersigned receipts in the public log by receipt ID, deliverable hash (file SHA-256) or seller key.Reads private dataNo findings
Why it is in this group
- The name "lookup_delivery_receipt" says "lookup": a word for reading.
What it can reach
- private-dataThe description's first sentence says "find" and "file": it reads files.
- private-dataThe input names a file (input.file_sha256), and the tool reads: it reads files.
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: 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.

2 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data1: Reads files, mail, messages, databases, secrets, calendars or repositories.; lookup_delivery_receipt
Reads text others write2: Brings in text someone else can write: web pages, inbound email, messages, issues and comments.; publish_delivery_receipt
verify_delivery_receipt
Can send data out1: Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.; publish_delivery_receipt

deny to break every path

{
  "permissions": {
    "deny": [
      "mcp__wayreceipt__publish_delivery_receipt"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Findings

Matches of fixed checks, with the text they matched.

2 info

Infoverify_delivery_receipt
The input schema at properties.receipt.description mentions "Credential".
Matched text
inputSchema.properties.receipt.description: "...eceipt delivery receipt (W3C Verifiable Credential 2.0 with eddsa-jcs-2022 proofs)."
What this check looks for
Infopublish_delivery_receipt
The input schema at properties.receipt.description mentions "Credential".
Matched text
inputSchema.properties.receipt.description: "...eceipt delivery receipt (W3C Verifiable Credential 2.0 with eddsa-jcs-2022 proofs)."
What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

All changes to this server

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

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

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

Run 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.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__wayreceipt__lookup_delivery_receipt",
      "mcp__wayreceipt__log_stats"
    ],
    "ask": [
      "mcp__wayreceipt__verify_delivery_receipt",
      "mcp__wayreceipt__publish_delivery_receipt"
    ],
    "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 wayreceipt. Review it before you use it.

Capability tags behind 3 rules

mcp__wayreceipt__verify_delivery_receipt untrusted-input
mcp__wayreceipt__lookup_delivery_receipt private-data
mcp__wayreceipt__publish_delivery_receipt untrusted-input, outbound

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://anlyon.dev/api/v1/servers/dev.pages.wayreceipt/wayreceipt/verify?hash=8d03c6dcee3885fad949b355d0034f3c68efcf410a9cdb06bf5fbf6547e06e22" | jq -e '.changed == false'

Pinned hash 8d03c6dcee38, from Oct 23, 2026, 20:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/dev.pages.wayreceipt/wayreceipt/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

[![anlyon.dev](https://anlyon.dev/badge/dev.pages.wayreceipt/wayreceipt.svg)](https://anlyon.dev/servers/dev.pages.wayreceipt/wayreceipt)

Source: MCP Registry. Synced Oct 23, 2026, 20:17 UTC.