Is Memex 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 Memex compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 65/100
- higher than 20% of 48,255 servers
- Tools that change things
- 20%
- typical: 0%. Fewer write tools means less an agent can break
What its tools let an agent do: 12 read · 3 change
Release history: 3 versions in the registry since 2026-08-26, latest 2026-10-26, typically one every 43 days.
Public scan report
scanner v0.1.10 · 2026-10-31 · same rubric, same numbers if you re-run it
1 high
- Code scan2 source files scanned; 117 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 3 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (1)
- highShell command built from a string (injection risk)
exec.shell-concatbin/memex-mcp.js: … function isCommand(cmd) { try { execSync(`${cmd} --version`, { stdio: 'ignore' }); …
Overall 65/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON