Ext Ops Panel
Open dashboard
Comparison

Memory (Reference) vs Well-Being Check

Memory (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). Well-Being Check is an MCP server published by keenethics-labs.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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
MarketplaceMemory (Reference)Well-Being Check
Docker MCP Catalog Listed
Version: sha256:db0c2db07a44
Forks (GitHub): 11 874
Pulls (Docker Hub): 564 233
Stars (Docker Hub): 26
Stars (GitHub): 91 633
Not marked · First seen
Not listed
Official MCP Registry Not listed 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

Memory (Reference) vs Well-Being Check
FactMemory (Reference)Well-Being Check
Marketplaces that list it11
Stars (GitHub) (differs)91 633No figure on GitHub
Pulls (Docker Hub) (differs)564 233No figure on Docker Hub
Forks (GitHub) (differs)11 874No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/memory)Remote server (mental-tests-mcp-app.keenethics-labs.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)9Not published
Environment variables it asks forNot publishedNot published
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/keen-mcp/mental-tests
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 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 (Reference)

In its own words, on Docker MCP Catalog:

Knowledge graph-based persistent memory system.

Well-Being Check

In its own words, on Official MCP Registry:

Hosted MCP app for guided anxiety, depression, and well-being self-checks.

How to run each

Memory (Reference) As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio memory -- docker run -i --rm mcp/memory

Well-Being Check As a remote MCP server

Claude Code
claude mcp add --transport http well-being-check https://mental-tests-mcp-app.keenethics-labs.com/mcp

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

Only Well-Being Check has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Well-Being Check publish no list of tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Memory (Reference) · What it can do: Well-Being Check · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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