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.Fisher521/bookmarks-mcp

NPM · BOOKMARKS-MCP · SCANNED SEP 30

Read-only MCP server for browser bookmarks: Chrome, Safari, Firefox, and read-later exports.

Available components

0 this week 82 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 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability84
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 733 tokens (~91/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 53% 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
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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.Fisher521/bookmarks-mcp server?

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

npm · bookmarks-mcp

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

  • 29 Sept 26 +1

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

  • 28 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
  • 27 Sept 26 0
    • Stability: 0.97 → pass security
  • 26 Sept 26 +1

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

  • 25 Sept 26 0
    • 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

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

  • 22 Sept 26 +1

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

  • 20 Sept 26 −3
    • Stability: pass → 0.77 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 30 Sept 2026 · Analysed npm/bookmarks-mcp@0.1.0

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

Background: SBOMs and build attestations, explained →

MCP tools · 8 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
bookmark_stats ~91

The state of the pile: total count, per-source counts, age distribution (how much has sat untouched for years), and top domains. A good first call before triaging.

NameTypeReqDescription
sourcestring–Filter by browser ("chrome", "safari", "firefox", "edge", "brave", "arc", "vivaldi") or a source id from list_sources. Omit for all.

No output schema declared.

No examples provided.

export_bookmarks ~97

Export bookmarks from detected browsers as markdown, csv, json, or importable browser HTML (Netscape format). Returns the file content; save it wherever you like.

NameTypeReqDescription
formatstringyes–
sourcestring–Filter by browser ("chrome", "safari", "firefox", "edge", "brave", "arc", "vivaldi") or a source id from list_sources. Omit for all.

No output schema declared.

No examples provided.

fetch_page_preview ~134

Fetch a bookmarked URL and return a short, structured preview (title, description, headings, an opening excerpt, word count) instead of the raw page — a few hundred tokens instead of tens of thousands. Use this only when a title/URL alone isn't enough to triage a bookmark: dead links come back as `dead` or `unreachable` so you can retire them without guessing, rather than raw HTML. Results are cached locally per URL; pass refresh:true to bypass the cache.

NameTypeReqDescription
refreshboolean–Bypass the local cache and re-fetch
urlstringyesThe URL to preview

No output schema declared.

No examples provided.

list_bookmarks ~101

List bookmarks from detected browsers. Supports folder filter and pagination.

NameTypeReqDescription
folderstring–Only bookmarks whose folder path contains this string (case-insensitive)
limitinteger––
offsetinteger––
sourcestring–Filter by browser ("chrome", "safari", "firefox", "edge", "brave", "arc", "vivaldi") or a source id from list_sources. Omit for all.

No output schema declared.

No examples provided.

list_sources ~56

Detect every bookmark source on this machine: Chromium-family profiles (Chrome, Edge, Brave, Arc, Vivaldi), Firefox profiles, and Safari (incl. Reading List). Returns ids usable as the `source` argument of other tools.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

parse_export_file ~72

Parse a bookmark export file from disk into clean JSON. Auto-detects: browser bookmark HTML (Netscape), Pocket CSV, Instapaper CSV, Raindrop CSV, or a plain URL list.

NameTypeReqDescription
formatstring––
pathstringyesAbsolute path to the export file

No output schema declared.

No examples provided.

recent_bookmarks ~93

Bookmarks added in the last N days, newest first. Useful for `what did I save this week?`.

NameTypeReqDescription
daysinteger––
limitinteger––
sourcestring–Filter by browser ("chrome", "safari", "firefox", "edge", "brave", "arc", "vivaldi") or a source id from list_sources. Omit for all.

No output schema declared.

No examples provided.

search_bookmarks ~89

Case-insensitive search across bookmark titles, URLs, folders, and tags in every detected browser.

NameTypeReqDescription
limitinteger––
querystringyes–
sourcestring–Filter by browser ("chrome", "safari", "firefox", "edge", "brave", "arc", "vivaldi") or a source id from list_sources. Omit for all.

No output schema declared.

No examples provided.

Common questions

What is the io.github.Fisher521/bookmarks-mcp server?

io.github.Fisher521/bookmarks-mcp is listed in the public MCP registry as io.github.Fisher521/bookmarks-mcp. Read-only MCP server for browser bookmarks: Chrome, Safari, Firefox, and read-later exports. This page covers its npm package (bookmarks-mcp).

Is the io.github.Fisher521/bookmarks-mcp server safe to use?

io.github.Fisher521/bookmarks-mcp scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 30 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.Fisher521/bookmarks-mcp server expose?

io.github.Fisher521/bookmarks-mcp exposes 8 tools: list_sources, list_bookmarks, search_bookmarks, recent_bookmarks, bookmark_stats, and 3 more. Their descriptions and schemas cost roughly 733 tokens of context every time the server is loaded.

Is the io.github.Fisher521/bookmarks-mcp server still maintained?

io.github.Fisher521/bookmarks-mcp is still listed as active in the MCP registry. We last reached this channel on 30 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.Fisher521/bookmarks-mcp server under?

io.github.Fisher521/bookmarks-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.