Bridge (helmdeck) MCP Server
@helmdeck/mcp-bridge
npm
v0.29.10
Source verified
Published by tosin2013 — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 6.3 = 94. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −6.3 | Package runs install-time scripts MTC-SUP-010 | supply-chain |
2. Client adoption risk — 94 − your exposure = 86. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −2 | publisher verification (source) — trust in the source of the package |
| 0 | inspection depth (source) — how much of the target the scan could see |
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 a deduction.
Findings 3
high Shell/command execution in server code (bin/helmdeck-mcp.js)MTC-SRC-002
In the server's implementation (`bin/helmdeck-mcp.js:14`): 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 bin/helmdeck-mcp.js
high Shell/command execution in server code (scripts/postinstall.js)MTC-SRC-002
In the server's implementation (`scripts/postinstall.js:17`): 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 scripts/postinstall.js
medium Package runs install-time scripts (postinstall)MTC-SUP-010
"@helmdeck/mcp-bridge" 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 @helmdeck/mcp-bridge
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.29.10 latest |
A 94/100 | 3 | 1.5.0 | 2026-07-23 |
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 @helmdeck/mcp-bridge --onlineOther implementations of Bridge 9
Independent packages implementing the same tool, scanned with the same engine. Compare all 10 side by side →
Security scan results for the Bridge (utcp) MCP server.
Security scan results for the Bridge (inferencesh) MCP server.
Security scan results for the Bridge (npm) MCP server.
Security scan results for the Bridge (PyPI) MCP server.
Security scan results for the Bridge (cofa-probe) MCP server.
Security scan results for the Bridge (mgsoftwarebv) MCP server.
More in Cloud & DevOps
Security scan results for the Adguard MCP server.
Security scan results for the Aliyun MCP server.
Security scan results for the Anypoint Connect MCP server.
Security scan results for the Aspro MCP server.
Security scan results for the Atlassian MCP server.
Security scan results for the Auroradocs MCP server.