Is Cogmemai MCP server safe?
Not recommended.
Hidden from default browsing. Significant findings or unreachable.
What to know before installing
- highShell command built from a string (injection risk)
- highShell command built from a string (injection risk)
How Cogmemai compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 43/100
- higher than 8% of 48,255 servers
Release history: 4 versions in the registry since 2026-08-31, latest 2026-10-01, typically one every 4 days.
Public scan report
scanner v0.1.10 · 2026-10-29 · same rubric, same numbers if you re-run it
2 high
- Code scan45 source files scanned; 45 source files scanned1/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 owner6/10
Findings (2)
- highShell command built from a string (injection risk)
exec.shell-concatbuild/cli.js: …= envParts.join(' '); try { execSync(`claude mcp add cogmemai cogmemai-mcp ${envStr} --scope user`, { stdio: 'pipe', … - highShell command built from a string (injection risk)
exec.shell-concatbuild/cli.js: …= envParts.join(' '); try { execSync(`claude mcp add cogmemai cogmemai-mcp ${envStr} --scope user`, { stdio: 'pipe', …
Overall 43/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Safer options for the same job
Front-End ChecklistReview frontend code and live pages against 386 quality-gated web development rules.not reviewedWidely usedA- Deja Vudeja-vu: local memory over the session histories of forty-three coding agents.not reviewedEstablishedA