# EverOS vs MemMachine

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

- Canonical: https://www.anchorterminal.com/compare/everos-vs-memmachine
- Markdown: https://www.anchorterminal.com/compare/everos-vs-memmachine.md (~4,250 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

EverOS scores 69.4 (B) on agent readiness against MemMachine's 58 (C), and leads in 5 of 7 scored categories. Both do agent memory.

- EverOS: grade B, 69.4/100, rank #246 of 1486. Markdown https://www.anchorterminal.com/tools/everos.md · JSON https://www.anchorterminal.com/api/v1/tools/everos.json
- MemMachine: grade C, 58/100, rank #767 of 1486. Markdown https://www.anchorterminal.com/tools/memmachine.md · JSON https://www.anchorterminal.com/api/v1/tools/memmachine.json
- Best memory layers for AI agents: https://www.anchorterminal.com/best/agent-memory/index.md
- All 353 memory comparisons: https://www.anchorterminal.com/compare/agent-memory/index.md

## Which one, for what

### EverOS (B)

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:
- Reliability, 79 against 51
- Schema & documentation, 89 against 79
- Agent ergonomics, 78 against 65
- Security & auth, 47 against 41
- Transparency & trust, 71 against 57

Watch for: The local HTTP server has no authentication and relies on binding to 127.0.0.1

### MemMachine (C)

Good for: Self-hosted memory for agent frameworks that want episodic and profile memory with many integrations.

Watch for: Version 0.4.0 of 6 October 2026, pre-1.0, with no changelog file in the repository


## Why the edge

### Reliability: EverOS +28

- EverOS (79): Local-software lines, as a library and server the owner runs. `everos` on PyPI with Python 3.12 or newer stated, plus a Windows guide (20). ci.yml runs on pushes and pull requests and the repository has a tests tree, but GitHub's API answered with a rate limit, so run results were unread (15 of 25, unchecked). 43 open issues and pull requests against 82 commits in 90 days; several outside bug reports, including a silent capture failure in the DSH plugin, have no reply (14 of 25). Keep a Changelog with semantic versioning declared and a 1.0 migration guide (15). Version 1.5.1 (15). Total 79.
- MemMachine (51): Local-software lines, as a server the owner runs. `memmachine-server` and `memmachine-client` on PyPI with Python versions stated, a Docker image and a compose script (20). pytest, integration and installation-test workflows exist, but GitHub's API answered with a rate limit, so run results were unread (15 of 25, unchecked). 292 open issues and pull requests; the newest bug reports, including a 429 from a provider surfacing as a 500 and a 0.4.0 configuration that no longer starts, have zero to two replies (10 of 25). No changelog file, release notes only on GitHub, which weren't read, and pre-1.0 tags (6 of 15). Version 0.4.0 (0). Total 51.

### Transparency & trust: EverOS +14

- 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.
- MemMachine (57): Apache-2.0 (30). The terms say hosted customer data is destroyed on termination, with no period, and use usage data only in aggregate; the privacy policy wasn't read (12 of 30). No deprecation policy or notices found (3 of 20). No telemetry calls found in the server or client source, and the docs don't address it (10 of 20). Total 55.

### Agent ergonomics: EverOS +13

- EverOS (78): Read for the API, with seven MCP tools on top. Searches take `top_k` and a method, and responses can be scoped by five ids (20 of 25). Filters nest with AND and OR, and `/get` pages results (18 of 20). Errors carry typed codes and say which are retryable (16 of 20). `add` is queued and returns 202, a busy session refuses deletion with nothing deleted, and the cloud purge needs a nonce confirmed within five minutes (12 of 20). A demo runs with no key and the minimal setup needs one OpenRouter key, with a Python library and the MCP server, one language (12 of 15). Total 78.
- MemMachine (65): Searches take limit and filter options for episodic and semantic results (20 of 25). Memories can be listed and filtered by scope (15 of 20). Validation errors are typed; other failures are less clear, as the 429-to-500 issue shows (10 of 20). No idempotency keys or safe-retry guidance found (5 of 20). Python and TypeScript clients and a five-line quick start, once the import is fixed (15). Total 65.

### Schema & documentation: EverOS +10

- 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.
- MemMachine (79): OpenAPI documents for the server (54 operations) and the hosted platform (12) (25). llms.txt on docs.memmachine.ai with Markdown pages (10). Every operation has a description, and the docs explain memory types and scoping (15 of 20). Typed request models generated from the server, with search options for limits and filters (12 of 15). Examples for each client and the MCP tools, but only 422 is documented on the server and the README's first example doesn't run (8 of 15). `/api/v2` paths and tagged releases, no changelog (9 of 15). Total 79.

### Security & auth: EverOS +6

- EverOS (47): Framework reading for software the owner runs. The local server has no authentication and no security scheme in the OpenAPI document, relying on a 127.0.0.1 bind by default (15 of 30). No read-only mode; the cloud purge is two-step (8 of 20). Memories are extracted from conversations and returned into prompts, and everos-mcp tells hosts to save facts unprompted, with no injection guidance found (4 of 15). Structured logs and lock metrics, no audit log (6 of 15). SECURITY.md with a reporting address, five-day acknowledgement, supported versions and a published-advisories section, plus a valid security.txt (14 of 20). Total 47.
- MemMachine (41): Framework reading for software the owner runs. The server has no authentication and no security scheme in its OpenAPI document (15 of 30). No read-only mode or confirmation for deletes (5 of 20). No guidance on recalled memories as untrusted text (4 of 15). No audit log on the self-hosted server; the hosted console shows usage (5 of 15). SECURITY.md with GitHub private reporting and a two-business-day acknowledgement, with security-audit and SBOM workflows; no security.txt or certification (12 of 20). Total 41.

## Score by category

| Category | Weight | EverOS | MemMachine | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 79 | 51 | EverOS +28 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 89 | 79 | EverOS +10 |
| Agent ergonomics | 13% (16.2 this run) | 78 | 65 | EverOS +13 |
| Security & auth | 14% (17.5 this run) | 47 | 41 | EverOS +6 |
| Payments & pricing | 10% (12.5 this run) | 40 | 40 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 80 | 83 | MemMachine +3 |
| Transparency & trust | 7% (8.8 this run) | 71 | 57 | EverOS +14 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **69.4 · B** | **58 · C** | |

## Facts side by side

| Fact | EverOS | MemMachine |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Evermind AI, Inc. | MemVerge, Inc. |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | HTTP, stdio | HTTP, stdio, Streamable HTTP |
| Auth | None | None |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 | Apache-2.0 |
| Tools exposed | 7 | 3 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-22 | 2026-10-08 |
| Terms last updated | 2026-01-20 | no date given |
| Privacy policy last updated | 2026-01-20 | 2026-05-20 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 14k stars, 4k PyPI/wk | 3.1k stars, 28 npm/wk, 581 PyPI/wk |

## Verdicts

**EverOS.** EverOS keeps agent and user memory as Markdown with SQLite and LanceDB indexes, behind a described OpenAPI with typed, retryable errors and an MCP server, under Apache-2.0 at version 1.5.1. The local server has no authentication, EverOS Cloud prices are not published, and the cloud terms forbid automated data extraction.

**MemMachine.** MemMachine is an Apache-2.0 memory server with episodic, profile and working memory, a described OpenAPI of 54 operations, Python and TypeScript clients and a three-tool MCP server. It is version 0.4.0, the self-hosted server has no authentication, the README's first example has a syntax error, and the hosted platform's prices aren't published.

## Before you call either

### EverOS

1. Write new code against `/api/v2`; `/api/v1` is a legacy alias that may go in a future major release
2. Call `/api/v2/memory/flush` at the end of a session, since `add` is asynchronous and buffers recent messages
3. Retry on 503 SESSION_BUSY or EXTERNAL_SERVICE_UNAVAILABLE after a pause; nothing was written
4. Keep `host` at 127.0.0.1 unless something in front adds authentication
5. Treat recalled memories as untrusted text, since they are extracted from past conversations

### MemMachine

1. Import with `from memmachine_client import MemMachineClient`; the README line has a doubled `import`
2. Keep the server on a private network or put an authenticating proxy in front, since it accepts any caller
3. Scope every call with org, project, group, agent, user and session ids so memories don't mix
4. Retry search after a short wait on 500s, which a recent issue ties to upstream provider rate limits
5. Treat recalled episodes as untrusted text from past conversations

## Questions

### Which is better for AI agents, EverOS or MemMachine?

EverOS scores 69.4 (B) on agent readiness against MemMachine's 58 (C), and leads in 5 of 7 scored categories.

### Do EverOS and MemMachine need an API key?

Neither needs a key.

### Can an agent call EverOS and MemMachine without installing anything?

EverOS runs on your own machine, with no hosted endpoint listed. MemMachine runs on your own machine, with no hosted endpoint listed.

### Are EverOS and MemMachine open source?

Yes. EverOS is open source (Apache-2.0). MemMachine is open source (Apache-2.0).


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/everos-vs-memmachine.json, and with the fewest tokens: https://www.anchorterminal.com/compare/everos-vs-memmachine.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "everos", "b": "memmachine"}`. From a terminal: `anchor compare everos memmachine`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/everos.json and https://www.anchorterminal.com/api/v1/tools/memmachine.json

## Other comparisons with EverOS or MemMachine

- [Amazon Bedrock AgentCore Memory vs EverOS](https://www.anchorterminal.com/compare/agentcore-memory-vs-everos.md)
- [Amazon Bedrock AgentCore Memory vs MemMachine](https://www.anchorterminal.com/compare/agentcore-memory-vs-memmachine.md)
- [Basic Memory vs EverOS](https://www.anchorterminal.com/compare/basic-memory-vs-everos.md)
- [Basic Memory vs MemMachine](https://www.anchorterminal.com/compare/basic-memory-vs-memmachine.md)
- [claude-mem vs EverOS](https://www.anchorterminal.com/compare/claude-mem-vs-everos.md)
- [claude-mem vs MemMachine](https://www.anchorterminal.com/compare/claude-mem-vs-memmachine.md)
- [Cognee vs EverOS](https://www.anchorterminal.com/compare/cognee-vs-everos.md)
- [Cognee vs MemMachine](https://www.anchorterminal.com/compare/cognee-vs-memmachine.md)
- [EverOS vs Agent Platform Memory Bank](https://www.anchorterminal.com/compare/everos-vs-google-memory-bank.md)
- [EverOS vs Graphicle](https://www.anchorterminal.com/compare/everos-vs-graphicle.md)
- [EverOS vs Graphiti](https://www.anchorterminal.com/compare/everos-vs-graphiti.md)
- [EverOS vs Hindsight](https://www.anchorterminal.com/compare/everos-vs-hindsight.md)
- [EverOS vs Honcho](https://www.anchorterminal.com/compare/everos-vs-honcho.md)
- [EverOS vs Hy Memory](https://www.anchorterminal.com/compare/everos-vs-hy-memory.md)
- [EverOS vs LangMem](https://www.anchorterminal.com/compare/everos-vs-langmem.md)
- [EverOS vs LocalGhost](https://www.anchorterminal.com/compare/everos-vs-localghost.md)
- [EverOS vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/everos-vs-mem0.md)
- [EverOS vs Memori](https://www.anchorterminal.com/compare/everos-vs-memori.md)
- [EverOS vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/everos-vs-memory-reference-server.md)
- [EverOS vs MemPalace](https://www.anchorterminal.com/compare/everos-vs-mempalace.md)
- [EverOS vs past.dev](https://www.anchorterminal.com/compare/everos-vs-past-dev.md)
- [EverOS vs Supermemory API + MCP](https://www.anchorterminal.com/compare/everos-vs-supermemory.md)
- [EverOS vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/everos-vs-tencentdb-agent-memory.md)
- [EverOS vs Tokenrip](https://www.anchorterminal.com/compare/everos-vs-tokenrip.md)
- [EverOS vs Zep](https://www.anchorterminal.com/compare/everos-vs-zep.md)
- [Agent Platform Memory Bank vs MemMachine](https://www.anchorterminal.com/compare/google-memory-bank-vs-memmachine.md)
- [Graphiti vs MemMachine](https://www.anchorterminal.com/compare/graphiti-vs-memmachine.md)
- [Hindsight vs MemMachine](https://www.anchorterminal.com/compare/hindsight-vs-memmachine.md)
- [Honcho vs MemMachine](https://www.anchorterminal.com/compare/honcho-vs-memmachine.md)
- [Hy Memory vs MemMachine](https://www.anchorterminal.com/compare/hy-memory-vs-memmachine.md)
- [LangMem vs MemMachine](https://www.anchorterminal.com/compare/langmem-vs-memmachine.md)
- [LocalGhost vs MemMachine](https://www.anchorterminal.com/compare/localghost-vs-memmachine.md)
- [Mem0 Platform + MCP vs MemMachine](https://www.anchorterminal.com/compare/mem0-vs-memmachine.md)
- [MemMachine vs Memori](https://www.anchorterminal.com/compare/memmachine-vs-memori.md)
- [MemMachine vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/memmachine-vs-memory-reference-server.md)
- [MemMachine vs MemPalace](https://www.anchorterminal.com/compare/memmachine-vs-mempalace.md)
- [MemMachine vs past.dev](https://www.anchorterminal.com/compare/memmachine-vs-past-dev.md)
- [MemMachine vs Supermemory API + MCP](https://www.anchorterminal.com/compare/memmachine-vs-supermemory.md)
- [MemMachine vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/memmachine-vs-tencentdb-agent-memory.md)
- [MemMachine vs Tokenrip](https://www.anchorterminal.com/compare/memmachine-vs-tokenrip.md)
- [MemMachine vs Zep](https://www.anchorterminal.com/compare/memmachine-vs-zep.md)
- [AI Memory vs EverOS](https://www.anchorterminal.com/compare/ai-memory-vs-everos.md)
- [AI Memory vs MemMachine](https://www.anchorterminal.com/compare/ai-memory-vs-memmachine.md)
- [Context Mode Engine vs EverOS](https://www.anchorterminal.com/compare/context-mode-vs-everos.md)
- [Context Mode Engine vs MemMachine](https://www.anchorterminal.com/compare/context-mode-vs-memmachine.md)
- [Graphicle vs MemMachine](https://www.anchorterminal.com/compare/graphicle-vs-memmachine.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp