Ext Ops Panel
Open dashboard
Comparison

io.github.gitmem-dev/gitmem vs ID MANDAT – Registry for AI Agents

io.github.gitmem-dev/gitmem is an MCP server published by gitmem-dev. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). ID MANDAT – Registry for AI Agents is an MCP server published by idmandat. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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.gitmem-dev/gitmemID MANDAT – Registry for AI Agents
Official MCP Registry Listed
Version: 1.2.1
Downloads/month (npm): 1 924
Downloads/week (npm): 133
Forks (GitHub): 1
Stars (GitHub): 9
Not marked · First seen
Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Listed
Version: 1.11.2
Downloads/month (npm): 1 924
Downloads/week (npm): 133
Forks (GitHub): 1
Stars (GitHub): 9
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.gitmem-dev/gitmem vs ID MANDAT – Registry for AI Agents
Factio.github.gitmem-dev/gitmemID MANDAT – Registry for AI Agents
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)9 (better)0 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (gitmem-mcp)Remote server (idmandat.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/gitmem-dev/gitmemgithub.com/idmandat/check
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-15
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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.gitmem-dev/gitmem

In its own words, on Official MCP Registry:

Persistent institutional memory for AI coding agents. Memory that compounds.

ID MANDAT – Registry for AI Agents

In its own words, on Official MCP Registry:

Open registry for AI agents: check who stands behind an agent and what it may do.

How to run each

io.github.gitmem-dev/gitmem As a local MCP server: npm package

Claude Code
claude mcp add --env "SUPABASE_SERVICE_ROLE_KEY=<YOUR_SUPABASE_SERVICE_ROLE_KEY>" --transport stdio gitmem -- npx -y gitmem-mcp

Requires: SUPABASE_SERVICE_ROLE_KEY (secret)

ID MANDAT – Registry for AI Agents As a remote MCP server

Claude Code
claude mcp add --transport http registry https://idmandat.com/mcp

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 ID MANDAT – Registry for AI Agents publish no settings it asks for, so we do not compare settings.

What it can do: io.github.gitmem-dev/gitmem · What it can do: ID MANDAT – Registry for AI Agents · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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