Memory Vault vs io.github.dbnexsus/nexsus
Memory Vault is an MCP server published by MihaiBuilds. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.dbnexsus/nexsus is an MCP server published by dbnexsus. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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 |  Memory Vault |  io.github.dbnexsus/nexsus |
|---|---|---|
| Official MCP Registry | Listed Version: 1.6.1 Forks (GitHub): 14 Stars (GitHub): 65 Not marked · First seen |
Listed Version: 1.0.0 No figure published 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 | Memory Vault | io.github.dbnexsus/nexsus |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 65 | No figure on GitHub |
| Forks (GitHub) (differs) | 14 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (ghcr.io/mihaibuilds/memory-vault-mcp:1.6.1) | Remote server (app.nexsus.com.au/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 5, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/mihaibuilds/memory-vault | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 404 (3 days ago) |
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
Memory Vault
Local-first AI memory layer with hybrid search. Postgres + pgvector. Self-hosted, MIT.
io.github.dbnexsus/nexsus
Private persistent memory for Claude, ChatGPT & Gemini via MCP - semantic search, zero-code setup.
How to run each
Memory Vault As a local MCP server: Docker image
claude mcp add --env "DB_HOST=<YOUR_DB_HOST>" --env "DB_NAME=<YOUR_DB_NAME>" --env "DB_PASSWORD=<YOUR_DB_PASSWORD>" --env "DB_PORT=<YOUR_DB_PORT>" --env "DB_USER=<YOUR_DB_USER>" --transport stdio memory-vault -- docker run -i --rm -e DB_HOST -e DB_NAME -e DB_PASSWORD -e DB_PORT -e DB_USER ghcr.io/mihaibuilds/memory-vault-mcp:1.6.1Requires: DB_HOST, DB_NAME, DB_PASSWORD (secret), DB_PORT, DB_USER
io.github.dbnexsus/nexsus As a remote MCP server
claude mcp add --transport http nexsus https://app.nexsus.com.au/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.dbnexsus/nexsus has a remote endpoint we check. How we check endpoints
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 io.github.dbnexsus/nexsus publish no settings it asks for, so we do not compare settings.
What it can do: Memory Vault · What it can do: io.github.dbnexsus/nexsus · 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.