# logbook-mcp (npm · logbook-mcp)

Project memory across sessions for AI agents. A queryable decision log in the repo.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- npm · `logbook-mcp`: 63/100 (this document), [markdown](https://verifymcp.io/servers/abduljabbarbxr-logbook-mcp/logbook-mcp.md), [page](https://verifymcp.io/servers/abduljabbarbxr-logbook-mcp/logbook-mcp)

## Channel facts

- Registry: `npm`
- Package: `logbook-mcp`
- Version: `0.1.3`
- 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-09-21.

- **Supply Chain Security**: 98/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.
  - 31 of 95 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 362 tokens (~72/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**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 88% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - 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 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.

### Claude

```bash
claude mcp add abduljabbarbxr-logbook-mcp -- npx -y logbook-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "abduljabbarbxr-logbook-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "logbook-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "abduljabbarbxr-logbook-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "logbook-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add abduljabbarbxr-logbook-mcp -- npx -y logbook-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add abduljabbarbxr-logbook-mcp --command npx --arg -y --arg logbook-mcp
```

### Hermes

```yaml
mcp_servers:
  abduljabbarbxr-logbook-mcp:
    command: "npx"
    args: ["-y", "logbook-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "abduljabbarbxr-logbook-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "logbook-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add abduljabbarbxr-logbook-mcp -t stdio -c npx -a -y logbook-mcp
```

### Other

```json
{
  "mcpServers": {
    "abduljabbarbxr-logbook-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "logbook-mcp"
      ]
    }
  }
}
```

## 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-09-16 (score 63)

First indexed and scored.

## MCP tools (5)

### `logbook.record` (~120 tokens)

Record a decision, finding, or gotcha into the project memory. The entry is persisted in the repository so future sessions can recall it.

Input parameters:

- `body` (string, required): 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, required): Short title for the entry
- `type` (string)

### `logbook.search` (~107 tokens)

Search the project memory by text, scope, tags, or type. Returns matching entries with their timestamps.

Input parameters:

- `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

### `logbook.recent` (~42 tokens)

Return the most recent entries from the project memory.

Input parameters:

- `limit` (integer)
- `path` (string): Repository root. Defaults to the current directory.

### `logbook.stats` (~46 tokens)

Summarize the project memory: total entries, counts by type and scope, and the logbook location.

Input parameters:

- `path` (string): Repository root. Defaults to the current directory.

### `logbook.forget` (~47 tokens)

Remove an entry from the project memory by id.

Input parameters:

- `id` (string, required): The entry id to remove
- `path` (string): Repository root. Defaults to the current directory.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/abduljabbarbxr-logbook-mcp/logbook-mcp#diagnostics

## Score history

- 2026-09-21: 63
- 2026-09-20: 63
- 2026-09-19: 63
- 2026-09-18: 63
- 2026-09-17: 63
- 2026-09-16: 63

## Common questions

### 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 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 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 21 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 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.

## Links

- npm package: https://www.npmjs.com/package/logbook-mcp
- Socket report: https://socket.dev/npm/package/logbook-mcp
- Changelog RSS feed: https://verifymcp.io/servers/abduljabbarbxr-logbook-mcp/logbook-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/abduljabbarbxr-logbook-mcp/logbook-mcp.json
- HTML version of this page: https://verifymcp.io/servers/abduljabbarbxr-logbook-mcp/logbook-mcp