Ext Ops Panel
Open dashboard
Comparison

cachly AI Brain vs io.github.theluckystrike/study-flashcards-exam-prep

cachly AI Brain is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑17.

cachly AI Brain is a plugin bundle for AI coding tools published by cachly. No marketplace we read lists it any more. io.github.theluckystrike/study-flashcards-exam-prep is an MCP server published by theluckystrike. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacecachly AI Brainio.github.theluckystrike/study-flashcards-exam-prep
Community marketplace cachly-dev/cachly-mcp Removed on 2026-10-17
Version: 0.10.201
Forks (GitHub): 1
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.23.1
Forks (GitHub): 0
Stars (GitHub): 2
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

cachly AI Brain vs io.github.theluckystrike/study-flashcards-exam-prep
Factcachly AI Brainno longer listed · io.github.theluckystrike/study-flashcards-exam-prep
Marketplaces that list it (differs)01
Stars (GitHub)22
Forks (GitHub) (differs)10
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@cachly-dev/mcp-server)Remote server (mcp.zovo.one/mcp/study-flashcards-exam-prep)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 0Not published
Hooks it runs (differs)3Not published
Parts of the bundle (differs)4Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/cachly-dev/cachly-mcpgithub.com/theluckystrike/mcp-servers
Changes in the last 7 days (differs)20
First seen (differs)2026-10-132026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 days ago

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of cachly AI Brain

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • Total Agent Memory

    Persistent local memory for coding agents: temporal knowledge graph, procedural and episodic recall

    by vbcherepanov · MCP server

    Listed on: Official MCP Registry, Community GitHub marketplaces · Describes nearly the same job

  • origin

    AI work memory for Claude Code: brief, capture, recall, handoff, and distill, backed by a local daemon and MCP so decisions, lessons, project context, and wiki pages carry across…

    by Qi-Xuan Lu · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • memora

    Persistent semantic memory for Claude Code — auto-injects relevant context at session start, captures git commits, test results, and research via hooks, and provides 30+ MCP tools…

    by agentic-mcp-tools · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • claude-memory

    A Claude Code plugin that adds structured, categorized memory to your projects.

    by tars23364-bit · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • claude-memory

    Long-term memory for Claude Code. Recalls architecture, conventions, and decisions across sessions, plus an episodic observation log of what happened — so Claude explains your…

    by Valentino Stoll · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • Remem

    Persistent project memory for Codex through remem MCP and explicit hook activation.

    by majiayu000 · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

cachly AI Brain

In its own words, on Community GitHub marketplaces:

Your assistant forgets everything each morning. cachly remembers your system: the bug you fixed, why you chose Postgres, the deploy step that always breaks — and which earlier decision a new one contradicts. Every editor reads the same memory, and every lesson carries the name of whoever learned it.

io.github.theluckystrike/study-flashcards-exam-prep

In its own words, on Official MCP Registry:

Build study flashcards and exam-prep decks from your AI chat, all stored locally.

How to run each

cachly AI Brain

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

io.github.theluckystrike/study-flashcards-exam-prep As a remote MCP server

Claude Code
claude mcp add --transport http study-flashcards-exam-prep https://mcp.zovo.one/mcp/study-flashcards-exam-prep --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only io.github.theluckystrike/study-flashcards-exam-prep 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 io.github.theluckystrike/study-flashcards-exam-prep publish no settings it asks for, so we do not compare settings.

What it can do: cachly AI Brain · What it can do: io.github.theluckystrike/study-flashcards-exam-prep · 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