Is ThumbGate MCP server safe?
Probably. Read the findings first.
Use with care. Some checks failed or could not be verified.
What to know before installing
- highShell command built from a string (injection risk)
How ThumbGate compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 58/100
- higher than 13% of 48,255 servers
- Tools that change things
- 40%
- typical: 0%. Fewer write tools means less an agent can break
What its tools let an agent do: 3 read · 1 change · 1 run or deploy
Public scan report
scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it
1 high2 medium
- Code scan56 source files scanned3/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 3 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (3)
- mediumnpm install lifecycle script present
install.script - highShell command built from a string (injection risk)
exec.shell-concatbin/cli.js: … } function whichExists(cmd) { try { execSync(`which ${cmd}`, { stdio: 'pipe' }); return true; … - mediumnpm install lifecycle script present
install.scriptpackage.json: …md", "src/" ], "scripts": { "postinstall": "node bin/postinstall.js || true", …
Overall 58/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON