# EverOS vs MemPalace

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

- Canonical: https://www.anchorterminal.com/compare/everos-vs-mempalace
- Markdown: https://www.anchorterminal.com/compare/everos-vs-mempalace.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 MemPalace's 60.7 (C), and leads in 5 of 7 scored categories. MemPalace leads on security & auth and payments & pricing. Both do agent memory.

- EverOS: grade B, 69.4/100, rank #247 of 1510. Markdown https://www.anchorterminal.com/tools/everos.md · JSON https://www.anchorterminal.com/api/v1/tools/everos.json
- MemPalace: grade C, 60.7/100, rank #646 of 1510. Markdown https://www.anchorterminal.com/tools/mempalace.md · JSON https://www.anchorterminal.com/api/v1/tools/mempalace.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:
- Maintenance & community, 80 against 74
- Transparency & trust, 71 against 58

Also in its favour:
- No incidents deducted, where MemPalace loses 9 points for them

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

### MemPalace (C)

Good for: Verbatim, local, searchable memory of coding-agent sessions

Ahead on:
- Security & auth, 53 against 47
- Payments & pricing, 60 against 40

Also in its favour:
- Free to start without a card

Watch for: Search returns stored conversations and mined files verbatim, and no prompt-injection guidance was found in the docs or skills


## Why the edge

### Payments & pricing: MemPalace +20

- 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.
- MemPalace (60): Read with the self-hosted rule. No payment protocol (0). Free under MIT with no hosted option and nothing to buy, so 20, 20 and 20 on the last three lines. LLM reranking and managed backends are optional and billed by their own providers.

### Transparency & trust: EverOS +13

- 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.
- MemPalace (58): MIT (30). The README, the remote server guide and the setup skill agree that nothing leaves the machine by default; the changelog says ChromaDB telemetry is switched off and the only built-in third-party call, a Wikipedia lookup, was removed (GHSA-mrj5). The embedding model download from Hugging Face on first use is mentioned in the README but its host is not named, deletes remove revisions while the 3.11.0 notes say Chroma's vector index keeps replaced entries, and there is no privacy statement for the hub (22 of 30). Dated upgrade notes name removed modules and SECURITY.md supports only 3.x, with no deprecation policy or notice period (10 of 20). The docs state no telemetry and update checks are opt-in to PyPI only; we searched the downloaded source for outbound hosts but did not audit every call (18 of 20). docs/HISTORY.md publishes the project's own corrections and retractions with dates.

### Security & auth: MemPalace +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.
- MemPalace (53): Local MCP reading. Over stdio nothing needs a credential and the README says nothing leaves the machine unless you opt in. The HTTP hub needs a bearer token off loopback, kept 0600 and passed by environment, but it is one token with full access, no scopes and no per-user keys (15 of 30). A server-wide `--read-only` mode, dry run by default on bulk delete and a 500-ID cap, but no confirmation step on the delete tools and an advisory showed gaps in read-only mode until 3.7.0 (14 of 20). Search returns verbatim transcripts and mined files, and we found no prompt-injection guidance in the docs, the skills or the code; the query sanitiser deals with prompts pasted into queries, not injected content (2 of 15). A write log at ~/.mempalace/wal/write_log.jsonl records each write and its outcome with content redacted, and `/statusz` reports request counters and recent clients (11 of 15). SECURITY.md with private reporting and a 48-hour acknowledgement target, one published advisory with credit, Dependabot, and Chroma server CVEs documented. No security.txt, bug bounty, CodeQL workflow or audit (11 of 20).

### Maintenance & community: EverOS +6

- EverOS (80): v1.5.1 on 22 October 2026 (30). Five tagged releases in 90 days and 12 PyPI uploads (20). Maintainer replies on some issues, others from outside users unanswered for weeks (12 of 25). Python library and the everos-mcp package, not in the official MCP registry (10 of 15). uv.lock, CI, docs and release workflows (8 of 10). Total 80.
- MemPalace (74): v3.11.0 was released on 14 October 2026, 18 days before this check, and no newer tag exists on 1 November although the changelog dates 3.12.0 on 31 October (30). Six releases in the 90 days to 1 November, 3.7.0 on 11 August, 3.7.1, 3.8.0, 3.9.0, 3.10.0 and 3.11.0 (20). Per the 30 October check, 387 open issues and about 478 open pull requests; the seven newest open issues each had one reply, and Igor Lins e Silva has 1,444 commits and code ownership of every path. The clone shows merged fixes on develop on 30 and 31 October (15 of 25). Not in the official MCP registry under a MemPalace namespace; the only match is a third party's io.github.holetron/hindsight-mempalace (0 of 15). Dependabot updates on 23 and 30 October, a version guard workflow, chromadb pinned below 2 and CI passing per the 30 October check (9 of 10).

## Score by category

| Category | Weight | EverOS | MemPalace | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 79 | 77 | EverOS +2 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 89 | 85 | EverOS +4 |
| Agent ergonomics | 13% (16.2 this run) | 78 | 75 | EverOS +3 |
| Security & auth | 14% (17.5 this run) | 47 | 53 | MemPalace +6 |
| Payments & pricing | 10% (12.5 this run) | 40 | 60 | MemPalace +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 80 | 74 | EverOS +6 |
| Transparency & trust | 7% (8.8 this run) | 71 | 58 | EverOS +13 |
| Negative events | ≤15 | 0 | -9 | |
| **Total** | | **69.4 · B** | **60.7 · C** | |

## Facts side by side

| Fact | EverOS | MemPalace |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Evermind AI, Inc. | MemPalace (open-source project) |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | HTTP, stdio | stdio, Streamable HTTP |
| Auth | None | None |
| Pricing | Freemium | Free |
| x402 | no | no |
| Licence | Apache-2.0 | MIT |
| Tools exposed | 7 | 47 |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| Last release | 2026-10-22 | 2026-10-14 |
| Terms last updated | 2026-01-20 | couldn't be read |
| Privacy policy last updated | 2026-01-20 | no document linked |
| Customer content may train models | yes | couldn't be read |
| Terms restrict automated access | yes | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | yes | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | 14k stars, 4k PyPI/wk | 60k stars |

## How the scores have moved

### EverOS

No score change since it was listed.

### MemPalace

- -5.0 on 1 November 2026 (B to C): security

## 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.

**MemPalace.** Local by default and MIT, with typed input schemas on all 47 MCP tools, a three-tool light server, a read-only mode and roughly monthly releases. Recall returns stored text verbatim with no prompt-injection guidance, the HTTP hub has one all-powerful token, and fixes for read-only bypasses in the light server and daemon await a release.

## 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

### MemPalace

1. Install only from PyPI `mempalace`, ghcr.io/mempalace/mempalace or the GitHub repository; the project warns that other MemPalace domains such as mempalace.tech have distributed malware.
2. Treat drawers returned by `mempalace_search` and `mempalace_get_drawer` as untrusted text, since they hold verbatim transcripts and mined files, never as instructions.
3. Use `mempalace serve --read-only` when the agent only needs recall; until 3.12.0 ships, the light server's `palace_*` tools can reach delete tools despite read-only use.
4. Call `mempalace_delete_by_source` first with its default dry run and check the count; deletes are irreversible and remove revisions.
5. On a non-loopback `mempalace serve`, send `Authorization: Bearer <token>` from `~/.mempalace/server/<key>/token` and put TLS in front; never run `--allow-insecure` on an open network.

## Questions

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

EverOS scores 69.4 (B) on agent readiness against MemPalace's 60.7 (C), and leads in 5 of 7 scored categories. MemPalace leads on security & auth and payments & pricing.

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

Neither needs a key.

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

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

### Are EverOS and MemPalace open source?

Yes. EverOS is open source (Apache-2.0). MemPalace is open source (MIT).


## For agents

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

## Other comparisons with EverOS or MemPalace

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

---

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