# GhostPaw Grimoire (npm · @ghostpaw/grimoire)

Local procedural knowledge with spells, notes, and revision history.

- Trust score: 76/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- npm · `@ghostpaw/grimoire`: 76/100 (this document), [markdown](https://verifymcp.io/servers/ghostpawjs-grimoire/ghostpaw-grimoire.md), [page](https://verifymcp.io/servers/ghostpawjs-grimoire/ghostpaw-grimoire)

## Channel facts

- Registry: `npm`
- Package: `@ghostpaw/grimoire`
- Version: `0.3.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-10-25.

- **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**: 71/100
  - Repository check failed: the declared repository URL redirects; it must resolve directly.
  - Cryptographically verified build provenance (signed, bound to GhostPawJS/grimoire).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1245 tokens (~113/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - 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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (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 GhostPaw Grimoire MCP server?

GhostPaw Grimoire runs locally as an npm package, launched with npx -y @ghostpaw/grimoire. 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 ghostpawjs-grimoire -- npx -y @ghostpaw/grimoire
```

### Cursor

```json
{
  "mcpServers": {
    "ghostpawjs-grimoire": {
      "command": "npx",
      "args": [
        "-y",
        "@ghostpaw/grimoire"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ghostpawjs-grimoire": {
      "command": "npx",
      "args": [
        "-y",
        "@ghostpaw/grimoire"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ghostpawjs-grimoire -- npx -y @ghostpaw/grimoire
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add ghostpawjs-grimoire --command npx --arg -y --arg @ghostpaw/grimoire
```

### Hermes

```yaml
mcp_servers:
  ghostpawjs-grimoire:
    command: "npx"
    args: ["-y", "@ghostpaw/grimoire"]
```

### Netclaw

```json
{
  "McpServers": {
    "ghostpawjs-grimoire": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@ghostpaw/grimoire"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add ghostpawjs-grimoire -t stdio -c npx -a -y @ghostpaw/grimoire
```

### Other

```json
{
  "mcpServers": {
    "ghostpawjs-grimoire": {
      "command": "npx",
      "args": [
        "-y",
        "@ghostpaw/grimoire"
      ]
    }
  }
}
```

## 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-25 (score 76, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-24 (score 61)

First indexed and scored.

## MCP tools (11)

### `search_grimoire` (~79 tokens)

Search the grimoire for spells by name or description.

Use when: When looking for spells matching a keyword, topic, or partial name.
Not for: When you already know the exact spell path — use inspect_grimoire_item instead.

Input parameters:

- `chapters` (array): Chapters to filter by
- `query` (string, required): Search query

### `review_grimoire` (~105 tokens)

Review a dashboard view of the grimoire — chapters, health, resonance, notes, drafts, validation, provenance, or index.

Use when: When you need a broad overview of grimoire state from a specific angle.
Not for: When you need details about a single spell — use inspect_grimoire_item instead.

Input parameters:

- `limit` (integer): Maximum results to return
- `now` (integer): Timestamp override
- `view` (string, required): Review view

### `inspect_grimoire_item` (~72 tokens)

Inspect a single spell in detail, including tier, resonance, validation, provenance, and history.

Use when: When you need full details about a specific spell by its path.
Not for: When you want a broad overview — use review_grimoire instead.

Input parameters:

- `path` (string, required): Spell path

### `inscribe_spell` (~88 tokens)

Create a new spell in the grimoire.

Use when: When writing a new skill/spell into the grimoire from scratch.
Not for: When updating existing spell content — use update_spell to edit, then hone_spell to seal.

Input parameters:

- `chapter` (string): Chapter name
- `content` (string, required): Spell body content in markdown
- `name` (string, required): Spell name

### `update_spell` (~102 tokens)

Write new content to an existing spell, leaving the change uncommitted.

Use when: When incorporating note evidence or improvements into an existing spell body. Follow with hone_spell to seal and advance rank.
Not for: When creating a brand-new spell — use inscribe_spell instead. When you only want to checkpoint existing edits — use hone_spell directly.

Input parameters:

- `content` (string, required): Full spec-compliant SKILL.md content
- `path` (string, required): Spell path

### `hone_spell` (~107 tokens)

Seal pending spell changes into a git commit, advancing spell ranks.

Use when: After editing spell content with update_spell, to checkpoint changes and evolve spell tiers. Pass note_ids to mark which notes were absorbed during this honing session.
Not for: When no changes have been made — the tool will return a no-op.

Input parameters:

- `message` (string): Commit message
- `note_ids` (array): Note IDs to distill after sealing
- `paths` (array): Spell paths to seal

### `manage_spell` (~170 tokens)

Manage spells: shelve, unshelve, move, delete, repair, repair all, or rollback to a previous seal.

Use when: When you need to reorganize, archive, restore, move, remove, fix, or revert spells.
Not for: When creating new spells — use inscribe_spell. When sealing changes — use hone_spell.

Input parameters:

- `action` (string, required): The management action to perform: shelve, unshelve, move, delete, repair, repair_all, or rollback.
- `path` (string): Spell path — required for all actions except repair_all.
- `ref` (string): Git commit hash to revert to — required for rollback. Use inspect_grimoire_item to find seal hashes from history.
- `target` (string): Target path — required for move.

### `drop_note` (~87 tokens)

Drop an observation note into the grimoire for later cataloguing.

Use when: When capturing an insight, observation, or piece of evidence about a spell topic.
Not for: When creating or editing a spell directly — use inscribe_spell or hone_spell.

Input parameters:

- `content` (string, required): Note content
- `domain` (string): Topic domain
- `source` (string, required): Source identifier

### `manage_draft` (~152 tokens)

Submit, approve, or dismiss spell drafts.

Use when: When managing the draft pipeline — proposing new spells from notes, approving, or dismissing drafts.
Not for: When creating spells directly — use inscribe_spell instead.

Input parameters:

- `action` (string, required): Draft action to perform: submit, approve, or dismiss.
- `chapter` (string): Chapter for the potential spell — required for submit.
- `draftId` (integer): Draft ID — required for approve and dismiss.
- `noteIds` (array): Note IDs backing this draft — required for submit.
- `rationale` (string): Why this draft should become a spell — required for submit.
- `title` (string): Draft title — required for submit.

### `run_catalogue` (~87 tokens)

Run the full catalogue maintenance pass — detect stale/dormant/oversized spells, route notes, cluster orphans, compute health.

Use when: Periodically or after dropping many notes to process and analyze grimoire health.
Not for: When just reading health data — use review_grimoire with view "health" instead.

Input parameters:

- `now` (integer): Timestamp override (ms)

### `scout_skills` (~150 tokens)

Scout, search, adopt, and update spells from external sources.

Use when: When discovering new skills from AgentSkillHub or GitHub, importing them, or checking for upstream updates.
Not for: When working with local spells only — use inscribe_spell or hone_spell.

Input parameters:

- `action` (string, required): Scout action to perform: adopt (import from source), search (find skills), check_updates, or apply_update.
- `chapter` (string): Chapter for adopted spells — optional for adopt.
- `path` (string): Spell path — required for apply_update.
- `query` (string): Search query — required for search.
- `source` (string): Source URL or identifier — required for adopt.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/ghostpawjs-grimoire/ghostpaw-grimoire#diagnostics

## Score history

- 2026-10-25: 76
- 2026-10-24: 61

## Common questions

### What is the GhostPaw Grimoire MCP server?

GhostPaw Grimoire is an MCP server listed in the public MCP registry as io.github.GhostPawJS/grimoire. Local procedural knowledge with spells, notes, and revision history. This page covers its npm package (@ghostpaw/grimoire).

### Is the GhostPaw Grimoire MCP server safe to use?

GhostPaw Grimoire scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 GhostPaw Grimoire MCP server expose?

GhostPaw Grimoire exposes 11 tools: search_grimoire, review_grimoire, inspect_grimoire_item, inscribe_spell, update_spell, and 6 more. Their descriptions and schemas cost roughly 1,199 tokens of context every time the server is loaded.

### Is the GhostPaw Grimoire MCP server still maintained?

GhostPaw Grimoire is still listed as active in the MCP registry. We last reached this channel on 25 October 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 GhostPaw Grimoire MCP server under?

GhostPaw Grimoire 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/@ghostpaw/grimoire
- Socket report: https://socket.dev/npm/package/@ghostpaw/grimoire
- Changelog RSS feed: https://verifymcp.io/servers/ghostpawjs-grimoire/ghostpaw-grimoire.xml
- Changelog JSON feed: https://verifymcp.io/servers/ghostpawjs-grimoire/ghostpaw-grimoire.json
- HTML version of this page: https://verifymcp.io/servers/ghostpawjs-grimoire/ghostpaw-grimoire