VelesDB Memory runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 18 Sep 2026.
Offline agentic memory: remember/recall/relate/forget/why over a fused vector+graph+columnar engine
We read the source, 22 h ago · rules 3dff92dd89df
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));
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
rustup toolchain install --no-self-update --profile minimal
rustup target add ${{ matrix.target }}
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
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.
Fused graph of your codebase — static code + runtime OTel — for AI agents, over MCP.
Persistent knowledge memory for AI agents. Hybrid search, code graph, pgvector.
Local-first memory for AI coding agents. Memory + CodeGraph + Wiki in one SQLite file.
Local code-memory graph for AI coding agents.
Memory, docs, and repo context layer for engineering agents.
Semantic code search for AI agents — hybrid BM25+vector, call-graph, 20+ languages.
Local Go repository call graphs and structural analysis for coding agents over stdio.
FAISS, call graph, AST, BM25 — 34 MCP tools for AI agents. 50-80% token reduction. Offline.
Answers built from our own checks of this server.