dark-memory-mcp vs io.github.jordanhindo/lore
dark-memory-mcp is an MCP server published by Opita-Code. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.jordanhindo/lore is an MCP server published by jordanhindo. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 4.0.0-alpha.32 Downloads/month (npm): 530 Downloads/week (npm): 281 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.1.1 Downloads/month (npm): 160 Downloads/week (npm): 32 Forks (GitHub): 1 Stars (GitHub): 15 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 | dark-memory-mcp | io.github.jordanhindo/lore |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (worse) | 15 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 1 (better) |
| Last release (differs) | 2026-10-15 | Not published |
| Where it runs (differs) | On your machine (@opitacode/dark-memory-mcp) | On your machine (@jordanhindo/lore) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/opita-code/dark-memory-mcp | github.com/jordanhindo/lore |
| Changes in the last 7 days (differs) | 1 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
dark-memory-mcp
Persistent memory + vibe-loop engine for AI agents. Single Go binary, SQLite-backed, stdio MCP.
io.github.jordanhindo/lore
Lightweight MCP for infinite agent memory. Any agent, any session, anytime.
How to run each
dark-memory-mcp As a local MCP server: npm package
claude mcp add --transport stdio dark-memory-mcp -- npx -y @opitacode/dark-memory-mcp
io.github.jordanhindo/lore As a local MCP server: npm package
claude mcp add --transport stdio lore -- npx -y @jordanhindo/lore
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
Neither one's marketplaces publish the settings it asks for.
What it can do: dark-memory-mcp · What it can do: io.github.jordanhindo/lore · 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.