# Agent Receipt Verify (mcpb · agent-receipt-verify-0.2.1.mcpb)

Checks x402 endpoint conformance before an agent pays, and links the receipt to its settlement.

- Trust score: 42/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- mcpb · `agent-receipt-verify-0.2.1.mcpb`: 42/100 (this document), [markdown](https://verifymcp.io/servers/holistis-agent-receipt-verify/agent-receipt-verify.md), [page](https://verifymcp.io/servers/holistis-agent-receipt-verify/agent-receipt-verify)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/holistis/agent-receipt-verify/releases/download/v0.2.1/agent-receipt-verify-0.2.1.mcpb`
- Version: `0.2.1`
- Transport: `stdio`
- SHA-256: `cd7fc4f8a07c1b2d9ab8e9ef67deefeff5f11b33a80925d4d84b25880fe0ce68`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-10-18.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 310 tokens (~155/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Agent Receipt Verify MCP server?

Agent Receipt Verify ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, cd7fc4f8a07c1b2d9ab8e9ef67deefeff5f11b33a80925d4d84b25880fe0ce68; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/holistis/agent-receipt-verify/releases/download/v0.2.1/agent-receipt-verify-0.2.1.mcpb`
- SHA-256: `cd7fc4f8a07c1b2d9ab8e9ef67deefeff5f11b33a80925d4d84b25880fe0ce68`

### Verify on macOS / Linux

```bash
echo "cd7fc4f8a07c1b2d9ab8e9ef67deefeff5f11b33a80925d4d84b25880fe0ce68  agent-receipt-verify-0.2.1.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\agent-receipt-verify-0.2.1.mcpb).Hash -eq "cd7fc4f8a07c1b2d9ab8e9ef67deefeff5f11b33a80925d4d84b25880fe0ce68"
```

## 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-10-18 (score 42, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-17 (score 42)

First indexed and scored.

## MCP tools (2)

### `check_x402_endpoint` (~136 tokens)

Check a paid x402 endpoint BEFORE paying it. Sends exactly one request, never pays, and reports which levels of the published conformance ladder it reaches: does it ask for payment the way x402 says, does it declare the offer-receipt extension, and does the signature on its offer actually verify. Levels that need a real settlement are reported as not measured, never as failed.

Input parameters:

- `method` (string): HTTP method the endpoint expects. Defaults to POST. Use GET for a GET-only route.
- `url` (string, required): The paid endpoint to check, for example https://api.example.com/paid/thing

### `link_receipt_to_settlement` (~174 tokens)

Check AFTER paying that a version 2 offer-receipt belongs to exactly one real on-chain settlement. Takes the signed receipt payload plus the authorization salt the seller returned outside it, and resolves the salted commitment against live chain state. Answers linked, not linked, or could-not-check, and never guesses between them.

Input parameters:

- `asset` (string, required): The token contract from the accepts entry that was paid, for example the USDC address
- `payload` (object, required): The signed receipt payload, the object with version, network, payer and authorizationCommitment
- `rpcUrl` (string): Optional. An RPC endpoint to use instead of the public default for that network.
- `salt` (string, required): The authorizationSalt from extensions["offer-receipt"].info, which is deliberately not inside the signed payload

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/holistis-agent-receipt-verify/agent-receipt-verify#diagnostics

## Score history

- 2026-10-18: 42
- 2026-10-17: 42

## Common questions

### What is the Agent Receipt Verify MCP server?

Agent Receipt Verify is an MCP server listed in the public MCP registry as io.github.holistis/agent-receipt-verify. Checks x402 endpoint conformance before an agent pays, and links the receipt to its settlement. This page covers its MCPB bundle (https://github.com/holistis/agent-receipt-verify/releases/download/v0.2.1/agent-receipt-verify-0.2.1.mcpb).

### Is the Agent Receipt Verify MCP server safe to use?

Agent Receipt Verify scores 42 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 Agent Receipt Verify MCP server expose?

Agent Receipt Verify exposes 2 tools: check_x402_endpoint, link_receipt_to_settlement. Their descriptions and schemas cost roughly 310 tokens of context every time the server is loaded.

### What licence is the Agent Receipt Verify MCP server under?

Agent Receipt Verify declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/holistis/agent-receipt-verify
- Website: https://github.com/holistis/agent-receipt-verify/blob/main/CONFORMANCE.md
- Changelog RSS feed: https://verifymcp.io/servers/holistis-agent-receipt-verify/agent-receipt-verify.xml
- Changelog JSON feed: https://verifymcp.io/servers/holistis-agent-receipt-verify/agent-receipt-verify.json
- HTML version of this page: https://verifymcp.io/servers/holistis-agent-receipt-verify/agent-receipt-verify