Vouchwell
NPM · VOUCHWELL
Read, verify and export a tamper-evident log of what an AI agent did. Read-only.
Available components
Last scanned (18 hours ago)
Scores higher than 94% of npm servers
Category Security
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 2 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Vouchwell/vouchwell). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 21 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 557 tokens (~111/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- Package version: 0.7.0 → 0.8.0 functional
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +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.
- 25 Oct 26 +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.
- 23 Oct 26 +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.
- 21 Oct 26 +3
- Stability: unverified → 0.23 ▲ functional
- 14 Oct 26 +32
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- Package version: 0.7.0 → 0.8.0 functional
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 4 Nov 2026 · Analysed npm/vouchwell@0.8.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Vouchwell/vouchwell |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Vouchwell/vouchwell/.github/workflows/release.yml@refs/tags/v0.8.0 |
| Rekor log index | 3246887217 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:40ff7929238738a45017dd60c58c8b9f735c29392ff091d556bc88cb7614ce58a894f8ad0d93a30c925b9d83b454368e401a8765dea9248c887926f15 |
Background: How many MCP packages publish verified provenance →
Dependencies 2 packages
| Packages resolved | 2 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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_bundle Check an evidence bundle ~99
Verify a Vouchwell evidence bundle file using nothing but the file itself. Pin the signer with log_keys (kid=publicKey, as the log owner published them) to also prove who signed it.
| Name | Type | Req | Description |
|---|---|---|---|
| log_keys | object | – | Trusted signing keys, kid → base64url public key. Without them, the bundle is checked against the keys it carries. |
| path | string | yes | The bundle file, relative to the working directory or absolute. |
No output schema declared.
No examples provided.
export_evidence Write an evidence bundle ~131
Write the log as a new evidence bundle file anyone can verify offline with `vw check`; the log itself is not changed. It holds no payloads and no salts; argument previews, if the log records them, are included. Refuses to overwrite an existing file.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Where to write it, relative to the working directory (default: vouchwell-<log>-<time>.bundle.json). |
| session | string | – | Only this session's receipts (a filtered bundle). |
| since | string | – | Only receipts from this ISO date or time on (a filtered bundle). |
No output schema declared.
No examples provided.
log_entries Recent receipts ~161
The most recent receipts in the Vouchwell log: what was called, when, and whether the policy allowed, refused or escalated it. Filters narrow it to refusals, calls monitor mode would have blocked, calls that never finished, a tool, or a session.
| Name | Type | Req | Description |
|---|---|---|---|
| denied | boolean | – | Only calls the policy refused or escalated. |
| session | string | – | Only this session. |
| tail | integer | – | How many of the latest matching receipts to return (default 20). |
| target | string | – | Only tools whose name contains this text. |
| unfinished | boolean | – | Only calls that were authorised and sent but never reported a result. |
| would_block | boolean | – | Only calls monitor mode let through that the policy would have blocked. |
No output schema declared.
No examples provided.
log_stats Log totals ~41
Totals for the Vouchwell log: receipts, allowed, refused, escalated, tool errors, what monitor mode would have stopped, and the busiest tools.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_log Verify the log ~52
Check every signature, hash-chain link and signed checkpoint in the Vouchwell log. ok: false means the log was altered after it was written: report it as evidence of tampering, never as something to repair.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Vouchwell MCP server?
Vouchwell runs locally as an npm package, launched with npx -y vouchwell. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · vouchwell
claude mcp add vouchwell-vouchwell -- npx -y vouchwell
What is the Vouchwell MCP server?
Vouchwell is an MCP server listed in the public MCP registry as io.github.Vouchwell/vouchwell. Read, verify and export a tamper-evident log of what an AI agent did. Read-only. This page covers its npm package (vouchwell).
Is the Vouchwell MCP server safe to use?
Vouchwell scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Vouchwell MCP server expose?
Vouchwell exposes 5 tools: log_entries, verify_log, log_stats, check_bundle, export_evidence. Their descriptions and schemas cost roughly 484 tokens of context every time the server is loaded.
Is the Vouchwell MCP server still maintained?
Vouchwell is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Vouchwell MCP server under?
Vouchwell 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.