io.github.zaojiaoci/verified-rec
NPM · VERIFIED-REC
Hash-chained audit ledger for AI agent work — record, verify and replay what the agent did.
Available components
Last scanned (35 minutes ago)
Scores higher than 36% 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency32
- 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
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 8 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 524 tokens (~104/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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 5 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.
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 53
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 5 Nov 2026 · Analysed npm/verified-rec@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
game_verify_rec ~186
Replay a game .rec recording through versioned deterministic kernels and compute its chain head. With expectedHead this is an integrity check with three outcomes: "reproduced" (some registered kernel reproduces the head — authentic), "not-reproduced" (no registered kernel does — tampered, or from an unregistered game version), "premise-broken" (facts digest matches no kernel). Without expectedHead it proves the recording is replayable and reports its head plus the kernel version used. Old recordings verify against old kernels — kernel upgrades never falsify them.
| Name | Type | Req | Description |
|---|---|---|---|
| expectedHead | string | – | Optional: the claimed 64-hex chain head to check against |
| kernelVersion | string | – | Optional: verify with one specific registered kernel version (e.g. "0.1"); default tries all |
| path | string | yes | .rec recording file path |
No output schema declared.
No examples provided.
ledger_append ~94
Append one entry to a ledger. Returns the new chain head. Verifies the existing chain first — you cannot append to a broken ledger.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | What happened, e.g. "deploy", "edit src/app.ts", "approve release" |
| actor | string | – | Who did it, default "agent" |
| note | string | – | Optional detail |
| path | string | yes | Ledger file path |
No output schema declared.
No examples provided.
ledger_replay ~73
Replay a ledger: list entries in order (optionally a seq range). Read-only; run ledger_verify to check integrity.
| Name | Type | Req | Description |
|---|---|---|---|
| from | number | – | First seq to include (default 0) |
| path | string | yes | Ledger file path |
| to | number | – | Last seq to include (default end) |
No output schema declared.
No examples provided.
ledger_start ~117
Start a new append-only hash-chained ledger file (.vrec). Each entry links to the previous one by hash; anyone can later verify the file was not tampered with. Fails if the file already exists (ledgers never overwrite).
| Name | Type | Req | Description |
|---|---|---|---|
| actor | string | – | Who is writing (agent/human name), default "agent" |
| path | string | yes | File path for the new ledger, e.g. ./work.vrec |
| title | string | – | What this ledger is for (recorded as the genesis entry note) |
No output schema declared.
No examples provided.
ledger_verify ~54
Verify a ledger end-to-end: recompute every entry hash, check the links and sequence. Returns ok=true with the chain head, or the first broken line number and why.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Ledger file path |
No output schema declared.
No examples provided.
How do I install the io.github.zaojiaoci/verified-rec MCP server?
io.github.zaojiaoci/verified-rec runs locally as an npm package, launched with npx -y verified-rec. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · verified-rec
claude mcp add zaojiaoci-verified-rec -- npx -y verified-rec
What is the io.github.zaojiaoci/verified-rec MCP server?
io.github.zaojiaoci/verified-rec is an MCP server listed in the public MCP registry as io.github.zaojiaoci/verified-rec. Hash-chained audit ledger for AI agent work, record, verify and replay what the agent did. This page covers its npm package (verified-rec).
Is the io.github.zaojiaoci/verified-rec MCP server safe to use?
io.github.zaojiaoci/verified-rec scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.zaojiaoci/verified-rec MCP server expose?
io.github.zaojiaoci/verified-rec exposes 5 tools: ledger_start, ledger_append, ledger_verify, ledger_replay, game_verify_rec. Their descriptions and schemas cost roughly 524 tokens of context every time the server is loaded.
Is the io.github.zaojiaoci/verified-rec MCP server still maintained?
io.github.zaojiaoci/verified-rec 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.