Cairn.ink Memory vs MemVault MCP Server
Cairn.ink Memory is an MCP server published by cairn.ink. Marketplaces we read that list it: 1 (Official MCP Registry). MemVault MCP Server is an MCP server published by dreamor. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Forks (GitHub): 3 Stars (GitHub): 31 Not marked · First seen |
Listed Version: 0.6.1 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 | Cairn.ink Memory | MemVault MCP Server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 31 | No figure on GitHub |
| Forks (GitHub) (differs) | 3 | No figure on GitHub |
| Last release (differs) | Not published | 2026-10-21 |
| Where it runs (differs) | Remote server (cairn.ink/api/mcp) | On your machine (ghcr.io/dreamor/memvault:v0.6.1) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/cairn-ink/cairn-memory | Not stated |
| Changes in the last 7 days (differs) | 0 | 10 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 2 h ago, requires a key | no remote endpoint we check |
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
Cairn.ink Memory
Cross-session memory for AI agents with a Source Receipt for every memory, over MCP.
MemVault MCP Server
Shared memory router for AI agents: save/search/recall, session-start injection, review inbox.
How to run each
Cairn.ink Memory As a remote MCP server
claude mcp add --transport http memory https://cairn.ink/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"
Requires: Authorization header
MemVault MCP Server As a local MCP server: Docker image
claude mcp add --transport stdio memvault -- docker run -i --rm ghcr.io/dreamor/memvault:v0.6.1
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Cairn.ink Memory 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
Neither one's marketplaces publish the settings it asks for.
What it can do: Cairn.ink Memory · What it can do: MemVault MCP Server · 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.