# claude-mem vs EverOS (slim)

> EverOS scores 69.4 (B) to claude-mem's 54.6 (C) for agent memory. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/claude-mem-vs-everos.md (~4,050 tokens) · this version ~1,680 tokens · JSON https://www.anchorterminal.com/compare/claude-mem-vs-everos.json · canonical https://www.anchorterminal.com/compare/claude-mem-vs-everos
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

EverOS scores 69.4 (B) on agent readiness against claude-mem's 54.6 (C), and leads in 6 of 7 scored categories. Both do agent memory.

- claude-mem: C 54.6, rank #900 of 1486 · https://www.anchorterminal.com/tools/claude-mem.min.md
- EverOS: B 69.4, rank #246 of 1486 · https://www.anchorterminal.com/tools/everos.min.md
- claude-mem, good for Session memory for one developer's coding agents, recalled by staged MCP search, with optional hosted sync across machines.
- EverOS, good for Self-hosted memory for agents and apps that want Markdown as the source of truth and separate user and agent tracks. Ahead on Schema & documentation, 89 against 84; Payments & pricing, 40 against 20; Transparency & trust, 71 against 46. Also No key needed to call it; No incidents deducted, where claude-mem loses 8 points for them.

| Category | claude-mem | EverOS |
| --- | --- | --- |
| Reliability (16%) | 75 | 79 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 84 | 89 |
| Agent ergonomics (13%) | 74 | 78 |
| Security & auth (14%) | 50 | 47 |
| Payments & pricing (10%) | 20 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 76 | 80 |
| Transparency & trust (7%) | 46 | 71 |

| Fact (where they differ) | claude-mem | EverOS |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | Alex Newman | Evermind AI, Inc. |
| Transports | stdio, HTTP | HTTP, stdio |
| Auth | OAuth or key | None |
| Licence | Apache-2.0 for the engine, CLI, worker, MCP tools, adapters and docs. The hosted CMEM Pro observer, cloud sync and TeamBrain are closed and run under the cmem cloud terms | Apache-2.0 |
| Tools exposed | 19 | 7 |
| Last release | 2026-11-02 | 2026-10-22 |
| Terms last updated | couldn't be read | 2026-01-20 |
| Privacy policy last updated | no date given | 2026-01-20 |
| Customer content may train models | couldn't be read | yes |
| Terms restrict automated access | couldn't be read | yes |
| Terms restrict benchmarking | couldn't be read | yes |
| Terms or service can change without notice | couldn't be read | yes |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | 106k stars, 30k npm/wk | 14k stars, 4k PyPI/wk |

Why the edge:
- Transparency & trust, EverOS +25: claude-mem 46 (Apache-2.0 engine with the hosted observer, sync and team functions reserved as closed, per docs/ip-boundary.md (25 of 30). SECURITY.md lists every route by which data leaves the machine, but the cmem.ai privacy page, re-read on 4 November, still says "Nothing leaves your device unless you explicitly turn on cloud sync" and that sensitive details are filtered before storage, while secret redaction defaults to off, doesn't cover the hosted observer, and names no retention periods, subprocessors or legal entity. Locally, raw tool uses are kept forever by default (CLAUDE_MEM_TOOL_USES_RETENTION_DAYS 0) and daily logs 30 days since 15.7.0 (12 of 30). Release notes date breaking changes with migration steps, such as 15.0.0 and the removal of Gemini CLI support in 13.10.0, but no written deprecation policy (8 of 20). Telemetry is on by default, documented field by field (including PostHog's city-level location from the sender's IP) with `telemetry disable`, `DO_NOT_TRACK` and a separate error-reporting switch, and the installer asks once; the README doesn't mention it (16 of 20).); EverOS 71 (Apache-2.0 with a NOTICE file (30). Local data stays in the owner's Markdown and indexes. For the cloud, the privacy policy gives no retention periods, the terms and privacy policy word the training exceptions differently, and the privacy contact link points to a miromind.ai address (12 of 30). The README marks `/api/v1` as a legacy alias that may be removed in a future major release, and a 1.0 migration guide exists, with no notice period (14 of 20). No outbound telemetry was found in the source, and the docs don't address it (10 of 20). Total 66.)
- Payments & pricing, EverOS +20: claude-mem 20 (No x402, MPP or L402 (0). Scored on the hosted option, as the brief says for open-source software with a paid service. CMEM Pro $30, Heavy $70 and CMEM Max $100 a month are public, but the included usage is shown only at checkout (10 of 20). The engine is free with no card, but the pricing page says the CMEM Pro trial needs a credit or debit card while the README says sign-in needs none (10 of 20). The hosted service needs a browser sign-in by magic link (0).); EverOS 40 (Self-hosted rule, with the price lines read for EverOS Cloud. No x402, MPP or L402 (0 of 40). No cloud price or plan found on evermind.ai, its FAQ, terms or docs (0). The open-source runtime is free with no card (20). An agent can install it from PyPI and run it with no account (20). Total 40.)
- Schema & documentation, EverOS +5: claude-mem 84 (Every one of the 26 MCP tools declares a JSON Schema input (25). llms.txt at docs.claude-mem.ai with Markdown copies of each page (10). Descriptions give purpose and order of use (search, then timeline, then get_observations) and say when not to call a tool (`get_tool_uses` "rarely needed", `dumb_search` "fast, but shallow"), but the README says recall uses 4 tools and lists 3 while the server advertises 19 (15 of 20). Required fields are marked and some limits have minimum and maximum, but `type`, `orderBy` and `obs_type` are free strings described in prose, `limit` is a number rather than an integer on most tools, and `metadata` and `fields` are open objects (8 of 15). README examples and a worker API reference with 400 and 404 error bodies (11 of 15). Keep a Changelog file and release notes for each version (15).); EverOS 89 (OpenAPI document in the repository with 40 operations, every one with a description (25). llms.txt and llms-full.txt on docs.evermind.ai (10). Operation descriptions state purpose; when-not-to-use guidance appears in the docs, such as flush after add, rather than per operation (15 of 20). Typed request models with filter operators eq, ne, gt, gte, lt, lte and in, and 422 on malformed ids (12 of 15). curl examples for add, flush and search, and typed error codes such as SESSION_BUSY and EXTERNAL_SERVICE_UNAVAILABLE (12 of 15). `/api/v2` with `/api/v1` kept as a legacy alias, a changelog and release notes (15). Total 89.)