# EverOS vs MemPalace (slim)

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

- Full: https://www.anchorterminal.com/compare/everos-vs-mempalace.md (~4,250 tokens) · this version ~1,930 tokens · JSON https://www.anchorterminal.com/compare/everos-vs-mempalace.json · canonical https://www.anchorterminal.com/compare/everos-vs-mempalace
- 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 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: B 69.4, rank #247 of 1510 · https://www.anchorterminal.com/tools/everos.min.md
- MemPalace: C 60.7, rank #646 of 1510 · https://www.anchorterminal.com/tools/mempalace.min.md
- 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 Maintenance & community, 80 against 74; Transparency & trust, 71 against 58. Also No incidents deducted, where MemPalace loses 9 points for them.
- MemPalace, good for Verbatim, local, searchable memory of coding-agent sessions Ahead on Security & auth, 53 against 47; Payments & pricing, 60 against 40. Also Free to start without a card.

| Category | EverOS | MemPalace |
| --- | --- | --- |
| Reliability (16%) | 79 | 77 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 89 | 85 |
| Agent ergonomics (13%) | 78 | 75 |
| Security & auth (14%) | 47 | 53 |
| Payments & pricing (10%) | 40 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 80 | 74 |
| Transparency & trust (7%) | 71 | 58 |

| Fact (where they differ) | EverOS | MemPalace |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Evermind AI, Inc. | MemPalace (open-source project) |
| Transports | HTTP, stdio | stdio, Streamable HTTP |
| Pricing | Freemium | Free |
| 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 |

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