VelesDB Memory vs amu-pgvector
VelesDB Memory is an MCP server published by cyberlife-coder. Marketplaces we read that list it: 1 (Official MCP Registry). amu-pgvector is an MCP server published by sangaraju1988. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  VelesDB Memory |  amu-pgvector |
|---|---|---|
| Official MCP Registry | Listed Version: 0.15.0 Forks (GitHub): 13 Stars (GitHub): 100 Not marked · First seen |
Listed Version: 0.1.3 Downloads/month (PyPI): 2 709 Downloads/week (PyPI): 31 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | VelesDB Memory | amu-pgvector |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 100 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 13 (better) | 0 (worse) |
| Last release (differs) | 2026-10-27 | Not published |
| Where it runs (differs) | On your machine (https://github.com/cyberlife-coder/VelesDB/releases/download/velesdb-memory-v0.15.0/velesdb-memory-0.15.0-aarch64-apple-darwin.mcpb) | On your machine (amu-pgvector) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/cyberlife-coder/velesdb | github.com/sangaraju1988/amu-pgvector |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
VelesDB Memory
Offline agentic memory: remember/recall/relate/forget/why over a fused vector+graph+columnar engine
amu-pgvector
Lineage-gated agent memory tools on Postgres + pgvector, enforced by row-level security.
How to run each
VelesDB Memory
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
amu-pgvector As a local MCP server: PyPI package
claude mcp add --env "AMU_PGVECTOR_DSN=<YOUR_AMU_PGVECTOR_DSN>" --transport stdio amu-pgvector -- uvx --from "amu-pgvector[mcp]==0.1.3" amu-pgvector amu-pgvector-mcpRequires: AMU_PGVECTOR_DSN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of VelesDB Memory publish no settings it asks for, so we do not compare settings.
What it can do: VelesDB Memory · What it can do: amu-pgvector · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.