Is Aegis 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 Aegis 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
- 0%
- typical: 0%. Fewer write tools means less an agent can break
What its tools let an agent do: 3 read
Public scan report
scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it
1 high
- Code scan120 source files scanned13/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 qualitystatic API keys via environment variables6/15
- Maintenancelast push 49 days ago12/15
- Maintainer identityregistry namespace matches repository owner7/10
Findings (1)
- highShell command built from a string (injection risk)
exec.shell-concatdist/cli/helpers.js: …ate RSA private key (2048 bits) execSync(`openssl genrsa -out "${keyPath}" 2048`, { stdio: 'pipe' }); …
Overall 58/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON