Redis MCP — security audit
Redis MCP: trust score 63/100 — 2 capability surfaces.
Trust score
63
Grade C
Risk flags
No public repository linked
Without a public repo we cannot independently audit the code. Caution warranted.
Capability surface
Process spawn
Medium riskLaunches subprocesses via docker, npx, uvx — supply-chain risk if package is compromised.
Evidence:
npxDatabase mutation
High riskConnects to a database. Read-only flag, when present, mitigates the risk.
Evidence:
redis
Trust signals
Total trust score is the sum of these contributions. Each signal carries a fixed weight.
Verified by Loadout
+20 / 20
Manually verified.
Official author
+15 / 15
Maintained by the official Redis team.
Community traction
+18 / 20
3,600 GitHub stars.
Public source
+0 / 15
No linked public repository.
Stability
+0 / 15
Stability not yet assessed.
Capability surface
+10 / 15
1 high-risk capability detected.
Disclaimer
This is an automated heuristic triage. It does not replace a hand-rolled code audit. Use it to prioritise which servers deserve a deeper look — especially anything carrying high-risk capabilities like shell execution or filesystem write.