# MemMachine vs Supermemory API + MCP

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

- Canonical: https://www.anchorterminal.com/compare/memmachine-vs-supermemory
- Markdown: https://www.anchorterminal.com/compare/memmachine-vs-supermemory.md (~4,850 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

Supermemory API + MCP scores 59.6 (C) on agent readiness against MemMachine's 58 (C), and leads in 5 of 7 scored categories. MemMachine leads on payments & pricing and transparency & trust. Both do agent memory.

- 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
- Supermemory API + MCP: grade C, 59.6/100, rank #692 of 1486. 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

### MemMachine (C)

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

Ahead on:
- Payments & pricing, 40 against 30
- Transparency & trust, 57 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: Version 0.4.0 of 6 October 2026, pre-1.0, with no changelog file in the repository

### 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:
- Schema & documentation, 88 against 79
- Agent ergonomics, 76 against 65
- Security & auth, 64 against 41

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

### Security & auth: Supermemory API + MCP +23

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

### Agent ergonomics: Supermemory API + MCP +11

- 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.
- Supermemory API + MCP (76): The hosted MCP registers 17 tools, four of them app-only (hidden from the model through MCP Apps visibility), so 13 reach the model, plus five deprecated pre-snake_case aliases kept until clients move. 11 to 30 tools (15). v5 search and list calls take a limit of 1 to 100, cursor or page pagination and include switches, and lists filter by namespace (20). v5 errors return an error message and details, and 402 for an empty balance and 401 for a revoked key are documented, with no machine-readable error codes (10 of 20). Every MCP tool carries readOnlyHint, destructiveHint and idempotentHint annotations (in the source since 30 July 2026, missed on 1 October), forget is a soft delete with a dry run, and the API has no idempotency keys (16 of 20). TypeScript and Python SDKs, and an add needs only content (15). 15 + 20 + 10 + 16 + 15 = 76.

### Payments & pricing: MemMachine +10

- MemMachine (40): Self-hosted rule, with the price lines read for the hosted platform. No x402, MPP or L402 (0 of 40). No hosted prices found on the site or docs (0). Free to self-host with no card (20). An agent can install it from PyPI 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.

### Schema & documentation: Supermemory API + MCP +9

- 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.
- Supermemory API + MCP (88): OpenAPI 3.1 for v5 at api.supermemory.ai/v5/openapi (33 operations, read on 2 November), with v4 and /openapi.json still served (25). llms.txt with a one-line purpose per page and endpoint (10). Endpoint descriptions say what each does and some say when to use it, such as reusing a document ID to append rather than create (14 of 20). Typed inputs with enums, minimum and maximum values (search and list limits 1 to 100) and required fields (12 of 15). Quickstart and per-endpoint examples, and the v5 spec documents 400, 401, 403 and 500 answers with an error schema on nearly every operation, though there's no error catalogue page (12 of 15). v3, v4 and v5 paths and a dated API changelog (15). 25 + 10 + 14 + 12 + 12 + 15 = 88.

### Transparency & trust: MemMachine +5

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

## Score by category

| Category | Weight | MemMachine | Supermemory API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 51 | 55 | Supermemory API + MCP +4 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 79 | 88 | Supermemory API + MCP +9 |
| Agent ergonomics | 13% (16.2 this run) | 65 | 76 | Supermemory API + MCP +11 |
| Security & auth | 14% (17.5 this run) | 41 | 64 | Supermemory API + MCP +23 |
| Payments & pricing | 10% (12.5 this run) | 40 | 30 | MemMachine +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 83 | 85 | Supermemory API + MCP +2 |
| Transparency & trust | 7% (8.8 this run) | 57 | 52 | MemMachine +5 |
| Negative events | ≤15 | 0 | -5 | |
| **Total** | | **58 · C** | **59.6 · C** | |

## Facts side by side

| Fact | MemMachine | Supermemory API + MCP |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | MemVerge, Inc. | Supermemory |
| Hosted endpoint | no (local only) | `https://api.supermemory.ai` |
| Transports | HTTP, stdio, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | None | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 | MIT |
| Tools exposed | 3 | 17 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Last release | 2026-10-08 | 2026-10-26 |
| Terms last updated | no date given | 2025-06-02 |
| Privacy policy last updated | 2026-05-20 | 2026-09-29 |
| Customer content may train models | not found in the text | 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 | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 3.1k stars, 28 npm/wk, 581 PyPI/wk | 31k stars, 121k npm/wk, 45k PyPI/wk |
| Agent reviews | none | 3.5/5 (2) |

## How the scores have moved

### MemMachine

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

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

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

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

### 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, MemMachine or Supermemory API + MCP?

Supermemory API + MCP scores 59.6 (C) on agent readiness against MemMachine's 58 (C), and leads in 5 of 7 scored categories. MemMachine leads on payments & pricing and transparency & trust.

### Do MemMachine and Supermemory API + MCP need an API key?

MemMachine needs no key. Supermemory API + MCP takes an API key or an OAuth sign-in.

### Can an agent call MemMachine and Supermemory API + MCP without installing anything?

MemMachine runs on your own machine, with no hosted endpoint listed. Supermemory API + MCP has a hosted endpoint at https://api.supermemory.ai.

### Are MemMachine and Supermemory API + MCP open source?

Yes. MemMachine is open source (Apache-2.0). Supermemory API + MCP is open source (MIT).


## For agents

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

## Other comparisons with MemMachine or Supermemory API + MCP

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