Ext Ops Panel
Open dashboard
Comparison

darwin-memo vs OMEM

darwin-memo is an MCP server published by rogermsc. Marketplaces we read that list it: 1 (Official MCP Registry). OMEM is an MCP server published by troybrandonc-bit. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
Marketplacedarwin-memoOMEM
Official MCP Registry Listed
Version: 0.7.1
Downloads/month (PyPI): 252
Downloads/week (PyPI): 47
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.3.15
Downloads/month (PyPI): 710
Downloads/week (PyPI): 137
Forks (GitHub): 0
Stars (GitHub): 0
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

darwin-memo vs OMEM
Factdarwin-memoOMEM
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (darwin-memo)On your machine (omem-infrastructure)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 05, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/rogermsc/darwin-memogithub.com/troybrandonc-bit/omem
Changes in the last 7 days00
First seen2026-10-112026-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

darwin-memo

In its own words, on Official MCP Registry:

Self-curating agent memory kept honest by survival-based selection over measured outcomes.

OMEM

In its own words, on Official MCP Registry:

Memory for AI agents that tracks beliefs over time and surfaces contradictions

How to run each

darwin-memo As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio darwin-memo -- uvx --with "darwin-memo[mcp]" darwin-memo mcp

OMEM As a local MCP server: PyPI package

Claude Code
claude mcp add --env "OMEM_API_KEY=<YOUR_OMEM_API_KEY>" --env "OMEM_PROJECT=<YOUR_OMEM_PROJECT>" --transport stdio omem -- uvx omem-infrastructure

Requires: OMEM_API_KEY (secret), OMEM_PROJECT

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

Only darwin-memo asks for

  • DARWIN_MEMO_PATH

Only OMEM asks for

  • OMEM_AGENT
  • OMEM_API_KEY (secret)
  • OMEM_BASE_URL
  • OMEM_PROJECT
  • OMEM_USER

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: darwin-memo · What it can do: OMEM · 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.

Where the data comes from: how the catalog is built