VelesDB Memory runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 2 Nov 2026.
Offline agentic memory: remember/recall/relate/forget/why over a fused vector+graph+columnar engine
What the code does
We read the source, 1 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.
return readFile(path.join(pkgDir, wasmFile));
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 VelesDB Memory
same job, measured the same wayShared local memory for coding agents: SQLite, semantic recall, linked entities, code navigation.
Persistent knowledge memory for AI agents. Hybrid search, code graph, pgvector.
Deterministic code map for AI coding agents: a tree-sitter call graph with exact file:line over MCP.
Local-first memory for AI coding agents. Memory + CodeGraph + Wiki in one SQLite file.
One shared, versioned memory for Claude Code, Cursor, Codex and every MCP agent. Local and offline.
Code graph and project memory for coding agents, cited to exact files and lines, on your machine.
Project memory for coding agents whose memories carry code evidence, re-checked on every recall.
Memory, docs, and repo context layer for engineering agents.
VelesDB Memory — questions
Answers built from our own checks of this server.