Docmcp (pieeee) MCP Server
@pieeee/docmcp
npm
v0.2.2
Source verified
Published by pieeee — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
Every server starts at 100. These are the exact deductions the deterministic engine applied — each one reproducible, none of it an opinion or an LLM's guess:
| Points | What was found | Category |
|---|---|---|
| −6.3 | Package runs install-time scripts MTC-SUP-010 | supply-chain |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind the deduction.
Findings 2
medium Hardcoded egress to an external endpoint (dist/embedder/providers/anthropic.js)MTC-SRC-003
In the server's implementation (`dist/embedder/providers/anthropic.js:15`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: fetch('https://api.voyageai.com/v1/embeddings'
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/embedder/providers/anthropic.js
medium Package runs install-time scripts (postinstall)MTC-SUP-010
"@pieeee/docmcp" executes postinstall script(s) at install time. The large majority of malicious packages abuse install hooks to run code before you ever import them.
Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.
Location: package @pieeee/docmcp
What this scan could not see
- No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Versions
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.2.2 latest |
A 94/100 | 2 | 1.5.0 | 2026-07-22 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @pieeee/docmcp --onlineOther implementations of Docmcp 1
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
More in Learning & Documentation
Security scan results for the Ab Integrations MCP server.
Security scan results for the Academic Research MCP server.
Security scan results for the Academic Research Mcp Suite MCP server.
Security scan results for the Adonis Docs MCP server.
Security scan results for the Adonis Mcp Docs MCP server.
Security scan results for the Advisor MCP server.