Ext Ops Panel
Open dashboard
Comparison

leteo vs Nautilus Compass Memory

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

leteo is a plugin bundle for AI coding tools published by Alexis Sanabria Lopez. No marketplace we read lists it any more. Nautilus Compass Memory is an MCP server published by chunxiaoxx. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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
MarketplaceleteoNautilus Compass Memory
Community marketplace asanabrial/leteo Removed on 2026-10-17
Version: 0.3.0
Forks (GitHub): 1
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 3.2.0
Downloads/month (PyPI): 704
Downloads/week (PyPI): 105
Forks (GitHub): 35
Stars (GitHub): 1 254
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

leteo vs Nautilus Compass Memory
Factleteono longer listed · Nautilus Compass Memory
Marketplaces that list it (differs)01
Stars (GitHub) (differs)21 254
Forks (GitHub) (differs)135
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (compass.nautilus.social/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)5Not published
Parts of the bundle (differs)6Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/asanabrial/leteogithub.com/chunxiaoxx/nautilus-compass
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, requires a key

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 leteo

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

  • engram

    Persistent memory with session tracking, compaction recovery, and Memory Protocol. Gives Claude a brain that survives across sessions.

    by Gentleman Programming · Plugin bundle

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

  • engram io.github.tstockham96/engram

    Intelligent agent memory with automatic extraction, consolidation, and bi-temporal recall.

    by tstockham96 · MCP server

    Listed on: Official MCP Registry, Claude Code: claude-plugins-community · Describes nearly the same job

  • agent-memory-hardened

    Persistent memory for AI agents: remember facts, learn from experience, and track entities across sessions.

    by faberlens · Plugin bundle

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

  • memoose

    A dual-path memory system for proactive agents: a typed knowledge graph with evidence, contradictions and supersession, maintained in the background on a small model. No API key…

    by Hieu Ngo · Plugin bundle

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

  • hivemind

    Persistent shared memory powered by Deeplake — captures all session activity and provides cross-session, cross-agent memory search

    by Activeloop · Plugin bundle

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

  • kairn

    Local memory with full-text recall and a recall-and-save skill.

    by PrimeLine · Plugin bundle

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

Its card, with similar plugins by marketplace

What each says it does

leteo

In its own words, on Community GitHub marketplaces:

Persistent memory with session tracking, compaction recovery, and a save protocol. Gives the agent a memory that survives across sessions.

Nautilus Compass Memory

In its own words, on Official MCP Registry:

Local-first long-term memory for AI agents, with byte-recomputable signed verification receipts.

How to run each

leteo

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

Nautilus Compass Memory As a remote MCP server

Claude Code
claude mcp add --transport http nautilus-compass https://compass.nautilus.social/mcp/ --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 Nautilus Compass Memory 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: leteo · What it can do: Nautilus Compass Memory · 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