Ext Ops Panel
Open dashboard
Comparison

everos-mcp vs SlashML (/ml) Persistent Agent Memory & Code Localization

everos-mcp is an MCP server published by EverMind-AI. Marketplaces we read that list it: 1 (PyPI (MCP servers)). SlashML (/ml) Persistent Agent Memory & Code Localization is an MCP server published by slashml-ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. 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
Marketplaceeveros-mcpSlashML (/ml) Persistent Agent Memory & Code Localization
PyPI (MCP servers) Listed
Version: 0.1.1
Downloads/month (PyPI): 0
Downloads/week (PyPI): 155
Forks (GitHub): 1
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.11
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

everos-mcp vs SlashML (/ml) Persistent Agent Memory & Code Localization
Facteveros-mcpSlashML (/ml) Persistent Agent Memory & Code Localization
Marketplaces that list it11
Stars (GitHub) (differs)2 (better)0 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last release (differs)2026-10-16Not published
Where it runs (differs)On your machine (everos-mcp)Remote server or your machine
Transport (differs)Not statedstdio, Streamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/evermind-ai/everos-mcpgithub.com/slashml-ai/ml-memory
Changes in the last 7 days (differs)04
First seen (differs)2026-10-122026-11-08
Endpoint at the last check (differs)no remote endpoint we checkResponded 13 h ago

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

everos-mcp

In its own words, on PyPI (MCP servers):

MCP server for EverOS — long-term memory for AI agents, backed by the EverOS Cloud Memory API (v2)

SlashML (/ml) Persistent Agent Memory & Code Localization

In its own words, on Official MCP Registry:

Persistent conversational memory, behavioral code search, and bug localization for AI agents.

How to run each

everos-mcp

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

SlashML (/ml) Persistent Agent Memory & Code Localization As a local MCP server: npm package

Claude Code
claude mcp add --env "SLASHML_API_KEY=<YOUR_SLASHML_API_KEY>" --transport stdio ml-memory -- npx -y @slashml/mcp

Requires: SLASHML_API_KEY (secret)

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

Only SlashML (/ml) Persistent Agent Memory & Code Localization 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 everos-mcp publish no settings it asks for, so we do not compare settings.

What it can do: everos-mcp · What it can do: SlashML (/ml) Persistent Agent Memory & Code Localization · Compare two other plugins

Package data comes from the Python Package Index (pypi.org). 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