Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.promptwheel-ai/logbook

NPM · @PROMPTWHEEL/LOGBOOK-MCP · SCANNED SEP 20

Local Git-history memory for coding agents: reverts, suppressions, hotspots, and annotations.

0 this week 83 Trust /100
Trust breakdown (7 categories)

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
  • 31 of 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 594 tokens (~118/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 Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 73% 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
Install

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

# add to Claude Code
claude mcp add promptwheel-ai-logbook -- npx -y @promptwheel/logbook-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "promptwheel-ai-logbook": {
      "command": "npx",
      "args": [
        "-y",
        "@promptwheel/logbook-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "promptwheel-ai-logbook": {
      "command": "npx",
      "args": [
        "-y",
        "@promptwheel/logbook-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add promptwheel-ai-logbook -- npx -y @promptwheel/logbook-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "promptwheel-ai-logbook": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@promptwheel/logbook-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add promptwheel-ai-logbook --command npx --arg -y --arg @promptwheel/logbook-mcp
# ~/.hermes/config.yaml
mcp_servers:
  promptwheel-ai-logbook:
    command: "npx"
    args: ["-y", "@promptwheel/logbook-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "promptwheel-ai-logbook": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@promptwheel/logbook-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add promptwheel-ai-logbook -t stdio -c npx -a -y @promptwheel/logbook-mcp
// mcp.json
{
  "mcpServers": {
    "promptwheel-ai-logbook": {
      "command": "npx",
      "args": [
        "-y",
        "@promptwheel/logbook-mcp"
      ]
    }
  }
}
Changelog

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.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 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.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 13 Sept 26 0
    • Security disclosure: fail → unverified functional
  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 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.

Diagnostics

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 20 Sept 2026 · Analysed npm/@promptwheel/logbook-mcp@0.4.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 97 packages
Packages resolved 97
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~594 tokens

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 →

Tool Tokens
logbook_annotate ~131

Persist WHY a commit happened (lazy enrichment). When you investigate a do-not-retry revert or a suppression — its failure mode, its cause — save the finding so the next session gets it for free instead of re-investigating. Judgments, not records: attributed and dated.

NameTypeReqDescription
bystringwho inferred it (model/agent name)
repostringyesabsolute path to the git repository
shastringyesthe commit being explained (any unique prefix)
whystringyesthe inferred cause, one sentence, specific (max 400 chars)

No output schema declared.

No examples provided.

logbook_audit ~67

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.

NameTypeReqDescription
repostringyesabsolute path to the git repository

No output schema declared.

No examples provided.

logbook_context ~162

Return the same filtered history order as logbook_query in compact, bounded pages for agent context. This is deterministic delivery, not relevance ranking. Follow NEXT cursors until END complete when completeness matters.

NameTypeReqDescription
cursorstringopaque NEXT cursor from the previous page; rejects stale or changed queries
downgradenumbermin assertion downgrades
filestringsubstring match against files touched
grepstringsubstring match against commit subject
repostringyesabsolute path to the git repository
revertboolean
sincestring
suppressbooleanonly events that added suppressions
untilstring
weakennumbermin net assertions removed

No output schema declared.

No examples provided.

logbook_digest ~77

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.

NameTypeReqDescription
repostringyesabsolute path to the git repository

No output schema declared.

No examples provided.

logbook_query ~157

Filter the full commit-event record with precision. Start with file + event type (for example file and revert) before broad grep. Returns up to `limit` matches, default 100, with exact counts and explicit truncation recovery.

NameTypeReqDescription
downgradenumbermin assertion downgrades
filestringsubstring match against files touched
grepstringsubstring match against commit subject
limitinteger
repostringyesabsolute path to the git repository
revertboolean
sincestring
suppressbooleanonly events that added suppressions
untilstring
weakennumbermin net assertions removed

No output schema declared.

No examples provided.

Common questions

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. Local Git-history memory for coding agents: reverts, suppressions, hotspots, and annotations. 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 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 594 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 20 September 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 MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.