Ext Ops Panel
Open dashboard
Comparison

engram vs Nightspar

engram is a plugin bundle for AI coding tools published by Quan Duong. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Nightspar is an MCP server published by nightspar.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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
MarketplaceengramNightspar
Community marketplace nagisanzenin/engram Listed
Version: 1.15.1
Forks (GitHub): 108
Stars (GitHub): 1 477
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
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

engram vs Nightspar
FactengramNightspar
Marketplaces that list it11
Stars (GitHub) (differs)1 477No figure on GitHub
Forks (GitHub) (differs)108No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (api.nightspar.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)7Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/nagisanzenin/engramNot stated
Changes in the last 7 days (differs)02
First seen (differs)2026-10-292026-11-07
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 2 days ago returned HTTP 405

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

engram

In its own words, on Community GitHub marketplaces:

Evidence-based learning engine: learn anything, verify by free recall, schedule with FSRS, adapt from your own retention data.

Nightspar

In its own words, on Official MCP Registry:

Save words from your AI chats as spaced-repetition flashcards, with meanings, IPA and audio.

How to run each

engram As a Claude Code plugin

Claude Code
/plugin marketplace add nagisanzenin/engram
/plugin install engram@engram

Nightspar As a remote MCP server

Claude Code
claude mcp add --transport http nightspar https://api.nightspar.com/mcp

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

Only Nightspar 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

Neither one's marketplaces publish the settings it asks for.

What it can do: engram · What it can do: Nightspar · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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