io.github.promptwheel-ai/logbook
NPM · @PROMPTWHEEL/LOGBOOK-MCP
Git-history memory for coding agents: reverts, weakened tests, hot spots, and unreviewed notes.
Available components
Last scanned (12 hours ago)
Scores higher than 53% of npm servers
Category Version Control
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
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 Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 966 tokens (~193/item across 5 items; 5 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 81% of tool parameters carry a description.Partial
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
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.
- 4 Nov 26 +14
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Known CVEs: fail → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Schema quality: 139 → 193 ▼ functional
- Schema quality: 139 → 185 ▼ functional
- Schema quality: 139 → 168 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: 0.86 → unverified ▼ functional
- Package version: 0.6.0 → 0.6.4 functional
- Package version: 0.6.0 → 0.6.3 functional
- Package version: 0.6.0 → 0.6.2 functional
- Package version: 0.6.0 → 0.6.1 functional
- 3 Nov 26 −17
- Malware scan: pass → unverified ▼ security
- Schema quality: pass → fail ▼ functional
- Schema quality: excellent → good functional
- Licence: MIT → Apache-2.0 functional
- Package version: 0.4.0 → 0.6.0 functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 26 Oct 26 −1
- Stability: pass → 0.93 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 20 Oct 26 +1
- Stability: 0.97 → pass security
- 19 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
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/@promptwheel/logbook-mcp@0.6.4
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 30 |
| 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 →
logbook_annotate ~221
Persist a machine-authored, explicitly unreviewed note after investigating a commit. It appears immediately in the repo digest but never enters check --diff authority. Optional quoted evidence is raw-object verified.
| Name | Type | Req | Description |
|---|---|---|---|
| by | string | – | who inferred it (model/agent name) |
| evidenceFile | string | – | required literal changed path when side=diff; omit for message |
| repo | string | – | absolute path to the git repository; defaults to the server's working directory, and must be inside it (or a root listed in LOGBOOK_MCP_ROOTS); when that directory is part of a repository (it holds f… |
| sha | string | yes | the commit being explained (any unique prefix) |
| side | string | – | required when span is present: where the exact evidence quote occurs |
| span | string | – | optional exact contiguous quote from the commit message or changed blob |
| why | string | yes | the inferred cause, one sentence, specific (max 400 chars) |
No output schema declared.
No examples provided.
logbook_audit ~118
What is STILL suppressed in HEAD and since when (blame-dated), with re-silencing fight logs. Use when asked what tests are skipped, what debt is live, or whether a suppression keeps coming back.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | – | absolute path to the git repository; defaults to the server's working directory, and must be inside it (or a root listed in LOGBOOK_MCP_ROOTS); when that directory is part of a repository (it holds f… |
No output schema declared.
No examples provided.
logbook_context ~251
Return the same filtered history order as logbook_query in compact, bounded pages for agent context. Pass all relevant paths in files; paths use OR and other filters use AND. This is deterministic delivery, not relevance ranking. Repeat identical filters with every NEXT cursor until END complete when completeness matters.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | opaque NEXT cursor from the previous page; rejects stale or changed queries |
| downgrade | number | – | min assertion downgrades |
| file | string | – | legacy single substring match against files touched |
| files | array | – | file substrings; matches events touching any supplied path |
| grep | string | – | substring match against commit subject |
| repo | string | – | absolute path to the git repository; defaults to the server's working directory, and must be inside it (or a root listed in LOGBOOK_MCP_ROOTS); when that directory is part of a repository (it holds f… |
| revert | boolean | – | – |
| since | string | – | – |
| suppress | boolean | – | only events that added suppressions |
| until | string | – | – |
| weaken | number | – | min net assertions removed |
No output schema declared.
No examples provided.
logbook_digest ~128
The repo's history digest: hotspots, do-not-retry reverts, suppression ledger, fragile areas, notable events, per-file history. Use when starting work in an unfamiliar repo, before a refactor or large change, or when deciding whether green tests can be trusted.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | – | absolute path to the git repository; defaults to the server's working directory, and must be inside it (or a root listed in LOGBOOK_MCP_ROOTS); when that directory is part of a repository (it holds f… |
No output schema declared.
No examples provided.
logbook_query ~248
Filter the full commit-event record with precision. Start with all relevant files + event type before broad grep. Repeated paths use OR; other filters use AND. Returns up to `limit` matches, default 100, with exact counts and explicit truncation recovery.
| Name | Type | Req | Description |
|---|---|---|---|
| downgrade | number | – | min assertion downgrades |
| file | string | – | legacy single substring match against files touched |
| files | array | – | file substrings; matches events touching any supplied path |
| grep | string | – | substring match against commit subject |
| limit | integer | – | at most 1000; for complete coverage page through logbook_context instead |
| repo | string | – | absolute path to the git repository; defaults to the server's working directory, and must be inside it (or a root listed in LOGBOOK_MCP_ROOTS); when that directory is part of a repository (it holds f… |
| revert | boolean | – | – |
| since | string | – | – |
| suppress | boolean | – | only events that added suppressions |
| until | string | – | – |
| weaken | number | – | min net assertions removed |
No output schema declared.
No examples provided.
How do I install the io.github.promptwheel-ai/logbook MCP server?
io.github.promptwheel-ai/logbook runs locally as an npm package, launched with npx -y @promptwheel/logbook-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @promptwheel/logbook-mcp
claude mcp add promptwheel-ai-logbook -- npx -y @promptwheel/logbook-mcp
What is the io.github.promptwheel-ai/logbook MCP server?
io.github.promptwheel-ai/logbook is an MCP server listed in the public MCP registry as io.github.promptwheel-ai/logbook. Git-history memory for coding agents: reverts, weakened tests, hot spots, and unreviewed notes. This page covers its npm package (@promptwheel/logbook-mcp).
Is the io.github.promptwheel-ai/logbook MCP server safe to use?
io.github.promptwheel-ai/logbook scores 76 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 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.promptwheel-ai/logbook MCP server expose?
io.github.promptwheel-ai/logbook exposes 5 tools: logbook_digest, logbook_annotate, logbook_audit, logbook_query, logbook_context. Their descriptions and schemas cost roughly 966 tokens of context every time the server is loaded.
Is the io.github.promptwheel-ai/logbook MCP server still maintained?
io.github.promptwheel-ai/logbook 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 io.github.promptwheel-ai/logbook MCP server under?
io.github.promptwheel-ai/logbook 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.