Is Docfork MCP server safe?
Yes, with the usual care.
Safe to use. Minor gaps such as a missing repository or slower maintenance.
What to know before installing
- highRepository is archived
How Docfork compares
Against every graded Productivity MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 71/100
- higher than 32% of 1,299 Productivity servers
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
What its tools let an agent do: 4 read
Public scan report
scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it
1 high
- Code scan10 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancerepository archived0/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Findings (1)
- highRepository is archived
maint.archived
Overall 71/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Other servers that do what Docfork does
Context7Up-to-date docs for AI agentsnot reviewedWidely usedA
Svelte MCPThe official Svelte MCP server providing docs and autofixing tools for Svelte developmentnot reviewedEstablishedA
SvGridChecks AI-written SvGrid code against the real API, plus version-pinned Svelte 5 grid docs.not reviewedEstablishedA