Ext Ops Panel
Open dashboard
Comparison

io.github.mifactory-bot/mifactory-agent-memory vs io.github.thelabvenice/memdata

io.github.mifactory-bot/mifactory-agent-memory is an MCP server published by mifactory-bot. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.thelabvenice/memdata is an MCP server published by thelabvenice. 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.mifactory-bot/mifactory-agent-memoryio.github.thelabvenice/memdata
Official MCP Registry Listed
Version: 1.3.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.4.1
Downloads/month (npm): 115
Downloads/week (npm): 15
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

io.github.mifactory-bot/mifactory-agent-memory vs io.github.thelabvenice/memdata
Factio.github.mifactory-bot/mifactory-agent-memoryio.github.thelabvenice/memdata
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (agent-memory-api.vercel.app/mcp)On your machine (memdata-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/mifactory-bot/agent-memory-apigithub.com/thelabvenice/memdata-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 6 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

io.github.mifactory-bot/mifactory-agent-memory

In its own words, on Official MCP Registry:

Persistent memory for AI agents across Claude, ChatGPT and any MCP client.

io.github.thelabvenice/memdata

In its own words, on Official MCP Registry:

Persistent memory for AI agents. Store context, retrieve it semantically.

How to run each

io.github.mifactory-bot/mifactory-agent-memory As a remote MCP server

Claude Code
claude mcp add --transport http mifactory-agent-memory https://agent-memory-api.vercel.app/mcp

io.github.thelabvenice/memdata As a local MCP server: npm package

Claude Code
claude mcp add --env "MEMDATA_API_KEY=<YOUR_MEMDATA_API_KEY>" --transport stdio memdata -- npx -y memdata-mcp

Requires: MEMDATA_API_KEY (secret)

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

Only io.github.mifactory-bot/mifactory-agent-memory 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 io.github.mifactory-bot/mifactory-agent-memory publish no settings it asks for, so we do not compare settings.

What it can do: io.github.mifactory-bot/mifactory-agent-memory · What it can do: io.github.thelabvenice/memdata · 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