{ "data": { "a": { "slug": "mem0", "name": "Mem0 Platform + MCP", "vendor": "Mem0", "vendorUrl": "https://mem0.ai", "kind": "http-api", "category": "agent-memory", "summary": "Hosted memory layer that extracts facts from conversations and returns the relevant ones for a user, agent or run on later turns.", "url": "https://www.anchorterminal.com/tools/mem0", "markdownUrl": "https://www.anchorterminal.com/tools/mem0.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/mem0.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/mem0.json", "dns": "mem0.grade.anchorterminal.com", "repo": "https://github.com/mem0ai/mem0", "license": "Apache-2.0", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.mem0.ai", "packages": [ { "registry": "pypi", "name": "mem0ai" }, { "registry": "npm", "name": "mem0ai" } ], "auth": "api-key", "authNotes": "API key in the `Authorization: Token \u003ckey\u003e` header on the REST API, not Bearer. The hosted MCP at mcp.mem0.ai/mcp signs in through the browser by default, and headless clients pass the API key as a Bearer token. `mem0 init --agent` creates an unclaimed Free account with no email, limited to 5 sign-ups a day per IP address.", "pricing": "freemium", "pricingNotes": "Free plan with no card. For the first 30 days Mem0 pays for the model calls, with 10,000 adds and 1,000 retrievals a month. After that, adds need the customer's own OpenAI, Anthropic, Azure OpenAI or OpenRouter key, and the limits rise to 50,000 adds and 10,000 retrievals a month. Accounts made before 26 October 2026 have until 25 November 2026. Starter, Growth and Pro are no longer sold to new accounts. Above the free limits, usage-based billing at a rate shown in the dashboard, with a monthly cap, or a custom Enterprise plan (https://github.com/mem0ai/mem0/blob/main/docs/platform/pricing.mdx, 26 October 2026).", "priceSummary": "Freemium", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": 11, "popularity": { "githubStars": 65900, "npmWeekly": 167841, "pypiWeekly": 501642, "asOf": "2026-09-30" }, "docsUrl": "https://docs.mem0.ai", "llmsTxt": "https://mem0.ai/llms.txt", "openapi": "https://docs.mem0.ai/openapi.json", "registryName": "io.github.mem0ai/mem0", "capabilities": [ "memory.store", "memory.search", "memory.graph", "memory.user", "memory.delete" ], "tags": [ "hosted", "freemium", "free-tier", "no-card", "mcp", "llms-txt", "openapi", "python", "typescript", "open-source", "self-hosted", "enterprise" ], "lastRelease": "2026-09-25", "graded": true, "anchor": { "graded": true, "score": 40.1, "grade": "E", "agentReady": false, "rank": 1310, "ranked": true, "rankOf": 1486, "categoryRank": 26, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 63, "maintenance": 75, "payments": 40, "reliability": 25, "schema": 80, "security": 45, "transparency": 62 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": -13, "negativeNotes": [ "-1, GHSA-5324-3w58-qpp2 (CVE-2026-116575), Moderate, published by Mem0 on 28 October 2026. A crafted run_id could collide with another tenant's session-scope key in the open-source library and read that tenant's recent messages. Fixed in Python 2.0.18 and TypeScript 3.1.6 on 12 August 2026 (https://osv.dev/vulnerability/GHSA-5324-3w58-qpp2).", "-2, GHSA-7587-9684-52r6 (CVE-2026-115324), Critical, published 22 October 2026 from a VulnCheck record. SQL injection through stored memory text in the Databricks vector store, fixed in 1.0.8. Under two months old, so 2; it falls to 1 after 22 December 2026 (https://osv.dev/vulnerability/GHSA-7587-9684-52r6).", "-1, GHSA-jfv9-68m5-gjjr (CVE-2026-31240), High, published 12 May 2026 by a third party. The self-hosted server up to 1.0.0 had no authentication on memory update and delete. OSV lists no fixed version, but the server has required a JWT or API key unless AUTH_DISABLED is set since 5 June 2026 (first released in 2.0.8 on 24 June), so it is read as fixed. Over two months old, so 1. Its two Medium companions (GHSA-cgx8-qgvr-f7vf, GHSA-gq6f-qwv9-rf4j) cost 0 and the fixed Low GHSA-xqxw-r767-67m7 costs nothing (https://osv.dev/list?q=mem0ai\u0026ecosystem=PyPI).", "-3, a breaking change without notice. Python 2.0.19 (24 August 2026), a patch release, stopped `mem0.proxy` installing `litellm` when it is missing and raises ImportError instead. litellm is only in the optional `llms` extra, and the OpenAI compatibility guide's managed-proxy example doesn't say to install it, so callers who followed it fail at import (https://github.com/mem0ai/mem0/blob/main/docs/changelog/sdk.mdx).", "-3, released fixes of described flaws with no advisory. v2.0.12 (13 July 2026) shipped \"security: fix SQL and Cypher injection vulnerabilities in PGVector, Azure MySQL, and Neptune\" (d1224796) and filter-injection fixes for Elasticsearch, OpenSearch, Neptune, Azure AI Search, Valkey, Milvus, MongoDB and Upstash ran from 22 June to 4 August. v2.0.13 and v2.0.16 stopped metadata from moving a memory into another tenant's scope. OSV holds no record for any of them (https://github.com/mem0ai/mem0/blob/main/docs/changelog/sdk.mdx).", "-3, security fixes on main in no release. d62ce07f (7 October 2026) stops the Vertex AI vector store writing the service account private key to DEBUG logs, and d26ba5e4 (12 October) makes the SDKs refuse an empty entity ID, which the docs say \"matches every memory in the project\" on delete_all. The newest release is still 2.2.1 of 25 September (https://github.com/mem0ai/mem0/commit/d62ce07faceafedd4b10d60704db2b9d89d0afff)." ], "verdict": "An agent can create its own free account with `mem0 init --agent`, no email and no card, and free limits rise to 50,000 adds a month with the customer's own LLM key. Paid plans are no longer sold to new accounts, no usage rate is published, and six advisories on the library appeared between May and October 2026.", "bestFor": "Chat products that want per-user facts back with one search call and little setup, and teams willing to connect their own LLM key for higher free limits.", "strengths": [ "An agent can create its own free account with `mem0 init --agent`, no email and no card", "Hosted MCP server with 11 tools, listed in the official MCP registry as io.github.mem0ai/mem0", "OpenAPI file with 47 paths, llms.txt, and Python and TypeScript SDKs, with six Python releases between 12 August and 25 September 2026", "The free plan gives 50,000 adds and 10,000 retrievals a month once the customer connects its own LLM key", "Apache-2.0 library that runs the same extraction on your own servers" ], "weaknesses": [ "Free Plan data is used to train Mem0's models, per the privacy policy of 22 August 2026", "No published Platform rate limits or general 429 handling, and no SLA outside a sales contract", "Since 26 October 2026 no paid plan is sold to new accounts and the usage-based rate appears only in the dashboard", "Six advisories on mem0ai were published between 2 May and 28 October 2026, among them a Critical SQL injection and a cross-tenant leak", "delete_all_memories and delete_entities are in the default MCP tool list with no read-only mode" ], "agentNotes": [ "Send the REST key as `Authorization: Token \u003ckey\u003e`, and the MCP key as Bearer", "Don't search for a memory straight after adding it. Adds are queued, so poll get_event_status with the returned event ID", "Never pass an empty `user_id` or other entity ID to delete_all. The docs say an empty ID matches every memory in the project", "After a free account's first 30 days, connect an LLM key in Settings, or adds return an error while searches keep working", "Set `MEM0_TELEMETRY=false` to stop the SDK's PostHog events, which the hosted client sends under the account email" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 2.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 40.1 } ], "editorialScores": { "ergonomics": 63, "maintenance": 75, "payments": 40, "reliability": 25, "schema": 80, "security": 45, "transparency": 56 }, "provenanceScore": 68, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install mem0ai # or: npm install mem0ai", "http": "curl -X POST https://api.mem0.ai/v1/memories/ -H \"Authorization: Token $MEM0_API_KEY\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"messages\":[{\"role\":\"user\",\"content\":\"I am vegetarian and allergic to nuts.\"}],\"user_id\":\"alex\"}'", "claudeCode": "claude mcp add --transport http mem0 https://mcp.mem0.ai/mcp --header \"Authorization: Bearer $MEM0_API_KEY\"", "config": { "mcpServers": { "mem0": { "headers": { "Authorization": "Bearer ${MEM0_API_KEY}" }, "type": "http", "url": "https://mcp.mem0.ai/mcp" } } } }, "letme": { "capability": "https://letme.dev/memory.store", "tool": "https://letme.dev/mem0" }, "area": "agent-runtime", "provenance": { "legalEntity": "Embedchain, Inc. (DBA Mem0)", "domain": "mem0.ai", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://mem0.ai/terms", "privacy": "https://mem0.ai/privacy-policy", "statusPage": "https://status.mem0.ai", "changelog": "https://docs.mem0.ai/changelog/platform", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "The privacy policy, last updated 22 August 2026, names Embedchain, Inc. doing business as Mem0, and lists OpenAI and Anthropic among the AI providers that process data.", "mem0.ai/.well-known/security.txt returns 404." ], "score": 68 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/mem0.json", "live": { "slug": "mem0", "probe": { "target": "https://api.mem0.ai", "method": "get", "lastAt": "2026-11-07T18:20:38.456031724Z", "lastOk": true, "lastStatus": 200, "lastMs": 534, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 462, "p95ms24h": 557, "samples24h": 239, "samples30d": 7910, "days": [ { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://status.mem0.ai", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:02.607773492Z" }, "versions": [ { "registry": "github", "name": "mem0ai/mem0", "version": "ts-v3.3.1", "released": "2026-09-25", "seenAt": "2026-11-06T23:43:52.566540472Z" }, { "registry": "mcp-registry", "name": "io.github.mem0ai/mem0", "version": "1.0.0", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "npm", "name": "mem0ai", "version": "3.3.1", "seenAt": "2026-11-06T23:43:50.751992157Z" }, { "registry": "pypi", "name": "mem0ai", "version": "2.2.1", "released": "2026-09-25", "seenAt": "2026-11-06T23:43:50.559739208Z" } ], "githubStars": 68531, "npmWeekly": 267851, "pypiWeekly": 591780, "securityTxt": { "url": "https://mem0.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:40.28309414Z" }, "llmsTxt": { "url": "https://mem0.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:59.262882324Z" }, "domain": { "domain": "mem0.ai", "registered": "2024-05-15", "source": "https://rdap.identitydigital.services/rdap/domain/mem0.ai", "checkedAt": "2026-11-01T14:09:04.649174009Z" }, "pages": [ { "url": "https://docs.mem0.ai/changelog/platform", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:07:00.503340695Z", "changedAt": "2026-10-27T03:44:38.791963666Z", "fingerprint": "169e29f348bb" }, { "url": "https://mem0.ai/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-04T08:27:49.243202525Z", "changedAt": "2026-10-27T03:50:03.843667488Z", "fingerprint": "b949f961f237" }, { "url": "https://raw.githubusercontent.com/mem0ai/mem0/main/docs/platform/pricing.mdx", "kind": "pricing", "status": 304, "checkedAt": "2026-11-07T14:21:41.095179342Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "82ec3077357d" }, { "url": "https://mem0.ai/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:14:09.309238426Z", "changedAt": "2026-10-27T03:50:05.971091022Z", "fingerprint": "f0cad2d4a658" }, { "url": "https://mem0.ai/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:14:11.686070925Z", "changedAt": "2026-10-27T03:50:08.177389046Z", "fingerprint": "94c917289ed0" } ], "mcpTools": { "url": "https://mcp.mem0.ai/mcp", "checkedAt": "2026-11-07T01:46:13.530814635Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:46:13.530814635Z" }, "github": { "repo": "mem0ai/mem0", "checkedAt": "2026-11-02T09:04:45.050881633Z", "stars": 68264, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-30T21:36:23Z", "openIssues": 446, "openPRs": 452, "issuesOpened90d": 315, "issuesClosed90d": 104, "prsMerged90d": 129, "ci": { "branch": "main", "runs": 50, "success": 45, "failure": 5, "other": 0, "latest": "success", "latestAt": "2026-10-30T21:44:18Z" }, "advisories": [ { "ghsa": "GHSA-5324-3w58-qpp2", "cve": "CVE-2026-116575", "severity": "medium", "published": "2026-10-20T17:17:59Z" } ], "replies": { "sampled": 25, "unanswered": 25 } }, "updatedAt": "2026-11-07T18:20:38.456031724Z" } }, "answer": "Memori scores 44.2 (E) on agent readiness against Mem0 Platform + MCP's 40.1 (E), and leads in 3 of 7 scored categories. Mem0 Platform + MCP leads on schema \u0026 documentation, maintenance \u0026 community and transparency \u0026 trust.", "b": { "slug": "memori", "name": "Memori", "vendor": "Memori Labs Inc.", "vendorUrl": "https://memorilabs.ai", "kind": "sdk", "category": "agent-memory", "summary": "Memori is a memory layer from Memori Labs that wraps an app's LLM client to capture conversations and agent traces, extract facts and recall them into later prompts, through Python and TypeScript SDKs, a CLI and a hosted MCP endpoint.", "url": "https://www.anchorterminal.com/tools/memori", "markdownUrl": "https://www.anchorterminal.com/tools/memori.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/memori.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/memori.json", "dns": "memori.grade.anchorterminal.com", "repo": "https://github.com/MemoriLabs/Memori", "license": "Apache-2.0", "transports": [ "streamable-http" ], "remoteUrl": "https://api.memorilabs.ai/mcp/", "packages": [ { "registry": "pypi", "name": "memori" }, { "registry": "npm", "name": "@memorilabs/memori" } ], "auth": "api-key", "authNotes": "Memori Cloud and the MCP endpoint take an API key, `X-Memori-API-Key` on MCP and a bearer token in the SDK. Keys come from app.memorilabs.ai or a CLI signup by email. Own-database mode works without a key, using a built-in anonymous key with a quota of 100 augmentations a month.", "pricing": "freemium", "pricingNotes": "A free key gives 5,000 Advanced Augmentation calls a month, per the docs; 100 a month without a key. Paid plans are sold through sales from $60,000 a year (Team) and $150,000 (Business), with Enterprise priced privately.", "priceSummary": "Freemium", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the SDK source, docs, llms.txt or pricing page (checked 2026-11-06).", "endpoints": [] }, "toolCount": 7, "popularity": { "githubStars": 17446, "npmWeekly": 130, "pypiWeekly": 3781, "asOf": "2026-11-06" }, "docsUrl": "https://memorilabs.ai/docs/memori-cloud/", "llmsTxt": "https://memorilabs.ai/llms.txt", "capabilities": [ "memory.store", "memory.search", "memory.user", "memory.graph" ], "tags": [ "open-source", "hosted", "freemium", "free-tier", "apache-2.0", "python", "typescript", "cli", "mcp", "remote-mcp", "llms-txt", "sales-led" ], "lastRelease": "2026-05-27", "graded": true, "anchor": { "graded": true, "score": 44.2, "grade": "E", "agentReady": false, "rank": 1214, "ranked": true, "rankOf": 1486, "categoryRank": 25, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 65, "maintenance": 33, "payments": 45, "reliability": 28, "schema": 68, "security": 45, "transparency": 52 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": -4, "negativeNotes": [ "-4: misleading claim, confirmed first-hand on 6 November 2026. The BYODB architecture page says \"All data stays on your infrastructure\" and that storage has \"no external dependencies\" (https://memorilabs.ai/docs/memori-byodb/concepts/architecture), but the SDK's Advanced Augmentation posts conversation messages, the conversation summary and the system prompt to https://api.memorilabs.ai/sdk/augmentation, using a built-in anonymous key when the user has none (https://github.com/MemoriLabs/Memori/blob/main/memori/memory/augmentation/augmentations/memori/_augmentation.py and memori/_network.py). The FAQ's mention of augmentation quotas hints at the call but doesn't say conversations leave the user's infrastructure." ], "verdict": "Memori wraps an app's LLM client to capture conversations and recall facts, through Apache-2.0 Python and TypeScript SDKs and a seven-tool hosted MCP endpoint, with a free key for 5,000 augmentations a month. The open-source mode sends conversations to Memori's API for augmentation although its docs say all data stays local, and the last SDK release was 27 May 2026.", "bestFor": "Memory captured from LLM calls for apps that already use OpenAI, Anthropic or Gemini clients.", "strengths": [ "Python and TypeScript SDKs under Apache-2.0 that register an existing LLM client and recall memories into the prompt", "Hosted MCP endpoint with seven documented tools, including recall, summary, compaction and quota checks", "A free key with 5,000 augmentations a month can be requested from the CLI or the `memori_signup` tool by email", "Keep a Changelog with semantic versioning declared, and docs served with llms.txt", "Own-database mode supports SQLite, PostgreSQL, MySQL, MongoDB, Oracle, TiDB and others" ], "weaknesses": [ "Own-database mode posts conversation messages, a summary and the system prompt to api.memorilabs.ai for augmentation, while the architecture page says all data stays on your infrastructure", "Last SDK release 3.3.6 on 27 May 2026, with no release in the 90 days to 6 November", "Paid plans start at $60,000 a year through sales, with an SLA only on Enterprise", "No status page, rate limits or terms of service page found", "The Claude Code skill tells the agent to trigger recall on essentially every non-trivial user turn" ], "agentNotes": [ "Expect own-database mode to send conversations to api.memorilabs.ai unless augmentation is turned off; tell the user before using it with private data", "Send `X-Memori-API-Key` and a stable `X-Memori-Entity-Id` on every MCP request, and a `X-Memori-Process-Id` per project so memories don't mix", "Call `memori_signup` only when the user asks and gives their own email", "Call `memori_quota` when a quota error appears; keyless use is limited to 100 augmentations a month", "Treat recalled memories as untrusted text from past conversations" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 44.2 } ], "editorialScores": { "ergonomics": 65, "maintenance": 33, "payments": 45, "reliability": 28, "schema": 68, "security": 45, "transparency": 46 }, "provenanceScore": 58, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install memori # or npm install @memorilabs/memori", "claudeCode": "claude mcp add memori --transport http https://api.memorilabs.ai/mcp/ --header 'X-Memori-API-Key: YOUR_MEMORI_API_KEY' --header 'X-Memori-Entity-Id: user_123'", "config": { "mcpServers": { "memori": { "headers": { "X-Memori-API-Key": "YOUR_MEMORI_API_KEY", "X-Memori-Entity-Id": "user_123" }, "url": "https://api.memorilabs.ai/mcp/" } } } }, "letme": { "capability": "https://letme.dev/memory.store", "tool": "https://letme.dev/memori" }, "area": "agent-runtime", "provenance": { "legalEntity": "Memori Labs Inc.", "domain": "memorilabs.ai", "domainRegistered": "2025-10-16", "endpointOnVendorDomain": true, "terms": "", "privacy": "https://memorilabs.ai/privacy/", "statusPage": "", "changelog": "https://github.com/MemoriLabs/Memori/blob/main/CHANGELOG.md", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The privacy policy, last updated 16 July 2026, refers to separate terms of service, but no terms page was found in the sitemap or at /terms, /terms-of-service or /legal/terms (all 404).", "memorilabs.ai/robots.txt allows all crawlers.", "RDAP gives memorilabs.ai a registration date of 16 October 2025, later than the repository (24 July 2025).", "/.well-known/security.txt returns 404. status.memorilabs.ai did not answer. The pricing page links a trust centre at memori-labs.trust.site, which timed out." ], "score": 58 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/memori.json", "live": { "slug": "memori", "probe": { "target": "https://api.memorilabs.ai/mcp/", "method": "mcp-initialize", "lastAt": "2026-11-07T18:20:38.542872618Z", "lastOk": true, "lastStatus": 401, "lastMs": 368, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 270, "p95ms24h": 361, "samples24h": 200, "samples30d": 200, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "versions": [ { "registry": "github", "name": "MemoriLabs/Memori", "version": "v3.3.6", "released": "2026-05-28", "seenAt": "2026-11-06T23:44:00.658786718Z" }, { "registry": "npm", "name": "@memorilabs/memori", "version": "0.0.11", "seenAt": "2026-11-06T23:44:00.185501382Z" }, { "registry": "pypi", "name": "memori", "version": "3.3.6", "released": "2026-05-28", "seenAt": "2026-11-06T23:44:00.000273764Z" } ], "githubStars": 17448, "npmWeekly": 130, "pypiWeekly": 3781, "securityTxt": { "url": "https://memorilabs.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T15:59:51.635644364Z" }, "llmsTxt": { "url": "https://memorilabs.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:59.605618502Z" }, "pages": [ { "url": "https://raw.githubusercontent.com/MemoriLabs/Memori/main/CHANGELOG.md", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:18:47.202866715Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "4f28fd41f6ed" }, { "url": "https://memorilabs.ai/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:14:13.209756014Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "29e786d80880" } ], "mcpTools": { "url": "https://api.memorilabs.ai/mcp/", "checkedAt": "2026-11-07T01:46:13.890822383Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:46:13.890822383Z" }, "updatedAt": "2026-11-07T18:20:38.542872618Z" } }, "edges": [ { "by": 42, "category": "maintenance", "leads": "mem0", "name": "Maintenance \u0026 community", "reasons": { "a": "The newest releases are Python mem0ai 2.2.1 and npm mem0ai 3.3.1 of 25 September 2026 (tags v2.2.1 and ts-v3.3.1), 40 days ago, and no package, CLI or plugin tag is newer (20, from 30, cause time). In the 90 days from 6 August, Python v2.0.18 (12 August), v2.0.19 (24 August), v2.0.20 (2 September), v2.1.0 (18 September), v2.2.0 (24 September) and v2.2.1, with the matching TypeScript releases (20). Issues and pull requests weren't re-read (github.com refused). 15 of 25 per the 1 October check. Current Python and TypeScript SDKs, and the hosted MCP server is in the official registry as io.github.mem0ai/mem0 per the 1 October check (15). CI workflows run on pull requests, with run state unread (5 of 10). 20+20+15+15+5 = 75.", "b": "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." }, "scores": { "a": 75, "b": 33 } }, { "by": 12, "category": "schema", "leads": "mem0", "name": "Schema \u0026 documentation", "reasons": { "a": "OpenAPI 3.0.1 file in the docs source (docs/openapi.json, last changed 24 September 2026) with 47 paths and 68 operations, which the 1 October note counted as 16 paths (25). llms.txt with a \"Use when\" line for each page, per the 1 October check (10). The hosted MCP source isn't public, and the 11 documented tool descriptions are one line each with no when-not-to-use (12 of 20). Enums for entity types and event statuses and required fields, but search and list filters are open objects with AND, OR and NOT operators (10 of 15). Examples throughout. 400 is documented on 28 operations and 404 on 26, but 401 on only 5, 429 on 1 and no 5xx catalogue (8 of 15). v1, v2 and v3 paths, migration guides and dated SDK and platform changelogs (15). 25+10+12+10+8+15 = 80.", "b": "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." }, "scores": { "a": 80, "b": 68 } }, { "by": 10, "category": "transparency", "leads": "mem0", "name": "Transparency \u0026 trust", "reasons": { "a": "The extraction library is Apache-2.0, but the Platform, the product listed here, is closed (20 of 30). Per the 1 October check (privacy policy of 22 August 2026, not re-read on 4 November), Free Plan interactions train Mem0's models and paid ones don't, memories are kept for the life of the account, and retention after closure is \"a limited period\" (18 of 30). Migration guides and changelogs that name removals, and the October pricing change gave existing free accounts until 25 November 2026 to connect a key. No written deprecation policy (10 of 20). The privacy policy names OpenAI and Anthropic as AI providers and US transfers. No full subprocessor list was found (8 of 20). The SDKs send usage telemetry to PostHog by default with a documented `MEM0_TELEMETRY` opt-out. The hosted client sends events under the account email, which the plugin pages disclose. No term. 20+18+10+8 = 56.", "b": "Apache-2.0 per the LICENSE text, though GitHub reports it as NOASSERTION (30). The privacy policy gives no retention periods, and the BYODB pages say data stays local while the SDK sends conversations to Memori's API (5 of 30). Changelog entries but no deprecation policy or notices (5 of 20). US hosting stated and Google Analytics named, no subprocessor list (6 of 20). Total 46." }, "scores": { "a": 62, "b": 52 } }, { "by": 5, "category": "payments", "leads": "memori", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). Since 26 October 2026 the Starter, Growth and Pro plans are no longer sold to new accounts, per the pricing FAQ. Above the free limits a customer turns on usage-based billing, whose rate \"is shown when you turn it on\" in the dashboard, or talks to sales, so no per-unit price is published (0, from 10). The free plan needs no card. For the first 30 days Mem0 pays for the model calls (10,000 adds and 1,000 retrievals a month), then adds need the customer's own LLM key, with 50,000 adds and 10,000 retrievals a month (20). `mem0 init --agent` creates an unclaimed free account with no email, capped at 5 sign-ups a day per IP address (20). 0+0+20+20 = 40.", "b": "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." }, "scores": { "a": 40, "b": 45 } } ], "facts": [ { "a": "HTTP API", "b": "SDK + MCP", "name": "Kind" }, { "a": "Mem0", "b": "Memori Labs Inc.", "name": "Vendor" }, { "a": "https://api.mem0.ai", "b": "https://api.memorilabs.ai/mcp/", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Apache-2.0", "b": "Apache-2.0", "name": "Licence" }, { "a": "11", "b": "7", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "io.github.mem0ai/mem0", "b": "not listed", "name": "MCP registry" }, { "a": "2026-09-25", "b": "2026-05-27", "name": "Last release" }, { "a": "no date given", "b": "no document linked", "name": "Terms last updated" }, { "a": "no date given", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "yes", "b": "not read yet", "name": "Customer content may train models" }, { "a": "yes", "b": "not read yet", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not read yet", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not read yet", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not read yet", "name": "Arbitration or class-action waiver" }, { "a": "66k stars, 168k npm/wk, 502k PyPI/wk", "b": "17k stars, 130 npm/wk, 3.8k PyPI/wk", "name": "Popularity" }, { "a": "2.5/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Memori scores 44.2 (E) on agent readiness against Mem0 Platform + MCP's 40.1 (E), and leads in 3 of 7 scored categories. Mem0 Platform + MCP leads on schema \u0026 documentation, maintenance \u0026 community and transparency \u0026 trust.", "question": "Which is better for AI agents, Mem0 Platform + MCP or Memori?" }, { "answer": "Yes. Mem0 Platform + MCP has a hosted endpoint at https://api.mem0.ai and Memori at https://api.memorilabs.ai/mcp/.", "question": "Can an agent call Mem0 Platform + MCP and Memori without installing anything?" }, { "answer": "Yes. Mem0 Platform + MCP is open source (Apache-2.0). Memori is open source (Apache-2.0).", "question": "Are Mem0 Platform + MCP and Memori open source?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 80 against 68", "Maintenance \u0026 community, 75 against 33", "Transparency \u0026 trust, 62 against 52" ], "also": [ "Free to start without a card" ], "goodFor": "Chat products that want per-user facts back with one search call and little setup, and teams willing to connect their own LLM key for higher free limits.", "slug": "mem0", "watchFor": "Free Plan data is used to train Mem0's models, per the privacy policy of 22 August 2026" }, { "aheadOn": [ "Payments \u0026 pricing, 45 against 40" ], "also": null, "goodFor": "Memory captured from LLM calls for apps that already use OpenAI, Anthropic or Gemini clients.", "slug": "memori", "watchFor": "Own-database mode posts conversation messages, a summary and the system prompt to api.memorilabs.ai for augmentation, while the architecture page says all data stays on your infrastructure" } ], "history": { "mem0": [ { "causes": [ "pricing", "evidence", "event", "time" ], "date": "2026-11-04", "delta": -16.1, "from": 56.2, "fromGrade": "C", "to": 40.1, "toGrade": "E" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 56.1, "fromGrade": "C", "to": 56.2, "toGrade": "C" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.5, "from": 56.6, "fromGrade": "C", "to": 56.1, "toGrade": "C" } ], "memori": null }, "job": { "capability": "memory.store", "name": "Agent memory" }, "others": [ { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-mem0.json", "title": "Amazon Bedrock AgentCore Memory vs Mem0 Platform + MCP", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-mem0" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-memori.json", "title": "Amazon Bedrock AgentCore Memory vs Memori", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-memori" }, { "json": "https://www.anchorterminal.com/compare/basic-memory-vs-mem0.json", "title": "Basic Memory vs Mem0 Platform + MCP", "url": "https://www.anchorterminal.com/compare/basic-memory-vs-mem0" }, { "json": "https://www.anchorterminal.com/compare/basic-memory-vs-memori.json", "title": "Basic Memory vs Memori", "url": "https://www.anchorterminal.com/compare/basic-memory-vs-memori" }, { "json": "https://www.anchorterminal.com/compare/claude-mem-vs-mem0.json", "title": "claude-mem vs Mem0 Platform + MCP", "url": "https://www.anchorterminal.com/compare/claude-mem-vs-mem0" }, { "json": "https://www.anchorterminal.com/compare/claude-mem-vs-memori.json", "title": "claude-mem vs Memori", "url": "https://www.anchorterminal.com/compare/claude-mem-vs-memori" }, { "json": "https://www.anchorterminal.com/compare/cognee-vs-mem0.json", "title": "Cognee vs Mem0 Platform + MCP", "url": "https://www.anchorterminal.com/compare/cognee-vs-mem0" }, { "json": "https://www.anchorterminal.com/compare/cognee-vs-memori.json", "title": "Cognee vs Memori", "url": "https://www.anchorterminal.com/compare/cognee-vs-memori" }, { "json": "https://www.anchorterminal.com/compare/everos-vs-mem0.json", "title": "EverOS vs Mem0 Platform + MCP", "url": "https://www.anchorterminal.com/compare/everos-vs-mem0" }, { "json": "https://www.anchorterminal.com/compare/everos-vs-memori.json", "title": "EverOS vs Memori", "url": "https://www.anchorterminal.com/compare/everos-vs-memori" }, { "json": "https://www.anchorterminal.com/compare/google-memory-bank-vs-mem0.json", "title": "Agent Platform Memory Bank vs Mem0 Platform + MCP", "url": "https://www.anchorterminal.com/compare/google-memory-bank-vs-mem0" }, { "json": "https://www.anchorterminal.com/compare/google-memory-bank-vs-memori.json", "title": "Agent Platform Memory Bank vs Memori", "url": "https://www.anchorterminal.com/compare/google-memory-bank-vs-memori" }, { "json": "https://www.anchorterminal.com/compare/graphiti-vs-mem0.json", "title": "Graphiti vs Mem0 Platform + MCP", "url": "https://www.anchorterminal.com/compare/graphiti-vs-mem0" }, { "json": "https://www.anchorterminal.com/compare/graphiti-vs-memori.json", "title": "Graphiti vs Memori", "url": "https://www.anchorterminal.com/compare/graphiti-vs-memori" }, { "json": "https://www.anchorterminal.com/compare/hindsight-vs-mem0.json", "title": "Hindsight vs Mem0 Platform + MCP", "url": "https://www.anchorterminal.com/compare/hindsight-vs-mem0" }, { "json": "https://www.anchorterminal.com/compare/hindsight-vs-memori.json", "title": "Hindsight vs Memori", "url": "https://www.anchorterminal.com/compare/hindsight-vs-memori" }, { "json": "https://www.anchorterminal.com/compare/honcho-vs-mem0.json", "title": "Honcho vs Mem0 Platform + MCP", "url": "https://www.anchorterminal.com/compare/honcho-vs-mem0" }, { "json": "https://www.anchorterminal.com/compare/honcho-vs-memori.json", "title": "Honcho vs Memori", "url": "https://www.anchorterminal.com/compare/honcho-vs-memori" }, { "json": "https://www.anchorterminal.com/compare/hy-memory-vs-mem0.json", "title": "Hy Memory vs Mem0 Platform + MCP", "url": "https://www.anchorterminal.com/compare/hy-memory-vs-mem0" }, { "json": "https://www.anchorterminal.com/compare/hy-memory-vs-memori.json", "title": "Hy Memory vs Memori", "url": "https://www.anchorterminal.com/compare/hy-memory-vs-memori" }, { "json": "https://www.anchorterminal.com/compare/langmem-vs-mem0.json", "title": "LangMem vs Mem0 Platform + MCP", "url": "https://www.anchorterminal.com/compare/langmem-vs-mem0" }, { "json": "https://www.anchorterminal.com/compare/langmem-vs-memori.json", "title": "LangMem vs Memori", "url": "https://www.anchorterminal.com/compare/langmem-vs-memori" }, { "json": "https://www.anchorterminal.com/compare/localghost-vs-mem0.json", "title": "LocalGhost vs Mem0 Platform + MCP", "url": "https://www.anchorterminal.com/compare/localghost-vs-mem0" }, { "json": "https://www.anchorterminal.com/compare/localghost-vs-memori.json", "title": "LocalGhost vs Memori", "url": "https://www.anchorterminal.com/compare/localghost-vs-memori" }, { "json": "https://www.anchorterminal.com/compare/mem0-vs-memmachine.json", "title": "Mem0 Platform + MCP vs MemMachine", "url": "https://www.anchorterminal.com/compare/mem0-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/mem0-vs-memory-reference-server.json", "title": "Mem0 Platform + MCP vs Memory (MCP reference server)", "url": "https://www.anchorterminal.com/compare/mem0-vs-memory-reference-server" }, { "json": "https://www.anchorterminal.com/compare/mem0-vs-mempalace.json", "title": "Mem0 Platform + MCP vs MemPalace", "url": "https://www.anchorterminal.com/compare/mem0-vs-mempalace" }, { "json": "https://www.anchorterminal.com/compare/mem0-vs-past-dev.json", "title": "Mem0 Platform + MCP vs past.dev", "url": "https://www.anchorterminal.com/compare/mem0-vs-past-dev" }, { "json": "https://www.anchorterminal.com/compare/mem0-vs-supermemory.json", "title": "Mem0 Platform + MCP vs Supermemory API + MCP", "url": "https://www.anchorterminal.com/compare/mem0-vs-supermemory" }, { "json": "https://www.anchorterminal.com/compare/mem0-vs-tencentdb-agent-memory.json", "title": "Mem0 Platform + MCP vs TencentDB Agent Memory", "url": "https://www.anchorterminal.com/compare/mem0-vs-tencentdb-agent-memory" }, { "json": "https://www.anchorterminal.com/compare/mem0-vs-tokenrip.json", "title": "Mem0 Platform + MCP vs Tokenrip", "url": "https://www.anchorterminal.com/compare/mem0-vs-tokenrip" }, { "json": "https://www.anchorterminal.com/compare/mem0-vs-zep.json", "title": "Mem0 Platform + MCP vs Zep", "url": "https://www.anchorterminal.com/compare/mem0-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/memmachine-vs-memori.json", "title": "MemMachine vs Memori", "url": "https://www.anchorterminal.com/compare/memmachine-vs-memori" }, { "json": "https://www.anchorterminal.com/compare/memori-vs-memory-reference-server.json", "title": "Memori vs Memory (MCP reference server)", "url": "https://www.anchorterminal.com/compare/memori-vs-memory-reference-server" }, { "json": "https://www.anchorterminal.com/compare/memori-vs-mempalace.json", "title": "Memori vs MemPalace", "url": "https://www.anchorterminal.com/compare/memori-vs-mempalace" }, { "json": "https://www.anchorterminal.com/compare/memori-vs-past-dev.json", "title": "Memori vs past.dev", "url": "https://www.anchorterminal.com/compare/memori-vs-past-dev" }, { "json": "https://www.anchorterminal.com/compare/memori-vs-supermemory.json", "title": "Memori vs Supermemory API + MCP", "url": "https://www.anchorterminal.com/compare/memori-vs-supermemory" }, { "json": "https://www.anchorterminal.com/compare/memori-vs-tencentdb-agent-memory.json", "title": "Memori vs TencentDB Agent Memory", "url": "https://www.anchorterminal.com/compare/memori-vs-tencentdb-agent-memory" }, { "json": "https://www.anchorterminal.com/compare/memori-vs-tokenrip.json", "title": "Memori vs Tokenrip", "url": "https://www.anchorterminal.com/compare/memori-vs-tokenrip" }, { "json": "https://www.anchorterminal.com/compare/memori-vs-zep.json", "title": "Memori vs Zep", "url": "https://www.anchorterminal.com/compare/memori-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/ai-memory-vs-mem0.json", "title": "AI Memory vs Mem0 Platform + MCP", "url": "https://www.anchorterminal.com/compare/ai-memory-vs-mem0" }, { "json": "https://www.anchorterminal.com/compare/ai-memory-vs-memori.json", "title": "AI Memory vs Memori", "url": "https://www.anchorterminal.com/compare/ai-memory-vs-memori" }, { "json": "https://www.anchorterminal.com/compare/context-mode-vs-mem0.json", "title": "Context Mode Engine vs Mem0 Platform + MCP", "url": "https://www.anchorterminal.com/compare/context-mode-vs-mem0" }, { "json": "https://www.anchorterminal.com/compare/context-mode-vs-memori.json", "title": "Context Mode Engine vs Memori", "url": "https://www.anchorterminal.com/compare/context-mode-vs-memori" }, { "json": "https://www.anchorterminal.com/compare/graphicle-vs-mem0.json", "title": "Graphicle vs Mem0 Platform + MCP", "url": "https://www.anchorterminal.com/compare/graphicle-vs-mem0" }, { "json": "https://www.anchorterminal.com/compare/graphicle-vs-memori.json", "title": "Graphicle vs Memori", "url": "https://www.anchorterminal.com/compare/graphicle-vs-memori" } ], "panel": null, "scores": [ { "by": 3, "edge": "memori", "key": "reliability", "mem0": 25, "memori": 28, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 12, "edge": "mem0", "key": "schema", "mem0": 80, "memori": 68, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 2, "edge": "memori", "key": "ergonomics", "mem0": 63, "memori": 65, "name": "Agent ergonomics", "weight": 13 }, { "by": 0, "edge": "", "key": "security", "mem0": 45, "memori": 45, "name": "Security \u0026 auth", "weight": 14 }, { "by": 5, "edge": "memori", "key": "payments", "mem0": 40, "memori": 45, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 42, "edge": "mem0", "key": "maintenance", "mem0": 75, "memori": 33, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 10, "edge": "mem0", "key": "transparency", "mem0": 62, "memori": 52, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Memori scores 44.2 (E) on agent readiness against Mem0 Platform + MCP's 40.1 (E), and leads in 3 of 7 scored categories. Mem0 Platform + MCP leads on schema \u0026 documentation, maintenance \u0026 community and transparency \u0026 trust. Both do agent memory.", "tasks": null, "tutorials": [], "verdicts": { "mem0": "An agent can create its own free account with `mem0 init --agent`, no email and no card, and free limits rise to 50,000 adds a month with the customer's own LLM key. Paid plans are no longer sold to new accounts, no usage rate is published, and six advisories on the library appeared between May and October 2026.", "memori": "Memori wraps an app's LLM client to capture conversations and recall facts, through Apache-2.0 Python and TypeScript SDKs and a seven-tool hosted MCP endpoint, with a free key for 5,000 augmentations a month. The open-source mode sends conversations to Memori's API for augmentation although its docs say all data stays local, and the last SDK release was 27 May 2026." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/mem0-vs-memori", "json": "https://www.anchorterminal.com/compare/mem0-vs-memori.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/mem0-vs-memori.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/mem0-vs-memori.min.md" }, "markdown": "Memori scores 44.2 (E) on agent readiness against Mem0 Platform + MCP's 40.1 (E), and leads in 3 of 7 scored categories. Mem0 Platform + MCP leads on schema \u0026 documentation, maintenance \u0026 community and transparency \u0026 trust. Both do agent memory.\n\n- Mem0 Platform + MCP: grade E, 40.1/100, rank #1310 of 1486. Markdown https://www.anchorterminal.com/tools/mem0.md · JSON https://www.anchorterminal.com/api/v1/tools/mem0.json\n- Memori: grade E, 44.2/100, rank #1214 of 1486. Markdown https://www.anchorterminal.com/tools/memori.md · JSON https://www.anchorterminal.com/api/v1/tools/memori.json\n- Best memory layers for AI agents: https://www.anchorterminal.com/best/agent-memory/index.md\n- All 353 memory comparisons: https://www.anchorterminal.com/compare/agent-memory/index.md\n\n## Which one, for what\n\n### Mem0 Platform + MCP (E)\n\nGood for: Chat products that want per-user facts back with one search call and little setup, and teams willing to connect their own LLM key for higher free limits.\n\nAhead on:\n- Schema \u0026 documentation, 80 against 68\n- Maintenance \u0026 community, 75 against 33\n- Transparency \u0026 trust, 62 against 52\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: Free Plan data is used to train Mem0's models, per the privacy policy of 22 August 2026\n\n### Memori (E)\n\nGood for: Memory captured from LLM calls for apps that already use OpenAI, Anthropic or Gemini clients.\n\nAhead on:\n- Payments \u0026 pricing, 45 against 40\n\nWatch for: Own-database mode posts conversation messages, a summary and the system prompt to api.memorilabs.ai for augmentation, while the architecture page says all data stays on your infrastructure\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Mem0 Platform + MCP +42\n\n- Mem0 Platform + MCP (75): The newest releases are Python mem0ai 2.2.1 and npm mem0ai 3.3.1 of 25 September 2026 (tags v2.2.1 and ts-v3.3.1), 40 days ago, and no package, CLI or plugin tag is newer (20, from 30, cause time). In the 90 days from 6 August, Python v2.0.18 (12 August), v2.0.19 (24 August), v2.0.20 (2 September), v2.1.0 (18 September), v2.2.0 (24 September) and v2.2.1, with the matching TypeScript releases (20). Issues and pull requests weren't re-read (github.com refused). 15 of 25 per the 1 October check. Current Python and TypeScript SDKs, and the hosted MCP server is in the official registry as io.github.mem0ai/mem0 per the 1 October check (15). CI workflows run on pull requests, with run state unread (5 of 10). 20+20+15+15+5 = 75.\n- 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.\n\n### Schema \u0026 documentation: Mem0 Platform + MCP +12\n\n- Mem0 Platform + MCP (80): OpenAPI 3.0.1 file in the docs source (docs/openapi.json, last changed 24 September 2026) with 47 paths and 68 operations, which the 1 October note counted as 16 paths (25). llms.txt with a \"Use when\" line for each page, per the 1 October check (10). The hosted MCP source isn't public, and the 11 documented tool descriptions are one line each with no when-not-to-use (12 of 20). Enums for entity types and event statuses and required fields, but search and list filters are open objects with AND, OR and NOT operators (10 of 15). Examples throughout. 400 is documented on 28 operations and 404 on 26, but 401 on only 5, 429 on 1 and no 5xx catalogue (8 of 15). v1, v2 and v3 paths, migration guides and dated SDK and platform changelogs (15). 25+10+12+10+8+15 = 80.\n- 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.\n\n### Transparency \u0026 trust: Mem0 Platform + MCP +10\n\n- Mem0 Platform + MCP (62): The extraction library is Apache-2.0, but the Platform, the product listed here, is closed (20 of 30). Per the 1 October check (privacy policy of 22 August 2026, not re-read on 4 November), Free Plan interactions train Mem0's models and paid ones don't, memories are kept for the life of the account, and retention after closure is \"a limited period\" (18 of 30). Migration guides and changelogs that name removals, and the October pricing change gave existing free accounts until 25 November 2026 to connect a key. No written deprecation policy (10 of 20). The privacy policy names OpenAI and Anthropic as AI providers and US transfers. No full subprocessor list was found (8 of 20). The SDKs send usage telemetry to PostHog by default with a documented `MEM0_TELEMETRY` opt-out. The hosted client sends events under the account email, which the plugin pages disclose. No term. 20+18+10+8 = 56.\n- Memori (52): Apache-2.0 per the LICENSE text, though GitHub reports it as NOASSERTION (30). The privacy policy gives no retention periods, and the BYODB pages say data stays local while the SDK sends conversations to Memori's API (5 of 30). Changelog entries but no deprecation policy or notices (5 of 20). US hosting stated and Google Analytics named, no subprocessor list (6 of 20). Total 46.\n\n### Payments \u0026 pricing: Memori +5\n\n- Mem0 Platform + MCP (40): No x402, MPP or L402 (0). Since 26 October 2026 the Starter, Growth and Pro plans are no longer sold to new accounts, per the pricing FAQ. Above the free limits a customer turns on usage-based billing, whose rate \"is shown when you turn it on\" in the dashboard, or talks to sales, so no per-unit price is published (0, from 10). The free plan needs no card. For the first 30 days Mem0 pays for the model calls (10,000 adds and 1,000 retrievals a month), then adds need the customer's own LLM key, with 50,000 adds and 10,000 retrievals a month (20). `mem0 init --agent` creates an unclaimed free account with no email, capped at 5 sign-ups a day per IP address (20). 0+0+20+20 = 40.\n- 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.\n\n## Score by category\n\n| Category | Weight | Mem0 Platform + MCP | Memori | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 25 | 28 | Memori +3 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 80 | 68 | Mem0 Platform + MCP +12 |\n| Agent ergonomics | 13% (16.2 this run) | 63 | 65 | Memori +2 |\n| Security \u0026 auth | 14% (17.5 this run) | 45 | 45 | even |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 45 | Memori +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 75 | 33 | Mem0 Platform + MCP +42 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 62 | 52 | Mem0 Platform + MCP +10 |\n| Negative events | ≤15 | -13 | -4 | |\n| **Total** | | **40.1 · E** | **44.2 · E** | |\n\n## Facts side by side\n\n| Fact | Mem0 Platform + MCP | Memori |\n| --- | --- | --- |\n| Kind | HTTP API | SDK + MCP |\n| Vendor | Mem0 | Memori Labs Inc. |\n| Hosted endpoint | `https://api.mem0.ai` | `https://api.memorilabs.ai/mcp/` |\n| Transports | HTTP, Streamable HTTP | Streamable HTTP |\n| Auth | API key | API key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | Apache-2.0 | Apache-2.0 |\n| Tools exposed | 11 | 7 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `io.github.mem0ai/mem0` | not listed |\n| Last release | 2026-09-25 | 2026-05-27 |\n| Terms last updated | no date given | no document linked |\n| Privacy policy last updated | no date given | no date given |\n| Customer content may train models | yes | not read yet |\n| Terms restrict automated access | yes | not read yet |\n| Terms restrict benchmarking | yes | not read yet |\n| Terms or service can change without notice | not found in the text | not read yet |\n| Arbitration or class-action waiver | yes | not read yet |\n| Popularity | 66k stars, 168k npm/wk, 502k PyPI/wk | 17k stars, 130 npm/wk, 3.8k PyPI/wk |\n| Agent reviews | 2.5/5 (2) | none |\n\n## How the scores have moved\n\n### Mem0 Platform + MCP\n\n- -16.1 on 4 November 2026 (C to E): pricing, new evidence, negative event, time\n- +0.1 on 27 October 2026: checklist\n- -0.5 on 8 October 2026: checklist\n\n### Memori\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Mem0 Platform + MCP.** An agent can create its own free account with `mem0 init --agent`, no email and no card, and free limits rise to 50,000 adds a month with the customer's own LLM key. Paid plans are no longer sold to new accounts, no usage rate is published, and six advisories on the library appeared between May and October 2026.\n\n**Memori.** Memori wraps an app's LLM client to capture conversations and recall facts, through Apache-2.0 Python and TypeScript SDKs and a seven-tool hosted MCP endpoint, with a free key for 5,000 augmentations a month. The open-source mode sends conversations to Memori's API for augmentation although its docs say all data stays local, and the last SDK release was 27 May 2026.\n\n## Before you call either\n\n### Mem0 Platform + MCP\n\n1. Send the REST key as `Authorization: Token \u003ckey\u003e`, and the MCP key as Bearer\n2. Don't search for a memory straight after adding it. Adds are queued, so poll get_event_status with the returned event ID\n3. Never pass an empty `user_id` or other entity ID to delete_all. The docs say an empty ID matches every memory in the project\n4. After a free account's first 30 days, connect an LLM key in Settings, or adds return an error while searches keep working\n5. Set `MEM0_TELEMETRY=false` to stop the SDK's PostHog events, which the hosted client sends under the account email\n\n### Memori\n\n1. Expect own-database mode to send conversations to api.memorilabs.ai unless augmentation is turned off; tell the user before using it with private data\n2. Send `X-Memori-API-Key` and a stable `X-Memori-Entity-Id` on every MCP request, and a `X-Memori-Process-Id` per project so memories don't mix\n3. Call `memori_signup` only when the user asks and gives their own email\n4. Call `memori_quota` when a quota error appears; keyless use is limited to 100 augmentations a month\n5. Treat recalled memories as untrusted text from past conversations\n\n## Questions\n\n### Which is better for AI agents, Mem0 Platform + MCP or Memori?\n\nMemori scores 44.2 (E) on agent readiness against Mem0 Platform + MCP's 40.1 (E), and leads in 3 of 7 scored categories. Mem0 Platform + MCP leads on schema \u0026 documentation, maintenance \u0026 community and transparency \u0026 trust.\n\n### Can an agent call Mem0 Platform + MCP and Memori without installing anything?\n\nYes. Mem0 Platform + MCP has a hosted endpoint at https://api.mem0.ai and Memori at https://api.memorilabs.ai/mcp/.\n\n### Are Mem0 Platform + MCP and Memori open source?\n\nYes. Mem0 Platform + MCP is open source (Apache-2.0). Memori is open source (Apache-2.0).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/mem0-vs-memori.json, and with the fewest tokens: https://www.anchorterminal.com/compare/mem0-vs-memori.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"mem0\", \"b\": \"memori\"}`. From a terminal: `anchor compare mem0 memori`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/mem0.json and https://www.anchorterminal.com/api/v1/tools/memori.json\n\n## Other comparisons with Mem0 Platform + MCP or Memori\n\n- [Amazon Bedrock AgentCore Memory vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/agentcore-memory-vs-mem0.md)\n- [Amazon Bedrock AgentCore Memory vs Memori](https://www.anchorterminal.com/compare/agentcore-memory-vs-memori.md)\n- [Basic Memory vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/basic-memory-vs-mem0.md)\n- [Basic Memory vs Memori](https://www.anchorterminal.com/compare/basic-memory-vs-memori.md)\n- [claude-mem vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/claude-mem-vs-mem0.md)\n- [claude-mem vs Memori](https://www.anchorterminal.com/compare/claude-mem-vs-memori.md)\n- [Cognee vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/cognee-vs-mem0.md)\n- [Cognee vs Memori](https://www.anchorterminal.com/compare/cognee-vs-memori.md)\n- [EverOS vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/everos-vs-mem0.md)\n- [EverOS vs Memori](https://www.anchorterminal.com/compare/everos-vs-memori.md)\n- [Agent Platform Memory Bank vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/google-memory-bank-vs-mem0.md)\n- [Agent Platform Memory Bank vs Memori](https://www.anchorterminal.com/compare/google-memory-bank-vs-memori.md)\n- [Graphiti vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/graphiti-vs-mem0.md)\n- [Graphiti vs Memori](https://www.anchorterminal.com/compare/graphiti-vs-memori.md)\n- [Hindsight vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/hindsight-vs-mem0.md)\n- [Hindsight vs Memori](https://www.anchorterminal.com/compare/hindsight-vs-memori.md)\n- [Honcho vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/honcho-vs-mem0.md)\n- [Honcho vs Memori](https://www.anchorterminal.com/compare/honcho-vs-memori.md)\n- [Hy Memory vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/hy-memory-vs-mem0.md)\n- [Hy Memory vs Memori](https://www.anchorterminal.com/compare/hy-memory-vs-memori.md)\n- [LangMem vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/langmem-vs-mem0.md)\n- [LangMem vs Memori](https://www.anchorterminal.com/compare/langmem-vs-memori.md)\n- [LocalGhost vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/localghost-vs-mem0.md)\n- [LocalGhost vs Memori](https://www.anchorterminal.com/compare/localghost-vs-memori.md)\n- [Mem0 Platform + MCP vs MemMachine](https://www.anchorterminal.com/compare/mem0-vs-memmachine.md)\n- [Mem0 Platform + MCP vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/mem0-vs-memory-reference-server.md)\n- [Mem0 Platform + MCP vs MemPalace](https://www.anchorterminal.com/compare/mem0-vs-mempalace.md)\n- [Mem0 Platform + MCP vs past.dev](https://www.anchorterminal.com/compare/mem0-vs-past-dev.md)\n- [Mem0 Platform + MCP vs Supermemory API + MCP](https://www.anchorterminal.com/compare/mem0-vs-supermemory.md)\n- [Mem0 Platform + MCP vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/mem0-vs-tencentdb-agent-memory.md)\n- [Mem0 Platform + MCP vs Tokenrip](https://www.anchorterminal.com/compare/mem0-vs-tokenrip.md)\n- [Mem0 Platform + MCP vs Zep](https://www.anchorterminal.com/compare/mem0-vs-zep.md)\n- [MemMachine vs Memori](https://www.anchorterminal.com/compare/memmachine-vs-memori.md)\n- [Memori vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/memori-vs-memory-reference-server.md)\n- [Memori vs MemPalace](https://www.anchorterminal.com/compare/memori-vs-mempalace.md)\n- [Memori vs past.dev](https://www.anchorterminal.com/compare/memori-vs-past-dev.md)\n- [Memori vs Supermemory API + MCP](https://www.anchorterminal.com/compare/memori-vs-supermemory.md)\n- [Memori vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/memori-vs-tencentdb-agent-memory.md)\n- [Memori vs Tokenrip](https://www.anchorterminal.com/compare/memori-vs-tokenrip.md)\n- [Memori vs Zep](https://www.anchorterminal.com/compare/memori-vs-zep.md)\n- [AI Memory vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/ai-memory-vs-mem0.md)\n- [AI Memory vs Memori](https://www.anchorterminal.com/compare/ai-memory-vs-memori.md)\n- [Context Mode Engine vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/context-mode-vs-mem0.md)\n- [Context Mode Engine vs Memori](https://www.anchorterminal.com/compare/context-mode-vs-memori.md)\n- [Graphicle vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/graphicle-vs-mem0.md)\n- [Graphicle vs Memori](https://www.anchorterminal.com/compare/graphicle-vs-memori.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Mem0 Platform + MCP vs Memori", "url": "" } ], "description": "Memori scores 44.2 (E) to Mem0 Platform's 40.1 (E) for agent memory. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Mem0 Platform + MCP E 40.1", "Memori E 44.2", "scores" ], "h1": "Mem0 Platform + MCP vs Memori", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/mem0-vs-memori", "published": "2026-10-01", "section": "tools", "title": "Mem0 Platform vs Memori for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/mem0-vs-memori" }, "tokens": { "markdown": 4350, "slim": 1980 }, "version": 1 }