Ext Ops Panel
Open dashboard
Comparison

com.usememra/memra vs io.github.varun29ankuS/shodh-memory

com.usememra/memra is an MCP server published by usememra.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.varun29ankuS/shodh-memory is an MCP server published by varun29ankuS. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. 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
Marketplacecom.usememra/memraio.github.varun29ankuS/shodh-memory
Official MCP Registry Listed
Version: 4.7.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.2.0
Downloads/month (npm): 289
Downloads/week (npm): 54
Forks (GitHub): 45
Stars (GitHub): 321
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

com.usememra/memra vs io.github.varun29ankuS/shodh-memory
Factcom.usememra/memraio.github.varun29ankuS/shodh-memory
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)321 (better)
Forks (GitHub) (differs)0 (worse)45 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (usememra.com/mcp)On your machine (@shodh/memory-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/usememra/mcpgithub.com/varun29ankus/shodh-memory
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Answered with HTTP 503 (13 h ago)no 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

com.usememra/memra

In its own words, on Official MCP Registry:

Persistent memory for AI agents. EU-hosted, privacy-first, hybrid recall, contradiction detection.

io.github.varun29ankuS/shodh-memory

In its own words, on Official MCP Registry:

Cognitive memory for AI agents — semantic search, Hebbian learning, knowledge graphs.

How to run each

com.usememra/memra As a remote MCP server

Claude Code
claude mcp add --transport http memra https://usememra.com/mcp

io.github.varun29ankuS/shodh-memory As a local MCP server: npm package

Claude Code
claude mcp add --env "SHODH_API_KEY=<YOUR_SHODH_API_KEY>" --transport stdio shodh-memory -- npx -y @shodh/memory-mcp

Requires: SHODH_API_KEY (secret)

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

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

What it can do: com.usememra/memra · What it can do: io.github.varun29ankuS/shodh-memory · 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