logbook-mcp
NPM · LOGBOOK-MCP
Project memory across sessions for AI agents. A queryable decision log in the repo.
Available components
Last scanned (6 hours ago)
Scores higher than 48% of npm servers
Category Memory and Knowledge
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 Security98
- 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
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 43 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 362 tokens (~72/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 Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "logbook.forget" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- 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.
- 5 Nov 26 −3
- Stability: pass → 0.77 functional
- 30 Oct 26 +1
- Stability: 0.97 → pass security
- 29 Oct 26 −1
- Stability: pass → 0.97 functional
- 23 Oct 26 +1
- Stability: 0.97 → pass security
- 22 Oct 26 −1
- Stability: pass → 0.97 functional
- 16 Oct 26 +1
- Stability: 0.97 → pass security
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Oct 26 +4
No change was recorded against any check on this day. Stability & Change Management went from 60 to 83. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
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/logbook-mcp@0.1.3
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 92 packages
| Packages resolved | 92 |
|---|---|
| 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.forget ~47
Remove an entry from the project memory by id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The entry id to remove |
| path | string | – | Repository root. Defaults to the current directory. |
No output schema declared.
No examples provided.
logbook.recent ~42
Return the most recent entries from the project memory.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| path | string | – | Repository root. Defaults to the current directory. |
No output schema declared.
No examples provided.
logbook.record ~120
Record a decision, finding, or gotcha into the project memory. The entry is persisted in the repository so future sessions can recall it.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The decision, finding, or gotcha to remember |
| path | string | – | Repository root where the logbook lives. Defaults to the current directory. |
| scope | string | – | Optional scope such as deploy, build, auth |
| tags | array | – | Tags for later search |
| title | string | yes | Short title for the entry |
| type | string | – | – |
No output schema declared.
No examples provided.
logbook.search ~107
Search the project memory by text, scope, tags, or type. Returns matching entries with their timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum entries to return |
| path | string | – | Repository root. Defaults to the current directory. |
| query | string | – | Text to match against titles and bodies |
| scope | string | – | Filter by scope |
| tags | array | – | Filter by tags, entries matching any tag are returned |
| type | string | – | Filter by type |
No output schema declared.
No examples provided.
logbook.stats ~46
Summarize the project memory: total entries, counts by type and scope, and the logbook location.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Repository root. Defaults to the current directory. |
No output schema declared.
No examples provided.
How do I install the logbook-mcp server?
logbook-mcp runs locally as an npm package, launched with npx -y 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 · logbook-mcp
claude mcp add abduljabbarbxr-logbook-mcp -- npx -y logbook-mcp
What is the logbook-mcp server?
logbook-mcp is listed in the public MCP registry as io.github.AbduljabbarBXR/logbook-mcp. Project memory across sessions for AI agents. A queryable decision log in the repo. This page covers its npm package (logbook-mcp).
Is the logbook-mcp server safe to use?
logbook-mcp scores 74 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 logbook-mcp server expose?
logbook-mcp exposes 5 tools: logbook.record, logbook.search, logbook.recent, logbook.stats, logbook.forget. Their descriptions and schemas cost roughly 362 tokens of context every time the server is loaded.
Is the logbook-mcp server still maintained?
logbook-mcp 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.
What licence is the logbook-mcp server under?
logbook-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.