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.

duke-book

NPM · DUKE-BOOK · SCANNED SEP 25

Manage Duke Bookmark notes, categories, and plan-enabled knowledge search over MCP.

Available components

0 this week 74 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 & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 58 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 406 tokens (~40/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 26% 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
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 10 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 duke-book MCP server?

duke-book runs locally as an npm package, launched with npx -y duke-book. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · duke-book

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

  • 25 Sept 26 −3
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 +1
    • Stability: 0.97 → pass security
  • 22 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.

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

  • 18 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 17 Sept 26 +1
    • Stability: 0.97 → pass security
  • 15 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.

  • 13 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.

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 25 Sept 2026 · Analysed npm/duke-book@0.1.5

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 · 10 exposed · ~406 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
duke_create_category ~32

Create a category for the configured token user.

NameTypeReqDescription
descriptionstring––
namestringyes–

No output schema declared.

No examples provided.

duke_create_note ~71

Create a new text or rich-text note.

NameTypeReqDescription
categoryIdstringyes–
contentstringyes–
idempotencyKeystring–Reuse this key only when retrying the exact same create request.
noteTypestring––
titlestringyes–

No output schema declared.

No examples provided.

duke_delete_note ~26

Delete a note owned by the configured token user.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

duke_get_note ~27

Read a single note with full decrypted content.

NameTypeReqDescription
idstringyesNote id.

No output schema declared.

No examples provided.

duke_health_check ~25

Check service health after validating API_ACCESS, MCP_ACCESS, and profile:read.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

duke_list_categories ~20

List note categories available to the configured Duke Bookmark token.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

duke_search_knowledge ~40

Search the Duke Bookmark knowledge base. Requires API_ACCESS, MCP_ACCESS, AI_RAG, and knowledge:read.

NameTypeReqDescription
querystringyes–

No output schema declared.

No examples provided.

duke_search_notes ~65

Search notes by keyword, or list recent notes when query is omitted.

NameTypeReqDescription
categoryIdstring–Optional category id filter.
pageinteger––
pageSizeinteger––
querystring–Keyword to search in note titles and summaries.

No output schema declared.

No examples provided.

duke_update_note ~74

Update the title, content, or category of an existing note.

NameTypeReqDescription
categoryIdstring––
contentstring––
idstringyes–
idempotencyKeystring–Reuse this key only when retrying the exact same update request.
titlestring––

No output schema declared.

No examples provided.

duke_validate_token ~26

Validate commercial MCP access and safely report the current plan, enabled features, and scopes.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the duke-book MCP server?

duke-book is an MCP server listed in the public MCP registry as io.github.gitHubDujianfeng/duke-book. Manage Duke Bookmark notes, categories, and plan-enabled knowledge search over MCP. This page covers its npm package (duke-book).

Is the duke-book MCP server safe to use?

duke-book scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 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 duke-book MCP server expose?

duke-book exposes 10 tools: duke_list_categories, duke_search_notes, duke_get_note, duke_create_note, duke_update_note, and 5 more. Their descriptions and schemas cost roughly 406 tokens of context every time the server is loaded.

Is the duke-book MCP server still maintained?

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

duke-book declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.