Auditable memory (memory3l)

io.github.jayzhtPublished by GitHub account jayzhtv0.2.0Updated Oct 27, 2026

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

The publisher's own server: Memory.fit

VerifiedSTDIODesktop onlyDatabasesKnowledge & Memory

Overview

AI-generated overview

Local MCP server that gives an assistant an auditable, append-only fact ledger stored in SQLite, with verifiable invariants I1-I5.

What you can do
  • Serve an append-only fact ledger from a local SQLite file so the assistant can recall stored facts.
  • Optionally expose an append_facts tool to add new facts to the ledger, only when explicitly enabled.
  • Support verification of the ledger's invariants I1-I5 for auditability.
  • Point at a specific ledger file or a development checkout of the audit core via environment variables.
When to use it
Use it when you want an assistant to keep durable memory whose history is append-only and auditable, rather than a free-form notes store. Suitable for local, desktop-based workflows where the ledger file stays on your machine.
Requirements
Runs as a local stdio process, launched with uvx from the PyPI package memory3l-mcp, so Python tooling is needed. Set MEMORY3L_DB to the SQLite fact-ledger file to serve; MEMORY3L_ALLOW_WRITE=1 is required to expose the append_facts tool; MEMORY3L_ROOT optionally overrides the audit core location. No authentication is declared.
Before you install
Writes are opt-in: append_facts appears only when MEMORY3L_ALLOW_WRITE is set to 1, so enabling it lets the assistant add facts to the ledger. The ledger is a local SQLite file whose path you supply via MEMORY3L_DB; point it at a file you are willing to have read and, if writes are enabled, appended to. No tool list is published, so review the exposed tools after connecting.

Installation

In SourceWeft

  1. Open Auditable memory (memory3l) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.0LatestSep 20, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Memory integrations