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.

com.docfork/docfork-mcp

NPM · DOCFORK · 2 COMPONENTS · SCANNED SEP 20

Up-to-date docs for AI. DEPRECATED: Use io.github.docfork/docfork instead.

Available components

remote · mcp.docfork.com 0 npm · docfork 78
+1 this week 78 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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.25.2, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 68 of 246 dependencies flagged as unhealthy (5 deprecated). View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • 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 117 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 261 tokens (~130/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 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
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 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 com.docfork/docfork-mcp server?

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

npm · docfork

# add to Claude Code
claude mcp add com-docfork-docfork-mcp -- npx -y docfork
// .cursor/mcp.json
{
  "mcpServers": {
    "com-docfork-docfork-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "docfork"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-docfork-docfork-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "docfork"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com-docfork-docfork-mcp -- npx -y docfork
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-docfork-docfork-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "docfork"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-docfork-docfork-mcp --command npx --arg -y --arg docfork
# ~/.hermes/config.yaml
mcp_servers:
  com-docfork-docfork-mcp:
    command: "npx"
    args: ["-y", "docfork"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-docfork-docfork-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "docfork"
      ]
    }
  }
}
# add to Vellum
assistant mcp add com-docfork-docfork-mcp -t stdio -c npx -a -y docfork
// mcp.json
{
  "mcpServers": {
    "com-docfork-docfork-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "docfork"
      ]
    }
  }
}
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 −2
    • Stability: pass → 0.83 functional
  • 19 Sept 26 0
    • Stability: 0.97 → pass security
  • 18 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.

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

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

  • 12 Sept 26 −3
    • Stability: pass → 0.77 functional
  • 11 Sept 26 0
    • Stability: 0.97 → pass security
  • 10 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.

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/docfork@1.3.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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-345p-7cg4-v4c7 CVE-2026-25536 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 246 packages
Packages resolved 246
Deprecated 5
Stale 62
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~261 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
docfork_read_url ~77

Fetches and returns the full content of a documentation page as markdown. This is ESSENTIAL for getting complete, detailed information after searching. Always use this to read URLs from docfork_search_docs results to get the actual documentation content.

NameTypeReqDescription
urlstringyesFull URL to read. Use exact URLs from docfork_search_docs results.

No output schema declared.

No examples provided.

docfork_search_docs ~184

Search documentation across GitHub repositories or the web. For targeted searches INSIDE a specific library's documentation, use the docforkIdentifier parameter (author/repo format). Extract from GitHub URLs (e.g., github.com/facebook/react → 'facebook/react') and include in ALL subsequent searches about that library for focused, accurate results.

NameTypeReqDescription
docforkIdentifierstring–CRITICAL for targeted library searches: Library identifier in author/repo format (e.g., 'facebook/react', 'vercel/next.js'). Use this to search INSIDE a specific library's documentation for focused,…
querystringyesSearch query. Include language/framework names.
tokensstring–Token budget: 'dynamic' or number (100-10000)

No output schema declared.

No examples provided.

Common questions

What is the com.docfork/docfork-mcp server?

com.docfork/docfork-mcp is listed in the public MCP registry as com.docfork/docfork-mcp. Up-to-date docs for AI. DEPRECATED: Use io.github.docfork/docfork instead. This page covers its npm package (docfork).

Is the com.docfork/docfork-mcp server safe to use?

com.docfork/docfork-mcp scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against 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 com.docfork/docfork-mcp server expose?

com.docfork/docfork-mcp exposes 2 tools: docfork_search_docs, docfork_read_url. Their descriptions and schemas cost roughly 261 tokens of context every time the server is loaded.

Is the com.docfork/docfork-mcp server still maintained?

com.docfork/docfork-mcp 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 com.docfork/docfork-mcp server under?

com.docfork/docfork-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.