Databases · MCP server
VelesDB Memory: MCP server, setup and security
VelesDB Memory is an MCP server published on GitHub that lets an AI agent remember, recall, relate and forget information using offline agent memory. Its repository has 100 stars and its last commit is from October 24, 2026, but it declares no licence.
| Adoption (stars) | 20/40 | |
|---|---|---|
| Maintenance | 30/30 | |
| Framework (licence, registry, official) | 5/30 |
What VelesDB Memory does
According to its repository: “Offline agentic memory: remember/recall/relate/forget/why over a fused vector+graph+columnar engine”
The Model Context Protocol (MCP) is a standard plug between an AI agent and an outside service: once the server is connected, its tools show up in the agent, which decides when to call them. VelesDB Memory is listed under Databases, a category of 138 servers in the directory, where it ranks #69 by stars.
Topics declared by the repository: embeddings, hnsw, local-first, machine-learning, rag, rust.
Installing and connecting VelesDB Memory
Distribution modes declared in the official MCP registry:
- MCPB bundle (one-click install in Claude Desktop)
It works with any MCP-compatible client (Claude Desktop, Claude Code, Cursor, VS Code, Codex and most recent agents). You add one entry to the client's MCP configuration: server name, start command or URL, environment variables. Project language: Rust.
Security: what to check
Connecting an MCP server means installing software that talks straight to your agent: it runs with your rights and the model trusts its tool descriptions. The risk therefore depends on what it can touch and how far its code can be trusted.
Points found for VelesDB Memory:
- No licence: without a licence the code is not legally reusable, even if it is public. Avoid it in a company setting without the author's agreement.
Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.
Project activity and maintenance
Created on December 17, 2025, the cyberlife-coder/VelesDB repository has 100 stars and 12 forks, with 35 open issues. It has more stars than 67% of the servers in the directory. It received changes this month. Version published in the registry: 0.14.2 (September 3, 2026).
Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.
Verdict
VelesDB Memory is a reasonable choice; check the points below before connecting it.
Strengths
- Active project: recent commit
- Listed in the official MCP registry
Limitations
- No licence declared
Avoid if…
- Company use without the author's agreement
Alternatives
- Nhost9.4K ★
- ArcadeDB MCP Server1.2K ★
- Jitsu5.1K ★
- Supabase3K ★
- Dbx27.7K ★
- MCP Toolbox for Databases16.7K ★
Learn more
Frequently asked questions
How do I install VelesDB Memory?
VelesDB Memory is distributed as MCPB bundle (one-click install in Claude Desktop). Add it to your client's MCP configuration (Claude Desktop, Cursor, VS Code…) following the README of cyberlife-coder/VelesDB.
Is VelesDB Memory free?
The code is public but has no declared licence: it is not formally free to reuse.
Is VelesDB Memory safe?
Points to watch: no licence. Give it minimum rights and approve sensitive actions.
Is it an official server?
Nothing says so: it is a project published by cyberlife-coder on GitHub. Check who maintains it before giving it access.
What are the alternatives to VelesDB Memory?
In the same category: Nhost, ArcadeDB MCP Server, Jitsu, and Supabase. Nhost and ArcadeDB MCP Server score higher on our grid.
Related articles
- Build your own MCP server in 30 minutesOctober 24, 2026
- Automate your inbox with an AI agentOctober 18, 2026
- MCP, A2A, and tool calling: agent protocols explainedOctober 17, 2026
- Build an AI agent with n8n, without codingOctober 16, 2026
Neutrality. No affiliate links. No vendor pays to be reviewed, rated or ranked. Reviews are directed by François Chollet, neutral and factual, and every data point is dated and sourced. How we score