Mmcp.market

Is Auditable memory (memory3l) MCP server safe?

Probably. Read the findings first.

C65/100grade C

Use with care. Some checks failed or could not be verified.

Public scan report

scanner v0.1.9 · 2026-09-20 · same rubric, same numbers if you re-run it

1 low
  • Code scan8 source files scanned25/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
  • Maintenanceno repository listed3/15
  • Maintainer identityno repository or website to verify2/10

Findings (1)

  • lowNo source repository listedmaint.no-repo
Overall 65/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 Auditable memory (memory3l) does

  • Deja Vu
    deja-vu: local memory over the session histories of thirty-three coding agents.
    A
  • Knowl
    Persistent memory for Claude Code, Cursor and Codex. Facts retire when they change.
    A
  • Plur
    Open, local-first engram memory for AI agents: read, correct, delete; shared over MCP.
    A

Auditable memory (memory3l) reviews, tools and install