Is Doc Extract API MCP server safe?
Yes, with the usual care.
Safe to use. Minor gaps such as a missing repository or slower maintenance.
No critical or high findings in the latest scan.
Public scan report
scanner v0.1.9 · 2026-09-20 · same rubric, same numbers if you re-run it
1 medium
- Code scan2 source files scanned20/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 qualitystatic API keys via environment variables6/15
- Maintenancelast push 12 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
Findings (1)
- mediumeval / new Function used
exec.evaldist/mcp-server.js: …ode, sch); const makeValidate = new Function(`${names_1.default.self}`, `${names_1.de…
Overall 72/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 Doc Extract API does
- TalonicExtract structured, schema-validated data from PDFs, scans, images, spreadsheets, and forms.not reviewedGrowingA
- MCPWeb intelligence for AI agents: fetch, render, extract, research. x402 micropayments, no API keys.not reviewedGrowingC
- zipnative MCP — ZIP creation, inspection, secure extraction & verificationZIP MCP server: create, inspect, verify, extract securely, modify without recompression. 13 toolsnot reviewedGrowingB
