Is sift 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 sift compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 72/100
- higher than 37% of 48,243 servers
- Tools that change things
- 17%
- typical: 0%. Fewer write tools means less an agent can break
What its tools let an agent do: 5 read · 1 run or deploy
Public scan report
scanner v0.1.10 · 2026-10-02 · same rubric, same numbers if you re-run it
1 medium
- Code scan26 source files scanned20/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 21 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
Findings (1)
- mediumsubprocess with shell=True
exec.shell-truesift_cli-1.1.0/src/sift/capture.py: … writes, and report how it ended. `shell=True` exists because pipes and globs are hal…
Overall 72/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON