Is MemoryGuard MCP server safe?
Yes, with the usual care.
Safe to use. Minor gaps such as a missing repository or slower maintenance.
No critical or high findings in the latest scan.
Public scan report
scanner v0.1.8 · 2026-09-19 · same rubric, same numbers if you re-run it
2 medium
- Code scan215 source files scanned15/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 qualitylocal package, no credentials required12/15
- Maintenancelast push 7 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
Findings (2)
- mediumeval / new Function used
exec.evalagent_memguard-0.7.12/src/memoryguard/desktop_executor.py: …_force() try: root.eval("tk::PlaceWindow . center") exce… - mediumsubprocess with shell=True
exec.shell-trueagent_memguard-0.7.12/src/memoryguard/rules/skill_rules.py: …"脚本含 rm -rf / curl | sh subprocess.call(shell=True)" negative_example = "脚本只做只读分析,无写操作…
Overall 74/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 MemoryGuard does
- Prism CoderSession memory for coding agents: local-first recall, drift detection, on-device inference.not reviewedEstablishedC
MemorixLocal-first project memory with legacy MCP and 2026 discovery compatibility.not reviewedEstablishedB- Deja Vudeja-vu: local memory over the session histories of thirty-three coding agents.not reviewedEstablishedA