Ext Ops Panel
Open dashboard
Comparison

waza-think vs io.github.cdeust/hypermnesia-mcp

waza-think is a plugin bundle for AI coding tools published by tw93. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.cdeust/hypermnesia-mcp is an MCP server published by cdeust. Marketplaces we read that list it: 3 (Official MCP Registry, PyPI (MCP servers), Community GitHub marketplaces). As of our marketplace pass on 2026-11-10. 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
Marketplacewaza-thinkio.github.cdeust/hypermnesia-mcp
Community marketplace tw93/waza Listed
Version: 3.41.0
Forks (GitHub): 432
Stars (GitHub): 7 544
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 4.23.5
Downloads/month (PyPI): 1 993
Downloads/week (PyPI): 135
Forks (GitHub): 16
Stars (GitHub): 76
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 4.23.5
Downloads/month (PyPI): 1 993
Downloads/week (PyPI): 135
Forks (GitHub): 16
Stars (GitHub): 76
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

waza-think vs io.github.cdeust/hypermnesia-mcp
Factwaza-thinkio.github.cdeust/hypermnesia-mcp
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)7 544 (better)76 (worse)
Forks (GitHub) (differs)432 (better)16 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (hypermnesia-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 0
Hooks it runs (differs)Not published12
Parts of the bundle (differs)Not published26
Licence (differs)Not statedMIT
Repository (differs)github.com/tw93/wazagithub.com/cdeust/cortex
Changes in the last 7 days (differs)20
First seen (differs)2026-11-092026-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

waza-think

In its own words, on Community GitHub marketplaces:

Turns rough ideas into approved, decision-complete plans before coding. Use when planning architecture, judging whether to build, or writing a handoff. Not for bug fixes or small edits.

io.github.cdeust/hypermnesia-mcp

In its own words, on Official MCP Registry:

Persistent memory for AI agents — 36 cited neuroscience mechanisms, local-first, hybrid retrieval.

How to run each

waza-think As a Claude Code plugin

Claude Code
/plugin marketplace add tw93/waza
/plugin install waza-think@waza

io.github.cdeust/hypermnesia-mcp As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio hypermnesia-mcp -- uvx hypermnesia-mcp

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 waza-think publish no settings it asks for, so we do not compare settings.

What it can do: waza-think · What it can do: io.github.cdeust/hypermnesia-mcp · 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. Package data comes from the Python Package Index (pypi.org). 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