Ext Ops Panel
Open dashboard
Comparison

io.github.STiFLeR7/memex vs io.github.philo-kim/openharness

io.github.STiFLeR7/memex is an MCP server published by STiFLeR7. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). io.github.philo-kim/openharness is an MCP server published by philo-kim. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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
Marketplaceio.github.STiFLeR7/memexio.github.philo-kim/openharness
Official MCP Registry Listed
Version: 1.0.2
Downloads/month (npm): 628
Downloads/week (npm): 393
Forks (GitHub): 0
Stars (GitHub): 12
Not marked · First seen
Listed
Version: 0.1.1
Downloads/month (npm): 147
Downloads/week (npm): 31
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Claude Code: claude-plugins-community Listed
Version: 0.3.2
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed

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

io.github.STiFLeR7/memex vs io.github.philo-kim/openharness
Factio.github.STiFLeR7/memexio.github.philo-kim/openharness
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)12 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (stifler-memex-mcp)On your machine (@freebird-ai/openharness)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)4, secrets among them: 2Not published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/stifler7/memexgithub.com/philo-kim/openharness
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

io.github.STiFLeR7/memex

In its own words, on Official MCP Registry:

Temporal engineering context for agents via MCP.

io.github.philo-kim/openharness

In its own words, on Official MCP Registry:

Lets AI coding agents discover and reference each other's recent sessions.

How to run each

io.github.STiFLeR7/memex As a local MCP server: npm package

Claude Code
claude mcp add --env "GEMINI_API_KEY=<YOUR_GEMINI_API_KEY>" --env "NEO4J_PASSWORD=<YOUR_NEO4J_PASSWORD>" --env "NEO4J_URI=<YOUR_NEO4J_URI>" --env "NEO4J_USER=<YOUR_NEO4J_USER>" --transport stdio memex -- npx -y stifler-memex-mcp serve --repo .

Requires: GEMINI_API_KEY (secret), NEO4J_PASSWORD (secret), NEO4J_URI, NEO4J_USER

io.github.philo-kim/openharness As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio openharness -- npx -y @freebird-ai/openharness

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 io.github.philo-kim/openharness publish no settings it asks for, so we do not compare settings.

What it can do: io.github.STiFLeR7/memex · What it can do: io.github.philo-kim/openharness · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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