Is Augments MCP server safe?
Not recommended.
Hidden from default browsing. Significant findings or unreachable.
What to know before installing
- highRemote endpoint did not respond — TypeError: fetch failed
How Augments compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 52/100
- higher than 10% of 48,114 servers
- Uptime
- 0%
- of our recent checks; the typical remote server answers 100%
Public scan report
scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it
1 high1 medium
- Code scan33 source files scanned20/25
- Live reliabilityremote unreachable: TypeError: fetch failed0/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 233 days ago4/15
- Maintainer identityendpoint served from the registry-verified namespace domain8/10
Findings (2)
- highRemote endpoint did not respond
reliability.unreachableTypeError: fetch failed
- mediumeval / new Function used
exec.evalaugments_mcp_server-2.0.2/src/augments_mcp/middleware/abuse_detector.py: …p table", # SQL injection "eval(", "exec(", # Code execution …
Overall 52/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON