Memors runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 14 Oct 2026.
Local, explainable knowledge base for AI agents: hybrid search with provenance over SQLite.
What the code does
We read the source, 1 d ago · rules ccca72095570
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.
rel := filepath.Join(ns, d.Prov.Kind, slug(d.Prov.Title)+"-"+shortID(d.ID)+".md")
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 Memors
same job, measured the same wayLocal, explainable knowledge base for AI agents: hybrid search with provenance over SQLite.
Local-first memory for AI agents: on-device hybrid retrieval over a single SQLite file.
Local code search for AI coding agents: hybrid keyword + semantic + SQL over an index in your repo.
Token-light local memory with SQLite hybrid retrieval for MCP agents.
Bi-temporal, provenance-carrying long-term memory for AI agents, in one SQLite file.
Lightweight persistent memory for AI agents. Hybrid search. 16 tools. One SQLite file.
Local-first, auditable memory for MCP-compatible AI agents with explicit writes and SQLite storage.
MCP server for AlphaFold and 8 other biomedical data sources with a local SQLite knowledge graph
Memors — questions
Answers built from our own checks of this server.