Freshcontext MCP Server
freshcontext-mcp
npm
v0.4.0
Published by princegabriel-lgtm — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.
Started at 100 and nothing was deducted: the deterministic scan raised no scored threat in the published surface it inspected. Capability observations and advisory notes are recorded but never lower the score.
Findings 5
high Shell/command execution in server code (package-script-guard.mjs)MTC-SRC-002
In the server's implementation (`package-script-guard.mjs:3`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: child_process
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 package-script-guard.mjs
medium Hardcoded egress to an external endpoint (dist/adapters/changelog.js)MTC-SRC-003
In the server's implementation (`dist/adapters/changelog.js:40`): 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.github.com/repos/${owner}/${repo}/releases?per_page=10`
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/adapters/changelog.js
medium Hardcoded egress to an external endpoint (dist/adapters/jobs.js)MTC-SRC-003
In the server's implementation (`dist/adapters/jobs.js:266`): 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://hn.algolia.com/api/v1/search?query=Ask+HN+Who+is+hiring&tags=story&hitsPerPage=5`
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/adapters/jobs.js
medium Hardcoded egress to an external endpoint (dist/adapters/packageTrends.js)MTC-SRC-003
In the server's implementation (`dist/adapters/packageTrends.js:17`): 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://registry.npmjs.org/${encodeURIComponent(pkgName)}`
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/adapters/packageTrends.js
medium Hardcoded egress to an external endpoint (dist/adapters/productHunt.js)MTC-SRC-003
In the server's implementation (`dist/adapters/productHunt.js:32`): 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.producthunt.com/v2/api/graphql"
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/adapters/productHunt.js
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.4.0 latest |
A 100/100 | 5 | 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 freshcontext-mcp --onlineMore in Web, Search & Scraping
Security scan results for the 3gpp Mcp Charging MCP server.
Security scan results for the 4o Mini Search MCP server.
Security scan results for the A11y Color Contrast MCP server.
Security scan results for the A2asearch MCP server.
Security scan results for the Access Calibre MCP server.
Security scan results for the Activitypub MCP server.