# Wayreceipt (remote · wayreceipt.pages.dev)

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

- Trust score: 77/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `wayreceipt.pages.dev`: 77/100 (this document), [markdown](https://verifymcp.io/servers/dev-pages-wayreceipt-wayreceipt/wayreceipt.md), [page](https://verifymcp.io/servers/dev-pages-wayreceipt-wayreceipt/wayreceipt)

## Channel facts

- Endpoint: `https://wayreceipt.pages.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 482 tokens (~120/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 75% of tool parameters carry a description.
  - Structured output schemas are declared (25% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Wayreceipt MCP server?

Wayreceipt is a hosted endpoint at https://wayreceipt.pages.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-pages-wayreceipt-wayreceipt": {
      "type": "remote",
      "url": "https://wayreceipt.pages.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-pages-wayreceipt-wayreceipt --url 'https://wayreceipt.pages.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-pages-wayreceipt-wayreceipt:
    url: "https://wayreceipt.pages.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-pages-wayreceipt-wayreceipt": {
      "Transport": "http",
      "Url": "https://wayreceipt.pages.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-pages-wayreceipt-wayreceipt -t streamable-http -u 'https://wayreceipt.pages.dev/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-23 (score 71)

First indexed and scored.

## MCP tools (4)

### `verify_delivery_receipt` (~155 tokens)

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.

Input parameters:

- `file_sha256` (string): Optional SHA-256 (hex) of a local file to compare with the receipt.
- `receipt` (object, required): A Wayreceipt delivery receipt (W3C Verifiable Credential 2.0 with eddsa-jcs-2022 proofs).

Output parameters:

- `reasons` (array)
- `state` (string)
- `valid` (boolean)

### `lookup_delivery_receipt` (~126 tokens)

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.

Input parameters:

- `file_sha256` (string): SHA-256 (hex) of the delivered file.
- `receipt_id` (string): Receipt id (urn:uuid:...) or log sequence number.
- `seller` (string): Seller DID (did:key:... or did:web:...).

### `log_stats` (~50 tokens)

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.

### `publish_delivery_receipt` (~151 tokens)

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.

Input parameters:

- `buyer_link` (string)
- `receipt` (object, required): A Wayreceipt delivery receipt (W3C Verifiable Credential 2.0 with eddsa-jcs-2022 proofs).
- `seller_link` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-pages-wayreceipt-wayreceipt/wayreceipt#diagnostics

## Score history

- 2026-11-05: 77
- 2026-11-04: 76
- 2026-11-03: 76
- 2026-11-02: 75
- 2026-11-01: 75
- 2026-10-31: 74
- 2026-10-30: 74
- 2026-10-29: 73
- 2026-10-28: 73
- 2026-10-27: 72
- 2026-10-26: 72
- 2026-10-25: 72
- 2026-10-24: 71
- 2026-10-23: 71

## Common questions

### What is the Wayreceipt MCP server?

Wayreceipt is an MCP server listed in the public MCP registry as dev.pages.wayreceipt/wayreceipt. Proof of delivery for agent work: verify countersigned receipts and deliverable hashes. Free. This page covers its hosted endpoint (https://wayreceipt.pages.dev/mcp).

### Is the Wayreceipt MCP server safe to use?

Wayreceipt scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Wayreceipt MCP server expose?

Wayreceipt exposes 4 tools: verify_delivery_receipt, lookup_delivery_receipt, log_stats, publish_delivery_receipt. Their descriptions and schemas cost roughly 482 tokens of context every time the server is loaded.

### Does the Wayreceipt MCP server require authentication?

No. We connected to Wayreceipt without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Wayreceipt MCP server still maintained?

Wayreceipt is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Wayreceipt MCP server?

VerifyMCP ran 13 checks on Wayreceipt, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://wayreceipt.pages.dev/mcp
- Website: https://wayreceipt.pages.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-pages-wayreceipt-wayreceipt/wayreceipt.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-pages-wayreceipt-wayreceipt/wayreceipt/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-pages-wayreceipt-wayreceipt/wayreceipt.json
- HTML version of this page: https://verifymcp.io/servers/dev-pages-wayreceipt-wayreceipt/wayreceipt