MemoStem vs io.github.tstockham96/engram
MemoStem is an MCP server published by girapphe. 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-26. 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 |  MemoStem |  io.github.tstockham96/engram |
|---|---|---|
| Official MCP Registry | Listed Version: 0.6.3 Forks (GitHub): 0 Stars (GitHub): 0 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 | MemoStem | io.github.tstockham96/engram |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 47 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 6 (better) |
| Last release (differs) | 2026-10-16 | Not published |
| Where it runs (differs) | Remote server (www.memostem.com/api/mcp) | On your machine (engram-sdk) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Parts of the bundle (differs) | Not a bundle | 5 |
| Licence (differs) | Not stated | Proprietary |
| Repository (differs) | github.com/girapphe/memostem-plugins | github.com/tstockham96/engram |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 4 days 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
MemoStem
Your reviewed knowledge, across AI conversations.
io.github.tstockham96/engram
Intelligent agent memory with automatic extraction, consolidation, and bi-temporal recall.
How to run each
MemoStem As a remote MCP server
claude mcp add --transport http memostem https://www.memostem.com/api/mcpio.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.
Only MemoStem has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of io.github.tstockham96/engram nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
The marketplaces of MemoStem publish no settings it asks for, so we do not compare settings.
What it can do: MemoStem · 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.