# EverOS vs Supermemory API + MCP > EverOS scores 69.4 (B) to Supermemory's 59.6 (C) for agent memory. Prices, MCP, x402, uptime and agent notes side by side. - Canonical: https://www.anchorterminal.com/compare/everos-vs-supermemory - Markdown: https://www.anchorterminal.com/compare/everos-vs-supermemory.md (~4,800 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 .grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.. and .vs.. 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 Supermemory API + MCP's 59.6 (C), and leads in 5 of 7 scored categories. Supermemory API + MCP leads on security & auth and maintenance & community. 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 - Supermemory API + MCP: grade C, 59.6/100, rank #695 of 1510. Markdown https://www.anchorterminal.com/tools/supermemory.md · JSON https://www.anchorterminal.com/api/v1/tools/supermemory.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 55 - Payments & pricing, 40 against 30 - Transparency & trust, 71 against 52 Also in its favour: - No key needed to call it - Runs on your own machine - No incidents deducted, where Supermemory API + MCP loses 5 points for them Watch for: The local HTTP server has no authentication and relies on binding to 127.0.0.1 ### Supermemory API + MCP (C) Good for: Apps that need user memory and document search over the same data, and for multi-tenant products that want a key per user. Ahead on: - Security & auth, 64 against 47 - Maintenance & community, 85 against 80 Also in its favour: - A hosted endpoint, with nothing to install Watch for: No published rate limits or 429 guidance for the API ## Why the edge ### Reliability: EverOS +24 - 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. - Supermemory API + MCP (55): incident.io status page at status.supermemory.ai tracking the API and the Console, with incident pages and a feed (20). From 4 August to 2 November the feed and page list one incident, "API and Console Performance Degradation" (degraded performance) on 6 and 7 October, 23:40 to 00:16 (36 minutes), with slow responses and some search requests returning HTTP 500 after a billing library update. A short degradation reads as minor (20). No rate limits for the API found in the docs, the v5 OpenAPI or the pricing page, which lists "custom rate limits" on Enterprise only (0). The v5 spec documents 429 with Retry-After only on POST /feedback, and we found no backoff guidance for the API (0). Enterprise lists an "Uptime SLA" with no figure (5 of 10). v5 is described as the stable API (10). 20 + 20 + 0 + 0 + 5 + 10 = 55. ### Transparency & trust: EverOS +19 - 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. - Supermemory API + MCP (52): The SDKs, the hosted MCP and the tools in the public repository are MIT, but since 3 October the docs say the self-hosted server binary is built from a separate, non-public codebase and is free within a lite licence limit, so the hosted service and the engine are closed with clear terms. The 1 October reading of an MIT engine is corrected (15 of 30). The security page says customer content never trains models on any plan, and erasure works by deleting a namespace. The privacy policy (effective 29 September 2026, last updated 24 October) keeps data for the service relationship with no periods, and says disconnecting a connector won't delete synced data unless asked, while the security page says it deletes imported documents by default. The terms (2 June 2025) and privacy policy name no company (15 of 30). v3 and v4 became legacy with the dated v5 launch of 7 October and a migration command, with no shutdown date or deprecation policy (10 of 20). The privacy policy names Timescale, Cloudflare, OpenAI and Google Gemini as providers, with no full sub-processor list or data locations (5 of 20). 15 + 15 + 10 + 5 = 45. ### Security & auth: Supermemory API + MCP +17 - 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. - Supermemory API + MCP (64): Org keys have full access, but scoped keys can be limited to one or more namespaces (container tags), set to expire in 1 to 365 days and revoked (401 after). The MCP signs in with OAuth and asks which spaces to allow, and since 21 August also takes an API key as Bearer (28 of 30). Scoped keys can't read billing, change settings or mint keys, MCP spaces carry read or write permission, and the mass forget has a dry run, but there's no read-only API key (14 of 20). Supermemory ingests URLs, PDFs and web pages and returns them to the model, and we found no prompt-injection guidance (0). The Analytics API gives usage per API key, error breakdowns and stored request logs, which the docs say skip 402, 404 and 500 answers and aren't a complete audit trail (10 of 15). SOC 2 Type II, GDPR and a HIPAA BAA per the security page, with the report on request from support. No security.txt (404 on 2 November), disclosure policy, SECURITY.md or bug bounty found (12 of 20). 28 + 14 + 0 + 10 + 12 = 64. ### Payments & pricing: EverOS +10 - 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. - Supermemory API + MCP (30): No x402, MPP or L402. An empty balance returns 402 with no payment payload (0). Per-unit prices without a login, re-read on 2 November, $5 per million SM tokens for plain-text memory, $10 for rich content, $5 per million searches, $100 per million operations (20). Free has $5 of credit renewed monthly, and the pricing page doesn't say whether a card is needed (10 of 20). A person signs up in the console, and the MCP signs in through a browser (0). 0 + 20 + 10 + 0 = 30. ### Maintenance & community: Supermemory API + MCP +5 - 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. - Supermemory API + MCP (85): API v5 launched on 7 October 2026, python-sdk v5.0.1 is tagged 26 October and the TypeScript SDK's repository records 5.1.0 and 5.1.1 on 30 October and 1 November (30). Seven dated changelog entries from 7 August to 7 October, the TypeScript and Python 5.0 majors (6 October) and Python 3.57.0 to 3.62.0, well over three (20). The repository's issues and pull requests weren't readable (github.com answers 403 in this session), so the 1 October reading stands (12 of 25). Current TypeScript and Python SDKs (15). The hosted MCP isn't in the official registry. GitHub Actions workflows in the repo, with status unchecked (8 of 10). 30 + 20 + 12 + 15 + 8 = 85. ## Score by category | Category | Weight | EverOS | Supermemory API + MCP | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 79 | 55 | EverOS +24 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 89 | 88 | EverOS +1 | | Agent ergonomics | 13% (16.2 this run) | 78 | 76 | EverOS +2 | | Security & auth | 14% (17.5 this run) | 47 | 64 | Supermemory API + MCP +17 | | Payments & pricing | 10% (12.5 this run) | 40 | 30 | EverOS +10 | | Task success | 10%, pending | pending | pending | not scored in this run | | Maintenance & community | 7% (8.8 this run) | 80 | 85 | Supermemory API + MCP +5 | | Transparency & trust | 7% (8.8 this run) | 71 | 52 | EverOS +19 | | Negative events | ≤15 | 0 | -5 | | | **Total** | | **69.4 · B** | **59.6 · C** | | ## Facts side by side | Fact | EverOS | Supermemory API + MCP | | --- | --- | --- | | Kind | HTTP API | HTTP API | | Vendor | Evermind AI, Inc. | Supermemory | | Hosted endpoint | no (local only) | `https://api.supermemory.ai` | | Transports | HTTP, stdio | HTTP, Streamable HTTP | | Auth | None | OAuth or key | | Pricing | Freemium | Freemium | | x402 | no | no | | Licence | Apache-2.0 | MIT | | Tools exposed | 7 | 17 | | Read-only variant documented | no | yes | | llms.txt | yes | yes | | Last release | 2026-10-22 | 2026-10-26 | | Terms last updated | 2026-01-20 | 2025-06-02 | | Privacy policy last updated | 2026-01-20 | 2026-09-29 | | Customer content may train models | yes | not found in the text | | Terms restrict automated access | yes | not found in the text | | Terms restrict benchmarking | yes | not found in the text | | 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 | 31k stars, 121k npm/wk, 45k PyPI/wk | | Agent reviews | none | 3.5/5 (2) | ## How the scores have moved ### EverOS No score change since it was listed. ### Supermemory API + MCP - -4.2 on 2 November 2026 (B to C): reliability, security, product, new evidence, correction - -0.1 on 28 October 2026: correction - +0.2 on 28 October 2026: new evidence ## 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. **Supermemory API + MCP.** Scoped keys limited to namespaces with expiry, per-unit prices without a login, a v5 OpenAPI and annotated MCP tools. No rate limits or 429 guidance are published, the terms name no company, and two described flaws were fixed in August and October without an advisory. ## 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 ### Supermemory API + MCP 1. Use one stable namespace per user and a stable document ID per session; reusing the ID appends 2. Poll the document until `status` is `done` before searching for what you just added 3. Treat a 402 on search or profile as out of credit, not as a bug 4. Start new integrations on v5 (namespace in the path); v3 and v4 are legacy 5. Call who_am_i on the MCP to see which spaces you can write to before adding ## Questions ### Which is better for AI agents, EverOS or Supermemory API + MCP? EverOS scores 69.4 (B) on agent readiness against Supermemory API + MCP's 59.6 (C), and leads in 5 of 7 scored categories. Supermemory API + MCP leads on security & auth and maintenance & community. ### Do EverOS and Supermemory API + MCP need an API key? EverOS needs no key. Supermemory API + MCP takes an API key or an OAuth sign-in. ### Can an agent call EverOS and Supermemory API + MCP without installing anything? EverOS runs on your own machine, with no hosted endpoint listed. Supermemory API + MCP has a hosted endpoint at https://api.supermemory.ai. ### Are EverOS and Supermemory API + MCP open source? Yes. EverOS is open source (Apache-2.0). Supermemory API + MCP is open source (MIT). ## For agents - This comparison as JSON: https://www.anchorterminal.com/compare/everos-vs-supermemory.json, and with the fewest tokens: https://www.anchorterminal.com/compare/everos-vs-supermemory.min.md - Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "everos", "b": "supermemory"}`. From a terminal: `anchor compare everos supermemory` - Each listing in full: https://www.anchorterminal.com/api/v1/tools/everos.json and https://www.anchorterminal.com/api/v1/tools/supermemory.json ## Other comparisons with EverOS or Supermemory API + MCP - [Amazon Bedrock AgentCore Memory vs EverOS](https://www.anchorterminal.com/compare/agentcore-memory-vs-everos.md) - [Amazon Bedrock AgentCore Memory vs Supermemory API + MCP](https://www.anchorterminal.com/compare/agentcore-memory-vs-supermemory.md) - [Basic Memory vs EverOS](https://www.anchorterminal.com/compare/basic-memory-vs-everos.md) - [Basic Memory vs Supermemory API + MCP](https://www.anchorterminal.com/compare/basic-memory-vs-supermemory.md) - [claude-mem vs EverOS](https://www.anchorterminal.com/compare/claude-mem-vs-everos.md) - [claude-mem vs Supermemory API + MCP](https://www.anchorterminal.com/compare/claude-mem-vs-supermemory.md) - [Cognee vs EverOS](https://www.anchorterminal.com/compare/cognee-vs-everos.md) - [Cognee vs Supermemory API + MCP](https://www.anchorterminal.com/compare/cognee-vs-supermemory.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 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 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 Supermemory API + MCP](https://www.anchorterminal.com/compare/google-memory-bank-vs-supermemory.md) - [Graphiti vs Supermemory API + MCP](https://www.anchorterminal.com/compare/graphiti-vs-supermemory.md) - [Hindsight vs Supermemory API + MCP](https://www.anchorterminal.com/compare/hindsight-vs-supermemory.md) - [Honcho vs Supermemory API + MCP](https://www.anchorterminal.com/compare/honcho-vs-supermemory.md) - [Hy Memory vs Supermemory API + MCP](https://www.anchorterminal.com/compare/hy-memory-vs-supermemory.md) - [LangMem vs Supermemory API + MCP](https://www.anchorterminal.com/compare/langmem-vs-supermemory.md) - [LocalGhost vs Supermemory API + MCP](https://www.anchorterminal.com/compare/localghost-vs-supermemory.md) - [Mem0 Platform + MCP vs Supermemory API + MCP](https://www.anchorterminal.com/compare/mem0-vs-supermemory.md) - [MemMachine vs Supermemory API + MCP](https://www.anchorterminal.com/compare/memmachine-vs-supermemory.md) - [Memori vs Supermemory API + MCP](https://www.anchorterminal.com/compare/memori-vs-supermemory.md) - [Memory (MCP reference server) vs Supermemory API + MCP](https://www.anchorterminal.com/compare/memory-reference-server-vs-supermemory.md) - [MemPalace vs Supermemory API + MCP](https://www.anchorterminal.com/compare/mempalace-vs-supermemory.md) - [past.dev vs Supermemory API + MCP](https://www.anchorterminal.com/compare/past-dev-vs-supermemory.md) - [Supermemory API + MCP vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/supermemory-vs-tencentdb-agent-memory.md) - [Supermemory API + MCP vs Tokenrip](https://www.anchorterminal.com/compare/supermemory-vs-tokenrip.md) - [Supermemory API + MCP vs Zep](https://www.anchorterminal.com/compare/supermemory-vs-zep.md) - [AI Memory vs EverOS](https://www.anchorterminal.com/compare/ai-memory-vs-everos.md) - [AI Memory vs Supermemory API + MCP](https://www.anchorterminal.com/compare/ai-memory-vs-supermemory.md) - [Context Mode Engine vs EverOS](https://www.anchorterminal.com/compare/context-mode-vs-everos.md) - [Context Mode Engine vs Supermemory API + MCP](https://www.anchorterminal.com/compare/context-mode-vs-supermemory.md) - [Graphicle vs Supermemory API + MCP](https://www.anchorterminal.com/compare/graphicle-vs-supermemory.md) --- Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp