Ext Ops Panel
Open dashboard
Comparison

io.github.Octonove/crbro-memory vs io.github.PeterAtPondo/kit-memory-demo

io.github.Octonove/crbro-memory is an MCP server published by Octonove. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.PeterAtPondo/kit-memory-demo is an MCP server published by PeterAtPondo. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
Marketplaceio.github.Octonove/crbro-memoryio.github.PeterAtPondo/kit-memory-demo
Official MCP Registry Listed
Version: 2.10.0
Downloads/month (npm): 2 821
Downloads/week (npm): 411
Forks (GitHub): 1
Stars (GitHub): 8
Not marked · First seen
Listed
Version: 1.0.1
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

io.github.Octonove/crbro-memory vs io.github.PeterAtPondo/kit-memory-demo
Factio.github.Octonove/crbro-memoryio.github.PeterAtPondo/kit-memory-demo
Marketplaces that list it11
Stars (GitHub) (differs)8 (better)0 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last release (differs)2026-10-18Not published
Where it runs (differs)On your machine (crbro-memory)Remote server (demo-mcp.kit-project.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/octonove/crbro-memorygithub.com/peteratpondo/kit-demo-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-24

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

io.github.Octonove/crbro-memory

In its own words, on Official MCP Registry:

Persistent file-based memory for AI agents: inspectable, versionable, fully local.

io.github.PeterAtPondo/kit-memory-demo

In its own words, on Official MCP Registry:

Continuity for agents: a live memory you can read and cite right now, outliving the context window.

How to run each

io.github.Octonove/crbro-memory As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio crbro-memory -- npx -y crbro-memory

io.github.PeterAtPondo/kit-memory-demo As a remote MCP server

Claude Code
claude mcp add --transport http kit-memory-demo https://demo-mcp.kit-project.com/mcp --header "Authorization: Bearer kbr_live_Kh9eO_ZfLldveFf1KXJEEvepfOpdgRqf7KoDDU3rB18"

Requires: Authorization header

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

Only io.github.PeterAtPondo/kit-memory-demo 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: io.github.Octonove/crbro-memory · What it can do: io.github.PeterAtPondo/kit-memory-demo · 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.

Where the data comes from: how the catalog is built