memalyze runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 28 Oct 2026.
Self-hosted agent memory: redaction before write, append-only audit, local embeddings.
What the code does
We read the source, 4 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
<p>Add, search and delete are appended to an audit table. The query is stored as SHA-256 + length, never plaintext. Export one CSV and hand it to an auditor.</p>
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to memalyze
same job, measured the same wayMemory, reflection and safety for AI agents. Hosted or local, no vector database.
Local-first persistent memory for AI agents — SQLite + local embeddings, MCP-native, no cloud.
Local-first memory for coding agents — MCP server, single SQLite file, local embeddings
Portable agent memory anchored on Solana. Local SQLite + vector recall, open export.
RAG memory for LLM agents over Garnet Vector Sets: store text as embeddings, recall by meaning.
Persistent memory for AI agents — semantic + recency search, ONNX embeddings, Docker Compose.
Bilingual dual memory with SSC for AI agents. Semantic search, embeddings, profiles.
Shared memory + orchestration for your coding agents. Local-first MCP, vector RAG.
memalyze — questions
Answers built from our own checks of this server.