Is memgit 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.
How memgit compares
Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 83/100
- higher than 65% of 1,119 Developer tools servers
Release history: 3 versions in the registry since 2026-09-11, latest 2026-10-08, typically one every 18 days.
Public scan report
scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it
1 medium
- Code scan2 source files scanned; 36 source files scanned20/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 identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace7/10
Findings (1)
- mediumeval / new Function used
exec.evalmemgit-0.13.0/memgit/cli.py: …t_command=True) @click.pass_context def eval(ctx): """Retrieval evaluation — prov…
Overall 83/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 memgit does
- PalinodeInspectable, correctable project memory in git-versioned Markdown for AI agents.not reviewedEstablishedC
- NexusmemLocal-first memory for AI coding agents: shell history with exit codes, git diffs, docs, MCP.not reviewedGrowingA
- SuvaduLocal shell history and AI agent sessions over MCP: search commands, failures, risk and git changesnot reviewedGrowingA