# io.github.zaojiaoci/verified-rec (npm · verified-rec)

Hash-chained audit ledger for AI agent work — record, verify and replay what the agent did.

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

## Components

- npm · `verified-rec`: 68/100 (this document), [markdown](https://verifymcp.io/servers/zaojiaoci-verified-rec/verified-rec.md), [page](https://verifymcp.io/servers/zaojiaoci-verified-rec/verified-rec)

## Channel facts

- Registry: `npm`
- Package: `verified-rec`
- Version: `0.1.0`
- Transport: `stdio`

## 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-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - 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.
  - Actively maintained (last published 8 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 524 tokens (~104/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 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.

### Claude

```bash
claude mcp add zaojiaoci-verified-rec -- npx -y verified-rec
```

### Cursor

```json
{
  "mcpServers": {
    "zaojiaoci-verified-rec": {
      "command": "npx",
      "args": [
        "-y",
        "verified-rec"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "zaojiaoci-verified-rec": {
      "command": "npx",
      "args": [
        "-y",
        "verified-rec"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add zaojiaoci-verified-rec -- npx -y verified-rec
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "zaojiaoci-verified-rec": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "verified-rec"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add zaojiaoci-verified-rec --command npx --arg -y --arg verified-rec
```

### Hermes

```yaml
mcp_servers:
  zaojiaoci-verified-rec:
    command: "npx"
    args: ["-y", "verified-rec"]
```

### Netclaw

```json
{
  "McpServers": {
    "zaojiaoci-verified-rec": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "verified-rec"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add zaojiaoci-verified-rec -t stdio -c npx -a -y verified-rec
```

### Other

```json
{
  "mcpServers": {
    "zaojiaoci-verified-rec": {
      "command": "npx",
      "args": [
        "-y",
        "verified-rec"
      ]
    }
  }
}
```

## 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-28 (score 68, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-27 (score 53)

First indexed and scored.

## MCP tools (5)

### `ledger_start` (~117 tokens)

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).

Input parameters:

- `actor` (string): Who is writing (agent/human name), default "agent"
- `path` (string, required): File path for the new ledger, e.g. ./work.vrec
- `title` (string): What this ledger is for (recorded as the genesis entry note)

### `ledger_append` (~94 tokens)

Append one entry to a ledger. Returns the new chain head. Verifies the existing chain first — you cannot append to a broken ledger.

Input parameters:

- `action` (string, required): What happened, e.g. "deploy", "edit src/app.ts", "approve release"
- `actor` (string): Who did it, default "agent"
- `note` (string): Optional detail
- `path` (string, required): Ledger file path

### `ledger_verify` (~54 tokens)

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.

Input parameters:

- `path` (string, required): Ledger file path

### `ledger_replay` (~73 tokens)

Replay a ledger: list entries in order (optionally a seq range). Read-only; run ledger_verify to check integrity.

Input parameters:

- `from` (number): First seq to include (default 0)
- `path` (string, required): Ledger file path
- `to` (number): Last seq to include (default end)

### `game_verify_rec` (~186 tokens)

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.

Input parameters:

- `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, required): .rec recording file path

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/zaojiaoci-verified-rec/verified-rec#diagnostics

## Score history

- 2026-11-05: 68
- 2026-11-04: 68
- 2026-11-03: 68
- 2026-11-02: 68
- 2026-11-01: 68
- 2026-10-31: 68
- 2026-10-30: 68
- 2026-10-29: 68
- 2026-10-28: 68
- 2026-10-27: 53

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/verified-rec
- Socket report: https://socket.dev/npm/package/verified-rec
- Repository: https://github.com/zaojiaoci/verified-rec
- Changelog RSS feed: https://verifymcp.io/servers/zaojiaoci-verified-rec/verified-rec.xml
- Changelog JSON feed: https://verifymcp.io/servers/zaojiaoci-verified-rec/verified-rec.json
- HTML version of this page: https://verifymcp.io/servers/zaojiaoci-verified-rec/verified-rec