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.jannks/handbook

NPM · @AH-OH/HANDBOOK-MCP-SERVER · SCANNED SEP 20

MCP server for the Handbook API – manage handbook entries via CRUD, overview and tag search.

0 this week 85 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 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability85
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 733 tokens (~104/item across 7 items; 7 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 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 7 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.jannks/handbook MCP server?

io.github.jannks/handbook runs locally as an npm package, launched with npx -y @ah-oh/handbook-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @ah-oh/handbook-mcp-server

# add to Claude Code
claude mcp add jannks-handbook -- npx -y @ah-oh/handbook-mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "jannks-handbook": {
      "command": "npx",
      "args": [
        "-y",
        "@ah-oh/handbook-mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "jannks-handbook": {
      "command": "npx",
      "args": [
        "-y",
        "@ah-oh/handbook-mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add jannks-handbook -- npx -y @ah-oh/handbook-mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jannks-handbook": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@ah-oh/handbook-mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add jannks-handbook --command npx --arg -y --arg @ah-oh/handbook-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  jannks-handbook:
    command: "npx"
    args: ["-y", "@ah-oh/handbook-mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "jannks-handbook": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@ah-oh/handbook-mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add jannks-handbook -t stdio -c npx -a -y @ah-oh/handbook-mcp-server
// mcp.json
{
  "mcpServers": {
    "jannks-handbook": {
      "command": "npx",
      "args": [
        "-y",
        "@ah-oh/handbook-mcp-server"
      ]
    }
  }
}
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.

  • 20 Sept 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.

  • 18 Sept 26 +1

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

  • 17 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 16 Sept 26 −3
    • Security disclosure: fail → unverified functional
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 13 Sept 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 Sept 26 +1

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

  • 9 Sept 26 −3
    • Stability: pass → 0.80 functional
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/@ah-oh/handbook-mcp-server@1.0.1

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 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~733 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
handbook_create_entry ~200

Create a new handbook entry. Args: - title (string): Entry title - content (string, optional): Markdown content - active (boolean): Whether the entry is active - app (string): App identifier (e.g. 'szales', 'sethub') - tags (string[], optional): Tags - importId (string, optional): Import ID Returns: The created HandbookEntry.

NameTypeReqDescription
activebooleanyesWhether the entry is active
appstringyesThe app associated with this entry (e.g. 'szales', 'sethub')
contentstringContent of the entry in markdown format
importIdstringOptional import ID for entries imported from sethub language content
tagsarrayTags for the entry, e.g. ['meeting', 'project']
titlestringyesTitle of the handbook entry

No output schema declared.

No examples provided.

handbook_delete_entry ~55

Permanently delete a handbook entry by ID. Args: - id (string): ID of the entry to delete Returns: Confirmation of deletion.

NameTypeReqDescription
idstringyesThe ID of the handbook entry to delete

No output schema declared.

No examples provided.

handbook_get_entry ~66

Retrieve a single handbook entry by its ID, including full content in markdown. Args: - id (string): The MongoDB ObjectId of the entry Returns: Full HandbookEntry object with content.

NameTypeReqDescription
idstringyesThe ID of the handbook entry to retrieve

No output schema declared.

No examples provided.

handbook_get_overview ~97

Get a lightweight overview of all handbook entries for a specific app. Returns only title, ID, app and tags (no full content). Args: - app (string): App identifier (e.g. 'szales', 'sethub') Returns: HandbookOverviewResponse with an array of overview entries.

NameTypeReqDescription
appstringyesThe app to get overview entries for (e.g. 'szales', 'sethub')

No output schema declared.

No examples provided.

handbook_list_entries ~60

Retrieve all handbook entries. Returns a list with title, ID, app, active status and tags for every entry. Returns: Array of HandbookEntry objects. Use when: you need an overview of all existing entries or want to find an entry ID.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

handbook_search_tags ~72

Search for tags across all handbook entries. Args: - searchQuery (string): Search string to filter tags (e.g. 'meet') Returns: HandbookTagsResponse with an array of matching tag strings.

NameTypeReqDescription
searchQuerystringyesSearch query to filter handbook tags (e.g. 'meet')

No output schema declared.

No examples provided.

handbook_update_entry ~183

Update an existing handbook entry by ID. Args: - id (string): ID of the entry to update - title (string): Updated title - content (string, optional): Updated markdown content - active (boolean): Active status - app (string): App identifier - tags (string[], optional): Updated tags - importId (string, optional): Import ID Returns: The updated HandbookEntry.

NameTypeReqDescription
activebooleanyesWhether the entry is active
appstringyesThe app associated with this entry
contentstringUpdated content in markdown format
idstringyesThe ID of the handbook entry to update
importIdstringOptional import ID
tagsarrayUpdated tags
titlestringyesUpdated title

No output schema declared.

No examples provided.

Common questions

What is the io.github.jannks/handbook MCP server?

io.github.jannks/handbook is an MCP server listed in the public MCP registry as io.github.jannks/handbook. MCP server for the Handbook API – manage handbook entries via CRUD, overview and tag search. This page covers its npm package (@ah-oh/handbook-mcp-server).

Is the io.github.jannks/handbook MCP server safe to use?

io.github.jannks/handbook scores 85 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.jannks/handbook MCP server expose?

io.github.jannks/handbook exposes 7 tools: handbook_list_entries, handbook_get_entry, handbook_create_entry, handbook_update_entry, handbook_delete_entry, and 2 more. Their descriptions and schemas cost roughly 733 tokens of context every time the server is loaded.

Is the io.github.jannks/handbook MCP server still maintained?

io.github.jannks/handbook 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.jannks/handbook MCP server under?

io.github.jannks/handbook declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.