MyMemory vs io.github.tstockham96/engram
MyMemory is an MCP server published by mymemory.dev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.tstockham96/engram is an MCP server published by tstockham96. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). 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
| Marketplace |  io.github.tstockham96/engram | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.1 No figure published Not marked · First seen |
Listed Version: 0.5.1 Downloads/month (npm): 474 Downloads/week (npm): 109 Forks (GitHub): 6 Stars (GitHub): 47 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 1.0.0 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
| Fact | MyMemory | io.github.tstockham96/engram |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 47 |
| Forks (GitHub) (differs) | No figure on GitHub | 6 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.mymemory.dev/v1/mcp) | On your machine (engram-sdk) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | 1, secrets among them: 1 | 1, secrets among them: 1 |
| Parts of the bundle (differs) | Not a bundle | 5 |
| Licence (differs) | Not stated | Proprietary |
| Repository (differs) | Not stated | github.com/tstockham96/engram |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-16 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | 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
MyMemory
Long-term memory for AI assistants: search, read and save your notes, links and documents.
io.github.tstockham96/engram
Intelligent agent memory with automatic extraction, consolidation, and bi-temporal recall.
How to run each
MyMemory As a remote MCP server
claude mcp add --transport http memory https://api.mymemory.dev/v1/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: EVERSTASH_API_KEY (secret), Authorization header
io.github.tstockham96/engram As a local MCP server: npm package
claude mcp add --env "GEMINI_API_KEY=<YOUR_GEMINI_API_KEY>" --transport stdio engram -- npx -y engram-sdkRequires: GEMINI_API_KEY (secret)
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
Only MyMemory asks for
EVERSTASH_API_KEY (secret)
Only io.github.tstockham96/engram asks for
GEMINI_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: MyMemory · What it can do: io.github.tstockham96/engram · 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.