Is CLI Bridge 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.
How CLI Bridge compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 74/100
- higher than 40% of 48,243 servers
Public scan report
scanner v0.1.10 · 2026-10-15 · same rubric, same numbers if you re-run it
2 medium
- Code scan31 source files scanned15/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 2 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
Findings (2)
- mediumsubprocess with shell=True
exec.shell-truecli_bridge_mcp-0.3.0/src/cli_bridge/workflows.py: …*=\s*True"), "medium", "subprocess with shell=True", "shell=True invites command inje…
- mediumeval / new Function used
exec.evalcli_bridge_mcp-0.3.0/src/cli_bridge/workflows.py: …ompile(r"\beval\s*\("), "high", "Use of eval()", "eval on untrusted input is arb…
Overall 74/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON