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.
Available components
Last scanned (18 hours ago)
Scores higher than 77% of MCPB servers
Category Crypto and Web3
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. How we score → Why this is hard to score →
Supply Chain Security0
- 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.Unverified
- 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).Unverified
- Install-script risk not yet assessed.Unverified
- 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).Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Oct 26 42
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Analysed mcpb/https://github.com/holistis/agent-receipt-verify/releases/download/v0.2.1/agent-receipt-verify-0.2.1.mcpb@0.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_x402_endpoint ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | – | HTTP method the endpoint expects. Defaults to POST. Use GET for a GET-only route. |
| url | string | yes | The paid endpoint to check, for example https://api.example.com/paid/thing |
No output schema declared.
No examples provided.
link_receipt_to_settlement ~174
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.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | The token contract from the accepts entry that was paid, for example the USDC address |
| payload | object | yes | 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 | yes | The authorizationSalt from extensions["offer-receipt"].info, which is deliberately not inside the signed payload |
No output schema declared.
No examples provided.
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.
mcpb · agent-receipt-verify-0.2.1.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
cd7fc4f8a07c1b2d9ab8e9ef67deefeff5f11b33a80925d4d84b25880fe0ce68
macOS / Linux
echo "cd7fc4f8a07c1b2d9ab8e9ef67deefeff5f11b33a80925d4d84b25880fe0ce68 agent-receipt-verify-0.2.1.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\agent-receipt-verify-0.2.1.mcpb).Hash -eq "cd7fc4f8a07c1b2d9ab8e9ef67deefeff5f11b33a80925d4d84b25880fe0ce68"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
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.