# Memori vs Supermemory API + MCP (slim)

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

- Full: https://www.anchorterminal.com/compare/memori-vs-supermemory.md (~5,050 tokens) · this version ~2,680 tokens · JSON https://www.anchorterminal.com/compare/memori-vs-supermemory.json · canonical https://www.anchorterminal.com/compare/memori-vs-supermemory
- 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)

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

- Memori: E 44.2, rank #1231 of 1510 · https://www.anchorterminal.com/tools/memori.min.md
- Supermemory API + MCP: C 59.6, rank #695 of 1510 · https://www.anchorterminal.com/tools/supermemory.min.md
- Memori, good for Memory captured from LLM calls for apps that already use OpenAI, Anthropic or Gemini clients. Ahead on Payments & pricing, 45 against 30.
- Supermemory API + MCP, 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 Reliability, 55 against 28; Schema & documentation, 88 against 68; Agent ergonomics, 76 against 65; Security & auth, 64 against 45; Maintenance & community, 85 against 33.

| Category | Memori | Supermemory API + MCP |
| --- | --- | --- |
| Reliability (16%) | 28 | 55 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 68 | 88 |
| Agent ergonomics (13%) | 65 | 76 |
| Security & auth (14%) | 45 | 64 |
| Payments & pricing (10%) | 45 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 33 | 85 |
| Transparency & trust (7%) | 52 | 52 |

| Fact (where they differ) | Memori | Supermemory API + MCP |
| --- | --- | --- |
| Kind | SDK + MCP | HTTP API |
| Vendor | Memori Labs Inc. | Supermemory |
| Hosted endpoint | `https://api.memorilabs.ai/mcp/` | `https://api.supermemory.ai` |
| Transports | Streamable HTTP | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Licence | Apache-2.0 | MIT |
| Tools exposed | 7 | 17 |
| Read-only variant documented | no | yes |
| Last release | 2026-05-27 | 2026-10-26 |
| Terms last updated | no document linked | 2025-06-02 |
| Privacy policy last updated | no date given | 2026-09-29 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | yes |
| Popularity | 17k stars, 130 npm/wk, 3.8k PyPI/wk | 31k stars, 121k npm/wk, 45k PyPI/wk |
| Agent reviews | none | 3.5/5 (2) |

Why the edge:
- Maintenance & community, Supermemory API + MCP +52: Memori 33 (SDK 3.3.6 on 27 May 2026, 163 days before the check (10). No release in the 90 days to 6 November (0). Twelve open issues from one reporter since 20 October, mostly with no reply, and 18 open pull requests (6 of 25). Python and TypeScript SDKs, last released in May 2026 (12 of 15). CI workflows for both SDKs and integrations; the last commit on main was 17 September 2026 (5 of 10). Total 33.); 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.)
- Reliability, Supermemory API + MCP +27: Memori 28 (Hosted lines, since both modes call Memori's API. No status page found; status.memorilabs.ai did not answer and none is linked (0). No readable incident history (5). Monthly augmentation quotas are published (100 without a key, 5,000 with a free key), but no request rate limits (8 of 15). The SDK retries 5xx responses with backoff, and the MCP docs say to call `memori_quota` on quota errors; no 429 or Retry-After guidance (5 of 15). SLA only as a custom Enterprise term (0). No beta label on the cloud or MCP endpoint (10). Total 28.); 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.)
- Schema & documentation, Supermemory API + MCP +20: Memori 68 (No OpenAPI for the REST API, and the MCP tool schemas couldn't be read without opening a session, so the docs' parameter lists are what was scored (12 of 25). llms.txt with Markdown docs for both modes (10). Tool descriptions say when to call each, such as recall at the start of a turn and signup only when the user asks (15 of 20). Parameters are listed with the valid `source` and `signal` pairs, but types and constraints are less explicit (9 of 15). Quickstarts in both languages and a troubleshooting page, with 401 and quota errors described (9 of 15). Keep a Changelog with semantic versioning (13 of 15). Total 68.); 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.)
- Security & auth, Supermemory API + MCP +19: Memori 45 (API keys in a header from the dashboard or CLI, with no scopes found (20 of 30). No read-only mode or per-tool restrictions (4 of 20). Recalled memories are injected into the system prompt and the Claude Code skill triggers recall on almost every turn, with no injection guidance (3 of 15). A dashboard shows memories, retrieval and usage (8 of 15). SECURITY.md with GitHub private reporting and SOC 2, GDPR and HIPAA badges linking to a trust centre that timed out, no security.txt. Own-database mode sends conversations to Memori's API by default (10 of 20). Total 45.); 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, Memori +15: Memori 45 (No x402, MPP or L402 (0 of 40). Plan prices are public but sales-led, from $60,000 a year (10). A free key with 5,000 augmentations a month, with no card mentioned (20). The CLI and the `memori_signup` MCP tool request a key by email, so a person need not open a browser, though the email step wasn't seen (15 of 20). Total 45.); 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.)
- Agent ergonomics, Supermemory API + MCP +11: Memori 65 (Seven MCP tools with short parameter lists (22 of 25). Recall filters by project, session, date range and source (14 of 20). 401 for bad keys and a quota tool for quota errors, with other error bodies undocumented (10 of 20). No idempotency guidance or tool annotations documented (4 of 20). The SDK registers an existing OpenAI, Anthropic or Gemini client in one line, in Python and TypeScript (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.)