Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-cyberlife-coder-velesdb-memory": {
"args": [
"-y",
"@wiscale/velesdb-wasm"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Your AI agents forget everything. VelesDB fixes that.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@wiscale/velesdb-wasm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @wiscale/velesdb-wasm against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in security
Proof primitive for AI agents on MultiversX. Anchor file hashes on-chain as verifiable proofs.
Model Context Protocol for WinDBG
Security scanner for GitHub repos, Agent Skills, Plugins, and MCP servers. 18 scanners. Zero dependencies.
AI agent trust & reputation protocol — verify, score, route, compare, delegate. 18 tools.
MCP Security Weekly
Get CVE alerts and security updates for io.github.cyberlife-coder/velesdb-memory and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
One ~9 MB binary. Three engines. One query language. Zero cloud dependency.
Vector + Graph + ColumnStore — unified under VelesQL
Download latest release • Quick Start • Architecture • Roadmap • Quality Bar • Documentation • DeepWiki
Every AI agent today stitches together 3 databases for memory — vectors for "what feels similar", a graph for "what is connected", and SQL for "what I know for sure". That's 3 deployments, 3 configs, 3 query languages, and a pile of glue code.
VelesDB replaces all of that with a single Rust binary — smaller than a single smartphone photo.
VelesDB was born in France out of a simple observation: EU data sovereignty is an architectural problem, not a legal one.
The US Cloud Act, FISA 702, and PATRIOT Act give US authorities multiple legal paths to reach data held by any US company — regardless of where the servers are. Hosting on AWS eu-west-1 is a latency decision, not a sovereignty decision. The EU's Data Privacy Framework has been invalidated twice (Schrems I, Schrems II), and a third challenge is pending.
For European developers building AI agents that handle health data, legal documents, or financial records, the typical 2026 stack sends embeddings to Pinecone (US), graphs to Neo4j Aura (US), and