Auditable memory (memory3l) MCP Server

by jayzht Your server? Claim it

local only

Auditable memory (memory3l) runs on your own machine — the client starts it, so there is no endpoint to ping.

Audited memory over MCP: an append-only fact ledger plus verifiable invariants I1-I5.

—

Installs / week

pypi · memory3l-mcp

—

Stars

on GitHub

—

Last commit

no recent releases

—

License

language unknown

Nothing serious here today

Today is the operative word: we check Auditable memory (memory3l) every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add memory3l-mcp -- uvx memory3l-mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "memory3l-mcp": {
      "args": [
        "memory3l-mcp"
      ],
      "command": "uvx"
    }
  }
}

~/.codex/config.toml

[mcp_servers.memory3l-mcp]
command = "uvx"
args = ["memory3l-mcp"]

.cursor/mcp.json

{
  "mcpServers": {
    "memory3l-mcp": {
      "args": [
        "memory3l-mcp"
      ],
      "command": "uvx"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "memory3l-mcp": {
      "args": [
        "memory3l-mcp"
      ],
      "command": "uvx"
    }
  }
}

This one needs environment variables set before it will start: MEMORY3L_ROOT (Override the location of the memory3l audit core (development against a source checkout).), MEMORY3L_DB (Path to the SQLite fact-ledger file to serve.), MEMORY3L_ALLOW_WRITE (Set to 1 to also expose the append_facts tool.). The author declared them in the registry entry; get the values from the project itself.

Alternatives to Auditable memory (memory3l)

same job, measured the same way

three.ws Provenance

by nirholas

Append-only, signed, on-chain-verifiable agent action log — record and audit what agents did.

29 installs/wk local only

Acta — Verifiable Agent Memory

by kylewilson04

Verifiable agent memory with signed ledger receipts — verify every write offline.

local only

Zaxy

by syndicalt

Event-sourced, auditable agent memory over MCP: cited checkout, replayable provenance.

379 installs/wk local only

Rails MCP

by jaimenbell

Default-deny action registry, append-only spend ledger, and human sign-off audit trail (MCP tools).

47 installs/wk local only

Mnema

by zimac

Local-first, formally verified memory for AI agents: consult/learn/related/list over MCP.

local only

Model Ledger

by block

Model inventory and governance: trace deployed models and their dependencies as an append-only log

224 installs/wk local only

Ariadne

by mclaut

Local-first multilingual, auditable memory for Codex, Claude Code, and MCP clients.

local only

Cogmem

by writerslogic

A self-improving, verifiable memory layer for AI coding agents.

47 installs/wk local only

Auditable memory (memory3l) — questions

Answers built from our own checks of this server.

Why is there no uptime for Auditable memory (memory3l)?

Auditable memory (memory3l) runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the pypi package memory3l-mcp.

How do I connect Auditable memory (memory3l)?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It runs locally, so the command pulls memory3l-mcp straight from pypi; nothing to host, nothing to sign up for.