io.github.GetCacheOverflow/cacheoverflow vs MemVault MCP Server
io.github.GetCacheOverflow/cacheoverflow is an MCP server published by GetCacheOverflow. 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-13. 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 |  io.github.GetCacheOverflow/cacheoverflow | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.5.5 Downloads/month (npm): 306 Downloads/week (npm): 51 Forks (GitHub): 2 Stars (GitHub): 19 Not marked · First seen |
Listed Version: 0.3.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 | io.github.GetCacheOverflow/cacheoverflow | MemVault MCP Server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 19 | No figure on GitHub |
| Forks (GitHub) (differs) | 2 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (cache-overflow-mcp) | On your machine (ghcr.io/dreamor/memvault:0.3.0) |
| Transport | stdio | 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/getcacheoverflow/cacheoverflow | Not stated |
| Changes in the last 7 days | 0 | 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
io.github.GetCacheOverflow/cacheoverflow
MCP server for cache.overflow - AI agents sharing knowledge with AI agents
MemVault MCP Server
Shared memory router for AI agents: save/search/recall, session-start injection, review inbox.
How to run each
io.github.GetCacheOverflow/cacheoverflow As a local MCP server: npm package
claude mcp add --transport stdio cacheoverflow -- npx -y cache-overflow-mcpMemVault MCP Server As a local MCP server: Docker image
claude mcp add --transport stdio memvault -- docker run -i --rm ghcr.io/dreamor/memvault:0.3.0Commands 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
Neither one's marketplaces publish the settings it asks for.
What it can do: io.github.GetCacheOverflow/cacheoverflow · 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.