Is Hicortex — AI Fleet Memory 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)
Public scan report
scanner v0.1.9 · 2026-09-19 · same rubric, same numbers if you re-run it
1 high1 medium
- Code scan183 source files scanned8/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 2 days ago15/15
- Maintainer identityregistry namespace matches repository owner7/10
Findings (2)
- mediumeval / new Function used
exec.evaldist/eval/importance-eval.js: …; /** * Importance-scorer distribution eval (#425) — the AC4 measurement. * * npm…
- highShell command built from a string (injection risk)
exec.shell-concatdist/llm.js: …h try { const raw = execSync(`${claudePath} -p ${JSON.stringify(prompt)} --model ${model} --max-turns 1 --output-format jso…
Overall 55/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Other servers that do what Hicortex — AI Fleet Memory does
- Total Agent MemoryPersistent local memory for coding agents: temporal knowledge graph, procedural and episodic recallnot reviewedEstablishedA
- Fidelis MemoryRecall locally stored agent memories through an MCP-compatible host.not reviewedGrowingB
- Agent Memory OsLocal-first memory engine for AI-agent teams: team/project ACL, recall, and federated sync.not reviewedGrowingA