Is SassyMCP safe?
Probably. Read the findings first.
Use with care. Some checks failed or could not be verified.
What to know before installing
- highWhole environment serialized (possible credential exfil)
Public scan report
scanner v0.1.3 · 2026-09-19 · same rubric, same numbers if you re-run it
1 high2 medium
- Code scan77 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 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (3)
- mediumeval / new Function used
exec.evalsassymcp-1.15.1/sassymcp/modules/persona.py: …for linting, pytest for testing - Never eval() on external input **JavaScript/TypeSc…
- mediumsubprocess with shell=True
exec.shell-truesassymcp-1.15.1/sassymcp/modules/session.py: … subprocess spawner. Argv-list form (no shell=True) # is the safe-by-default option — no s…
- highWhole environment serialized (possible credential exfil)
env.dumpsassymcp-1.15.1/sassymcp/overlay/mesh.py: …NODE_PATH or SASSYMCP_REPO."} env = dict(os.environ) env.setdefault("HERMES_AUTORUN", "0…
Overall 58/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON