Ext Ops Panel
Open dashboard
Comparison

dev.aieph/aieph vs io.github.STiFLeR7/memex

dev.aieph/aieph is an MCP server published by aieph.dev. Marketplaces we read that list it: 1 (Official MCP Registry). 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). As of our marketplace pass on 2026-10-23. 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
Marketplacedev.aieph/aiephio.github.STiFLeR7/memex
Official MCP Registry Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 1.0.2
Downloads/month (npm): 602
Downloads/week (npm): 50
Forks (GitHub): 0
Stars (GitHub): 12
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 0.3.2
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

dev.aieph/aieph vs io.github.STiFLeR7/memex
Factdev.aieph/aiephio.github.STiFLeR7/memex
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)1 (worse)12 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (aieph.dev/mcp)On your machine (stifler-memex-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published4, secrets among them: 2
Parts of the bundle (differs)Not a bundle1
Licence (differs)Not statedMIT
Repository (differs)github.com/tryaieph/aiephgithub.com/stifler7/memex
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 3 days agono 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

dev.aieph/aieph

In its own words, on Official MCP Registry:

Shared knowledge cache for AI coding agents — reuse an answer once it exists.

io.github.STiFLeR7/memex

In its own words, on Official MCP Registry:

Temporal engineering context for agents via MCP.

How to run each

dev.aieph/aieph As a remote MCP server

Claude Code
claude mcp add --transport http aieph https://aieph.dev/mcp

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

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

Only dev.aieph/aieph 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 dev.aieph/aieph publish no settings it asks for, so we do not compare settings.

What it can do: dev.aieph/aieph · What it can do: io.github.STiFLeR7/memex · 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