GhostPaw Grimoire
NPM · @GHOSTPAW/GRIMOIRE
Local procedural knowledge with spells, notes, and revision history.
Available components
Last scanned (2 hours ago)
Scores higher than 57% 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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency71
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to GhostPawJS/grimoire). View diagnostics → Pass
- Clear OSI-approved license (MIT).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 Usability77
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
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.
- 25 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 24 Oct 26 61
First indexed and scored.
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 25 Oct 2026 · Analysed npm/@ghostpaw/grimoire@0.3.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | GhostPawJS/grimoire |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/GhostPawJS/grimoire/.github/workflows/publish.yml@refs/tags/v0.3.0 |
| Rekor log index | 3440911902 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:dfc67b85d5c707669b553aa29ac3fbb697d78e59c0e39144f6a1ab7e6a1515ec0b5e692999372cf333f535cd1a9c6f81d00bdf8334f25d151c6a6d371 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
drop_note ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Note content |
| domain | string | – | Topic domain |
| source | string | yes | Source identifier |
No output schema declared.
No examples provided.
hone_spell ~107
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.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | Commit message |
| note_ids | array | – | Note IDs to distill after sealing |
| paths | array | – | Spell paths to seal |
No output schema declared.
No examples provided.
inscribe_spell ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chapter | string | – | Chapter name |
| content | string | yes | Spell body content in markdown |
| name | string | yes | Spell name |
No output schema declared.
No examples provided.
inspect_grimoire_item ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Spell path |
No output schema declared.
No examples provided.
manage_draft ~152
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | 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. |
No output schema declared.
No examples provided.
manage_spell ~170
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | 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. |
No output schema declared.
No examples provided.
review_grimoire ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum results to return |
| now | integer | – | Timestamp override |
| view | string | yes | Review view |
No output schema declared.
No examples provided.
run_catalogue ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| now | integer | – | Timestamp override (ms) |
No output schema declared.
No examples provided.
scout_skills ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | 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. |
No output schema declared.
No examples provided.
search_grimoire ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chapters | array | – | Chapters to filter by |
| query | string | yes | Search query |
No output schema declared.
No examples provided.
update_spell ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Full spec-compliant SKILL.md content |
| path | string | yes | Spell path |
No output schema declared.
No examples provided.
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.
npm · @ghostpaw/grimoire
claude mcp add ghostpawjs-grimoire -- npx -y @ghostpaw/grimoire
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.