Is Veto 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 Veto compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 63/100
- higher than 18% of 48,255 servers
- Tools that change things
- 12%
- typical: 0%. Fewer write tools means less an agent can break
What its tools let an agent do: 84 read · 11 change
Release history: 5 versions in the registry since 2026-09-15, latest 2026-10-04, typically one every 7 days.
Public scan report
scanner v0.1.10 · 2026-10-15 · same rubric, same numbers if you re-run it
1 high1 medium
- Code scan380 source files scanned8/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)
- mediumeval / new Function used
exec.evaldist/agents/security/penetration.js: …turn no data or 400, not 500', 'eval() and shell execution with user input ar…
- highShell command built from a string (injection risk)
exec.shell-concatdist/server/handlers/generators.js: …leHint) { const blame = execSync(`git log --oneline -10 -- "${fileHint}"`, { windowsHide: true, cwd: p…
Overall 63/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON