Ext Ops Panel
Open dashboard
Comparison

Mnemoverse Memory vs MemoCat — Shared AI Memory

Mnemoverse Memory is a plugin bundle for AI coding tools published by Mnemoverse. Marketplaces we read that list it: 1 (Community GitHub marketplaces). MemoCat — Shared AI Memory is an MCP server published by MontyGovernance. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-15. 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

Where each is published
MarketplaceMnemoverse MemoryMemoCat — Shared AI Memory
Community marketplace hashgraph-online/awesome-codex-plugins Listed
Version: 1.0.4
Forks (GitHub): 491
Stars (GitHub): 1 576
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.4.3
Downloads/month (PyPI): 1 030
Downloads/week (PyPI): 25
Forks (GitHub): 6
Stars (GitHub): 27
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

Mnemoverse Memory vs MemoCat — Shared AI Memory
FactMnemoverse MemoryMemoCat — Shared AI Memory
Marketplaces that list it11
Stars (GitHub) (differs)1 576 (better)27 (worse)
Forks (GitHub) (differs)491 (better)6 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.mnemoverse.com/mcp)On your machine (memocat-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)8Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/hashgraph-online/awesome-codex-pluginsgithub.com/montygovernance/memocat-mcp
Changes in the last 7 days (differs)20
First seen (differs)2026-11-142026-10-11
Endpoint at the last check (differs)Responded 7 h ago, requires authenticationno 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

Mnemoverse Memory

In its own words, on Community GitHub marketplaces:

Hosted AI agent memory that learns from outcomes, over remote MCP with OAuth sign-in: tell it a recalled memory helped or misled and it re-ranks what comes back next, with shared rooms for multi-agent work.

MemoCat — Shared AI Memory

In its own words, on Official MCP Registry:

One shared, persistent memory across AI agents and systems, with semantic recall and live updates.

How to run each

Mnemoverse Memory As a Codex plugin

Codex
codex plugin marketplace add hashgraph-online/awesome-codex-plugins

MemoCat — Shared AI Memory As a local MCP server: PyPI package

Claude Code
claude mcp add --env "MONTYCAT_URI=<YOUR_MONTYCAT_URI>" --transport stdio memocat-mcp -- uvx memocat-mcp

Requires: MONTYCAT_URI (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Mnemoverse 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

The marketplaces of Mnemoverse Memory publish no settings it asks for, so we do not compare settings.

What it can do: Mnemoverse Memory · What it can do: MemoCat — Shared AI Memory · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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.

Where the data comes from: how the catalog is built