Ext Ops Panel
Open dashboard
Comparison

Memory Kernel vs io.github.kKEo/memory-find

Memory Kernel is an MCP server published by Artem362. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.kKEo/memory-find is an MCP server published by kKEo. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
MarketplaceMemory Kernelio.github.kKEo/memory-find
Official MCP Registry Listed
Version: 0.3.2
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Listed
Version: 1.5.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

Memory Kernel vs io.github.kKEo/memory-find
FactMemory Kernelio.github.kKEo/memory-find
Marketplaces that list it11
Stars (GitHub) (differs)3 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (amormorri-memory-kernel)On your machine (https://github.com/kKEo/memory-find/releases/download/v1.5.0/memo-mcp_1.5.0_linux_amd64.tar.gz)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 03, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)github.com/artem362/memory-kernelgithub.com/kkeo/memory-find
Changes in the last 7 days00
First seen2026-10-112026-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

Memory Kernel

In its own words, on Official MCP Registry:

Local-first memory for AI agents: SQLite FTS5, deterministic recall, no vector DB, no cloud.

io.github.kKEo/memory-find

In its own words, on Official MCP Registry:

Local, explainable knowledge base for AI agents: hybrid search with provenance over SQLite.

How to run each

Memory Kernel As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio memory-kernel -- uvx amormorri-memory-kernel

io.github.kKEo/memory-find

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

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

Only Memory Kernel asks for

  • MEMORY_KERNEL_DB

Only io.github.kKEo/memory-find asks for

  • MEMO_HOME
  • MEMO_KB
  • MEMO_MODEL

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Memory Kernel · What it can do: io.github.kKEo/memory-find · 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