Is PDF MCP server safe?
Probably. Read the findings first.
Use with care. Some checks failed or could not be verified.
How PDF compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 63/100
- higher than 18% of 48,255 servers
- Tools that change things
- 67%
- typical: 0%. Fewer write tools means less an agent can break
What its tools let an agent do: 3 create
Public scan report
scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it
3 medium
- Code scan33 source files scanned10/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
- Maintenancelast push 11 days ago15/15
- Maintainer identitynamespace and repository owner differ4/10
Findings (3)
- mediumnpm install lifecycle script present
install.script - mediumeval / new Function used
exec.evalbin/server.js: …cjs if (typeof require === 'undefined') eval("import('../dist/esm/index.js').then((mo… - mediumnpm install lifecycle script present
install.scriptpackage.json: …t": "biome check --write --unsafe", "postinstall": "node scripts/postinstall.cjs", "te…
Overall 63/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON