memalyze
Use memalyze as a small self-hosted MCP memory service with redaction-before-write, audited reads, and hybrid retrieval.
Store memories with optional kind, scope, and TTL; get duplicate, redaction, and embedding status.
Search memories via vector search with keyword/recent fallback, scope filtering, and expiry control.
Soft-delete memories by id; already-deleted ids are idempotent and unknown ids error.
Echo text to verify MCP wiring.
Rely on local embeddings, configurable redaction rules, tamper-evident audit logs, backup checkpoints, and governance reports per the README.
Uses a local Ollama instance as the embedding provider (e.g. qwen3-embedding:0.6b) for vector search, so memories are embedded and queried fully offline without a cloud API or runtime model download.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@memalyze Remember that the client prefers email over phone calls"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
memalyze
MCP-native, self-hosted memory for AI agents — with the governance an enterprise will actually ask for.
One static binary. Local embeddings. No cloud, no graph database, no Python stack. Redaction happens before anything is written; every read is audited.
Website · MCP Registry · v0.2.0
./memalyze # MCP over stdio, for Claude Code / Cline / any harnessv0.2.0 is out — static binaries for linux/darwin/windows, checksums, hash-chained audit verification, backup checkpoints, and local HTML/JSON governance reports.

Video
60-second product overview — what memalyze does and how the redaction + audit loop works:

📺 Watch the 60s demo video — click to stream or download the MP4.
Related MCP server: Centralaizer
The problem
Every agent framework ships its own memory: a vector table here, a JSON file there, a "notes" folder somewhere else. Three things follow, and all three hurt in production:
You cannot audit it. "Which customer's data did the agent read last Tuesday?" has no answer, so security review stops the project.
You cannot deploy it offline. Most options either call a cloud API or download model weights from HuggingFace at runtime — both fail inside a bank, a hospital, or a factory.
You cannot keep it small. Twenty-three tools, a graph database, and a Python dependency tree later, the "memory feature" is a second product to operate.
memalyze is the middleware that fixes those three, and nothing else.
What is different
Cloud memory APIs | Framework built-ins | Personal note apps | memalyze | |
Where data lives | vendor cloud | inside the framework | local Markdown | your server / your laptop |
How to connect | proprietary API | tied to one framework | MCP | MCP, any harness, stdio or HTTP |
Redaction before write | ❌ | ❌ | ❌ | ✅ 8 rule families, configurable, irreversible by default |
Read audit | partial | ❌ | ❌ | ✅ append-only*, per-actor, exportable |
Offline | ❌ | partial | ⚠️ model download needed | ✅ local embeddings, no network |
Deployment | SaaS | with the framework | 173 Python packages | ✅ one static binary / one compose file |
Tool surface | — | — | 23 tools | 4 tools |
* Triggers reject both UPDATE and DELETE; a SHA-256 hash chain makes later edits visible.
This is not WORM: use audit verify with a checkpoint stored independently from the database
to detect tail truncation. Anyone who can rewrite both can still fabricate a chain
(SECURITY.md).
Not another mem0, and not Basic Memory either: those are good at remembering. memalyze assumes remembering is becoming a commodity and competes on governance, offline operation, and a deliberately small surface.
30-second demo
No Ollama, no network, no MCP client:
./examples/demo/demo.sh
# or: go run ./cmd/memalyze demoIt writes a memory containing a phone number, an e-mail and a resident ID, then shows:
what is actually stored (
[REDACTED:phone], not13800138000);that searching for the original number returns 0 hits;
that a business-word search still hits, returning the redacted text;
the audit rows for the two writes and the two reads.
Details and transcripts: docs/s15-redaction-audit.md.
Quick start
1. Binary + local embedding model
Prebuilt, checksum-verified (Linux/macOS; Windows: take the .exe from the release page):
curl -fsSL https://raw.githubusercontent.com/mahaoboy/memalyze/main/scripts/install.sh | sh
ollama pull qwen3-embedding:0.6b # ~640 MB, 1024-dim, strong on Chinese
memalyze --versionFrom source (Go 1.27+): make build, then ./memalyze --version.
2. Wire it into a harness
Claude Code (project scope):
claude mcp add --scope project memalyze -- "$(pwd)/memalyze"
cp examples/claude-code/CLAUDE.md ./CLAUDE.md # makes Claude search before answeringCline: copy examples/cline/cline_mcp_settings.json and .clinerules.
Generic harness: examples/custom-harness/ — one prompt contract
plus pseudocode. All options: examples/README.md.
3. Or one-click in Claude Desktop (MCPB)
Download the bundle for your platform from the
v0.2.0 release and open it.
Claude Desktop shows an install sheet and asks where to keep memalyze.db.
Platform | File |
macOS Apple Silicon |
|
macOS Intel |
|
Windows x64 |
|
Linux x64 |
|
The binary inside is the same v0.2.0 build as above. These bundles are new and have not
been opened on a real macOS/Windows desktop yet — if the install sheet does not appear,
use the plain binary. The server is also listed in the
MCP Registry.
4. Or run it in Docker (memalyze + Ollama + model pull)
printf 'MEMALYZE_HTTP_TOKEN=%s\n' "$(openssl rand -hex 24)" > .env
docker compose up -d --build
curl -s http://127.0.0.1:8080/healthz # {"status":"ok","version":"dev"}Point a Streamable-HTTP MCP client at http://127.0.0.1:8080/mcp with
Authorization: Bearer $MEMALYZE_HTTP_TOKEN. See docs/s16-docker.md.
Tools
Four, on purpose. Every extra tool is a decision the model has to make.
Tool | What it does | Notable semantics |
| store a memory | duplicates return the existing id; embedding failure keeps the memory ( |
| retrieve | vector first, keyword backfill, |
| soft delete | idempotent for already-deleted ids; unknown id returns a tool error |
| wiring check | proves the MCP link works; no business logic |
There is no memory_context tool: memory_search already returns text you can paste
into a prompt, and two overlapping tools make model choice worse (D-017).
Governance
Redaction (write path). Rules run in memory.Service.Add before dedup, FTS and
embedding — so plaintext never reaches the main table, the full-text index or a vector.
Rule | Example input | Stored as |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Modes: enforce (default), dry-run (count only, for tuning), off (debugging).
Custom rule packs are JSON: examples/redaction-rules.json.
Audit (read path). Schema-v3 audit_log records actor, tenant, scope, action, memory id,
timestamp, result count, degraded, and redaction count. UPDATE and DELETE triggers plus a
SHA-256 hash chain provide tamper evidence. Search text is stored as SHA-256 + length unless
you explicitly set MEMALYZE_AUDIT_QUERY_PLAIN=1.
memalyze audit export --from 2026-10-01 --to 2026-10-31 --format csv --out audit.csv
memalyze audit verify --write-checkpoint ./memalyze.audit.json
memalyze audit verify --checkpoint ./memalyze.audit.json
memalyze audit report --tenant acme --format html --out governance.htmlverify without a checkpoint checks internal consistency only. Exact checkpoint comparison also
detects a deleted (or newly advanced) tail; keep the unsigned checkpoint in an independent trust
domain. backup writes a matching <snapshot>.audit.json sidecar. Static reports contain only
aggregates and verification state—not memory IDs/content, query text/hash/length, or audit detail.
Set MEMALYZE_AUDIT_STRICT=on to return an error when audit append fails. Search then returns no
hits on audit failure; add/delete/reembed side effects are not rolled back. See
docs/audit-verification.md.
What is not here yet: per-user authentication (one token per process, actor from
env), audit retention/purge, reversible redaction, or an interactive audit UI.
Retrieval, measured
Numbers from S8 on a 60-memory Chinese corpus, 16 queries, measured not assumed
(docs/s8-retrieval-report.md):
Approach | recall@3 | MRR |
| 0.94 | 0.92 |
CJK bigram FTS5 (keyword backfill) | 0.88 | — |
| 0.47 | — |
Two counter-intuitive findings that shaped the design: SQLite FTS5's default tokenizer cannot search Chinese at all (0.19 recall until we stored bigram text), and RRF fusion scored worse than vector-only, so v0.1 does not fuse. See D-012.
Latency (S14, cold start fixed): warmup 37.8 s in background, then search 1.14 s with
degraded=false; after five idle minutes a fresh process answers in 1.52 s. If the vector
path is unavailable, search degrades to keyword in ≤3 s instead of hanging (D-015/D-018).
How it works
harness (Claude Code / Cline / your agent)
│ MCP: stdio or Streamable HTTP
▼
internal/mcp 4 tools, argument conversion only
▼
internal/memory redact → dedup → store → embed; search: vector → keyword → degraded
├── internal/govern rule engine (8 families, JSON configurable)
├── internal/store interface; sqlite impl (memories, embeddings, audit_log)
├── internal/embed float32 BLOB codec, cosine; Ollama client
└── internal/search CJK bigram tokenizer + FTS5 MATCH builderSQLite (WAL) with ULID ids, partial unique index for dedup, soft delete, TTL.
Vectors are
float32little-endian BLOBs; search is brute-force cosine (fine under ~10k memories, and the honest limit of a single-binary design).Schema migrations are versioned via
PRAGMA user_version(v2 → v3 backfills the audit hash chain and installs both append-only triggers).
Operations
memalyze audit export --from 2026-10-01 --format csv --out audit.csv # who read what
memalyze backup --out /var/backups/memalyze-$(date +%F).db # snapshot + .audit.json checkpoint
memalyze audit verify --checkpoint /var/backups/memalyze-$(date +%F).db.audit.json --db /var/backups/memalyze-$(date +%F).db
memalyze health --url http://127.0.0.1:8080/healthz # probesystemd:
deploy/systemd/memalyze.service+docs/s16-systemd.md(hardened unit, env file, backup timer).Docker:
docs/s16-docker.md.backupusesVACUUM INTO, so snapshots are consistent under WAL and include the audit table; it refuses to overwrite an existing file. It verifies the completed snapshot and writes a separate mode-0600.audit.jsoncheckpoint for restore-time verification.
Configuration
All through environment variables; defaults work out of the box.
Variable | Default | Meaning |
|
| SQLite path |
|
| default tenant for tool calls |
|
| local embedding endpoint |
|
| embedding model |
|
| vector-path budget before degrading |
|
| Ollama model residency |
|
|
|
| (built-in) | path to a JSON rule pack |
|
| append audit rows |
|
| actor recorded in audit |
|
| store query text (default: hash only) |
|
| fail the response when audit append fails; not a mutation rollback |
| (empty = stdio) | e.g. |
| (empty) | Bearer token; required when binding off-loopback |
Status
Honest snapshot — this is an early-stage project, not a 1.0.
Milestone | State |
M0 立项与定位 (S1–S4) | ✅ |
M1 备料与技术验证 (S5–S8) | ✅ |
M2 核心链路 (S9–S14) | ✅ |
M3 打磨与文档 (S15–S19) | ✅ S15 governance, S16 Docker, S17 docs, S18 tests+CI, S19 examples |
M4 发布 (S20–S23) | 🟡 S20 ✅, S21 ✅ (v0.2.0 public), S22 GitHub ✅ / HN·Reddit·V2EX pending, S23 ⬜ |
M5 复盘 (S24) | ⬜ needs real users |
M5 复盘 (S24) | ⬜ |
Known gaps: no per-user auth, no audit retention, the Docker image has not been built in CI (no daemon in the dev environment), brute-force vector scan, Chinese-first defaults (English works, but the tokenizer is tuned for CJK).
Docs
Doc | What it covers |
hash format, checkpoints, strict mode, backup/restore, report privacy | |
v0.2.0 features, upgrade, limits, verification | |
rules, modes, audit schema, demo transcript | |
compose stack, token policy, verification status | |
hardened systemd unit, env file, backup/restore | |
the 11 retrieval approaches and why this one won | |
the prompt contract that makes models search | |
real harness, two sessions, cold-start numbers | |
release artifacts, channels, post-release checklist | |
copy-paste entries for MCP directories and ClawHub | |
live feedback log (currently empty, honestly) | |
the milestone review template (not yet filled) | |
threat model: what is defended, what is out of scope |
Pilot
Two-week pilot: we install memalyze in your environment, tune the redaction rules to your data, review the audit export with you, and write down the threat-model gaps we find. No fee; you keep the deployment and the notes.
Request a pilot · Integration notes
Non-goals
Not a SaaS: you self-host, we do not hold your data.
Not an agent framework: it never takes over the harness.
Not a knowledge graph: no entity extraction pipeline, no graph database.
Not feature-maximal: four tools, one binary, and a hard "no" to anything that needs an operator.
License
AGPL-3.0-or-later (LICENSE). Commercial licensing for embedding in closed products:
open an issue titled commercial license.
Contributions: see CONTRIBUTING.md. Security reports: see
SECURITY.md.
Available Tools
4 toolsechoA
Echo the given text back unchanged. Used to verify the MCP wiring.
Inputs: text (required).
memory_addA
Store a memory for later retrieval. Returns duplicate=true when identical content already exists (no new record), and embedding_failed=true when the memory was saved but vectorization failed (keyword search still works).
Inputs: content (required), kind, scope, ttl_hours. Returns: id, dry_run, embedded, redacted, +4 more
memory_deleteA
Soft-delete a memory by id. Already-deleted ids are idempotent; an unknown id returns an error instead of pretending to succeed.
Inputs: id (required). Returns: deleted
memory_searchA
Search memories with vector search first and keyword fallback. degraded=true means the vector path was unavailable; degrade_reason explains why. An empty query lists recent memories.
Inputs: limit, query, scope, include_expired. Returns: hits, degraded, degrade_reason
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: echo is a wiring check, while memory_add, memory_delete, and memory_search map to separate lifecycle operations on a single resource. Descriptions reinforce the boundaries (e.g., soft-delete vs. store vs. hybrid search).
The three core tools follow a clean memory_verb snake_case pattern. echo is the only deviation, but as a conventional diagnostic utility it does not create confusion.
Four tools is slim but reasonable for a focused memory store; each earns its place except arguably echo, which is a wiring diagnostic rather than a memory operation. Not thin enough to be a mismatch.
Add, search (with list-recent fallback), and delete cover the core lifecycle, but there is no get-by-id or update/edit operation, so an agent cannot correct or inspect a specific memory without going through search. These are minor workaround-able gaps assuming memories are effectively immutable.
Maintenance
Related MCP Connectors
Persistent, inspectable memory for AI agents with lineage, correction, and a hosted MCP endpoint.
Persistent memory for AI agents. Semantic search, memory graph, W3C DID identity.
Hosted memory for AI agents over MCP. One memory shared by all your agents.
Private-by-default, local-first memory/context/task orchestrator for MCP apps and agents.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceSelf-hosted semantic memory for AI agents. Save worklogs, decisions, and notes via MCP, then recall them across sessions by meaning rather than keyword. Backed by Postgres + pgvector with local embeddings (multilingual-e5-base).1MIT
- FlicenseNot gradedqualityCmaintenanceA local-first, privacy-preserving centralized memory hub for AI agents — MCP-compatible, zero cloud egress.3-
- AlicenseAqualityCmaintenanceEmbedded memory and retrieval engine for AI agents, providing local-first memory with MCP support for multi-agent access control.32MIT
- AlicenseNot gradedqualityAmaintenanceAn offline-first, governed memory and knowledge server for AI agents that provides Remember, Search, Update, and Forget operations with hybrid retrieval, semantic embeddings, and NID-based authentication. It can be used as an MCP server via stdio or Streamable HTTP, enabling agents to persist and query memories and wiki knowledge.Apache 2.0