{ "data": { "a": { "slug": "memmachine", "name": "MemMachine", "vendor": "MemVerge, Inc.", "vendorUrl": "https://memmachine.ai", "kind": "http-api", "category": "agent-memory", "summary": "MemMachine is an open-source long-term memory layer for AI agents, incubated by MemVerge, with episodic, profile and working memory behind a self-hosted REST server, Python and TypeScript clients and an MCP server, plus a hosted platform.", "url": "https://www.anchorterminal.com/tools/memmachine", "markdownUrl": "https://www.anchorterminal.com/tools/memmachine.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/memmachine.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/memmachine.json", "dns": "memmachine.grade.anchorterminal.com", "repo": "https://github.com/MemMachine/MemMachine", "license": "Apache-2.0", "transports": [ "http", "stdio", "streamable-http" ], "packages": [ { "registry": "pypi", "name": "memmachine-server" }, { "registry": "pypi", "name": "memmachine-client" }, { "registry": "npm", "name": "@memmachine/client" } ], "auth": "none", "authNotes": "The self-hosted server takes no credential; the owner supplies LLM and embedding keys (OpenAI, Bedrock or Ollama) in its config. The hosted MemMachine Platform at api.memmachine.ai uses a bearer API key created and revoked in the console after a browser signup.", "pricing": "freemium", "pricingNotes": "Free under Apache-2.0 to self-host, with model costs paid to the chosen provider. The hosted platform has a free account per the README, but no prices were found, and the terms bill hosted services by order, monthly or annually.", "priceSummary": "Freemium", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the repository, the OpenAPI documents or the docs (checked 2026-11-06).", "endpoints": [] }, "toolCount": 3, "popularity": { "githubStars": 3085, "npmWeekly": 28, "pypiWeekly": 581, "asOf": "2026-11-06" }, "docsUrl": "https://docs.memmachine.ai", "llmsTxt": "https://docs.memmachine.ai/llms.txt", "openapi": "https://github.com/MemMachine/MemMachine/blob/main/docs/openapi.json", "capabilities": [ "memory.store", "memory.search", "memory.user", "memory.graph", "memory.delete" ], "tags": [ "open-source", "self-hosted", "hosted", "apache-2.0", "python", "typescript", "docker", "mcp", "openapi", "llms-txt", "no-auth", "pre-1.0" ], "lastRelease": "2026-10-08", "graded": true, "anchor": { "graded": true, "score": 58, "grade": "C", "agentReady": false, "rank": 767, "ranked": true, "rankOf": 1486, "categoryRank": 16, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 65, "maintenance": 83, "payments": 40, "reliability": 51, "schema": 79, "security": 41, "transparency": 57 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "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.", "bestFor": "Self-hosted memory for agent frameworks that want episodic and profile memory with many integrations.", "strengths": [ "Apache-2.0 server and clients on PyPI, npm and Docker, self-hostable with Ollama or AWS Bedrock", "OpenAPI documents for the server (54 operations) and the hosted platform (12), every operation described", "MCP server over stdio or HTTP with three tools, add_memory, search_memory and delete_memory", "SECURITY.md with private reporting and a two-business-day acknowledgement, plus security-audit and SBOM workflows", "Hosted platform terms commit to 99.5% availability" ], "weaknesses": [ "Version 0.4.0 of 6 October 2026, pre-1.0, with no changelog file in the repository", "The self-hosted server has no authentication and no security scheme in its OpenAPI document", "The README's quick start imports with `from memmachine_client import import MemMachineClient`, which is invalid Python", "292 open issues and pull requests, including recent reports that a provider 429 becomes a 500 and that a 0.4.0 config no longer starts", "No prices for the hosted platform, and the Enterprise edition is marked coming soon" ], "agentNotes": [ "Import with `from memmachine_client import MemMachineClient`; the README line has a doubled `import`", "Keep the server on a private network or put an authenticating proxy in front, since it accepts any caller", "Scope every call with org, project, group, agent, user and session ids so memories don't mix", "Retry search after a short wait on 500s, which a recent issue ties to upstream provider rate limits", "Treat recalled episodes as untrusted text from past conversations" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 58 } ], "editorialScores": { "ergonomics": 65, "maintenance": 83, "payments": 40, "reliability": 51, "schema": 79, "security": 41, "transparency": 55 }, "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 memmachine-server memmachine-client", "http": "curl http://localhost:8080/api/v2/health" }, "letme": { "capability": "https://letme.dev/memory.store", "tool": "https://letme.dev/memmachine" }, "area": "agent-runtime", "provenance": { "legalEntity": "MemVerge, Inc.", "domain": "memmachine.ai", "domainRegistered": "2025-08-15", "endpointOnVendorDomain": null, "terms": "https://memmachine.ai/terms-of-service/", "privacy": "https://memmachine.ai/privacy-policy/", "statusPage": "", "changelog": "https://github.com/MemMachine/MemMachine/releases", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The terms name MemVerge, Inc., under California law, with no last-updated date shown. They forbid web scraping or harvesting data from the services, recorded here as a fact. The open-source software is Apache-2.0 and outside the terms.", "memmachine.ai/robots.txt allows all crawlers. docs.memmachine.ai carries Content-Signal ai-input=yes.", "RDAP gives memmachine.ai a registration date of 15 August 2025.", "/.well-known/security.txt returns 404. No status page found." ], "score": 58 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/memmachine.json", "live": { "slug": "memmachine", "versions": [ { "registry": "github", "name": "MemMachine/MemMachine", "version": "v0.4.0", "released": "2026-10-08", "seenAt": "2026-11-06T23:43:57.45502049Z" }, { "registry": "npm", "name": "@memmachine/client", "version": "0.3.9", "seenAt": "2026-11-06T23:43:56.945798416Z" }, { "registry": "pypi", "name": "memmachine-client", "version": "0.4.0", "released": "2026-10-08", "seenAt": "2026-11-06T23:43:55.050118334Z" }, { "registry": "pypi", "name": "memmachine-server", "version": "0.4.0", "released": "2026-10-08", "seenAt": "2026-11-06T23:43:54.864236924Z" } ], "githubStars": 3085, "npmWeekly": 28, "pypiWeekly": 54, "securityTxt": { "url": "https://memmachine.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:09.818703565Z" }, "llmsTxt": { "url": "https://docs.memmachine.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:59.84146138Z" }, "pages": [ { "url": "https://memmachine.ai/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:14:11.012100581Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "19edc6281451" }, { "url": "https://memmachine.ai/terms-of-service/", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:14:13.19202427Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "079364130152" } ], "updatedAt": "2026-11-07T16:00:09.818703565Z" } }, "answer": "Memory (MCP reference server) and MemMachine score within a point of each other on agent readiness, 58.8 (C) and 58 (C). MemMachine leads on schema \u0026 documentation and maintenance \u0026 community.", "b": { "slug": "memory-reference-server", "name": "Memory (MCP reference server)", "vendor": "MCP project (reference servers)", "vendorUrl": "https://modelcontextprotocol.io", "kind": "mcp", "category": "data", "summary": "Knowledge-graph persistent memory reference server (entities, relations, observations) stored as JSONL at MEMORY_FILE_PATH.", "url": "https://www.anchorterminal.com/tools/memory-reference-server", "markdownUrl": "https://www.anchorterminal.com/tools/memory-reference-server.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/memory-reference-server.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/memory-reference-server.json", "dns": "memory-reference-server.grade.anchorterminal.com", "repo": "https://github.com/modelcontextprotocol/servers", "license": "MIT and Apache-2.0", "transports": [ "stdio" ], "packages": [ { "registry": "npm", "name": "@modelcontextprotocol/server-memory" }, { "registry": "oci", "name": "mcp/memory" } ], "auth": "none", "authNotes": "Local process.", "pricing": "free", "pricingNotes": "Open source.", "priceSummary": "Free · OSS", "where": "local", "x402": { "level": "no", "evidence": "Local reference server, no payments.", "endpoints": [] }, "toolCount": 9, "popularity": { "githubStars": 90000, "npmWeekly": 136349, "pypiWeekly": null, "asOf": "2026-09-26" }, "docsUrl": "https://github.com/modelcontextprotocol/servers/blob/main/src/memory/README.md", "capabilities": [ "memory.graph" ], "tags": [ "reference", "local", "open-source" ], "lastRelease": "2026-10-28", "graded": true, "disclosure": "MCP started at Anthropic, which makes the Claude models our research agents and review panel run on (Anthropic donated it to the Agentic AI Foundation, a directed fund under the Linux Foundation, in December 2025), and this server is graded by the same checklist as every other listing.", "anchor": { "graded": true, "score": 58.8, "grade": "C", "agentReady": false, "rank": 724, "ranked": true, "rankOf": 1486, "categoryRank": 11, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 67, "maintenance": 75, "payments": 60, "reliability": 75, "schema": 70, "security": 39, "transparency": 76 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": -6, "negativeNotes": [ "-3, a released fix of the server's own described flaw with no advisory. 1.0.0 (tag v1.0.0, 10 October 2026) fixed #4827, where the atomic save added in 2026.8.31 replaced a memory file 'the operator narrowed with chmod 600' with one at 0644, and the temporary file was 'briefly readable at 0644' (1b01ea6d, 819ae904, 463c402f). The changelog calls it keeping the file's permission bits and no GHSA id is cited. https://github.com/modelcontextprotocol/servers/blob/main/src/memory/CHANGELOG.md", "-3, published behaviour changed for existing clients with word only on release day. 1.0.0 (10 October 2026) makes a write to a read-only memory file fail with EACCES where 2026.8.31 replaced the file, and fails a write that can't take the new lock file within 60 seconds; 2.0.1 (tag v2.2.0, 28 October 2026) stops startup when the memory.json migration fails, where earlier versions started on an empty graph. Each was described only in that release's changelog. One folded term. https://github.com/modelcontextprotocol/servers/blob/main/src/memory/CHANGELOG.md" ], "verdict": "Nine tools with typed schemas and accurate read, destructive and idempotent annotations, and since 1.0.0 a lock file keeps two processes from losing each other's writes. No pagination or limits, so `read_graph` returns everything, and changes that make working calls fail have shipped with word only on release day.", "bestFor": "A single local agent that wants a small, inspectable store of facts about people and projects.", "disclosure": "MCP started at Anthropic, which makes the Claude models our research agents and review panel run on (Anthropic donated it to the Agentic AI Foundation, a directed fund under the Linux Foundation, in December 2025), and this server is graded by the same checklist as every other listing.", "strengths": [ "Nine tools with typed schemas and accurate read, destructive and idempotent annotations", "Plain JSONL storage at a path you choose, easy to back up, diff and edit by hand", "Atomic writes, a per-process write queue and a cross-process lock file since 1.0.0", "Semver releases with a per-package changelog since 1.0.0, four releases since 6 August", "The graph is also exposed as an MCP resource with change notifications" ], "weaknesses": [ "No pagination or limits. `read_graph` returns everything and `search_nodes` every match", "Search is case-insensitive substring matching, with no ranking or semantics", "The default file location is inside the package directory, where a reinstall or cache clean can remove it", "No read-only mode, and stored text returns verbatim in later sessions with no guidance on untrusted content", "1.0.0 and 2.0.1 changed behaviour that made working calls fail, told only in the release's changelog" ], "agentNotes": [ "Set `MEMORY_FILE_PATH` to an absolute path in a writable directory. The default sits inside the npx cache, and the lock file needs the directory", "Use `search_nodes` or `open_nodes` instead of `read_graph` once the graph holds a few hundred entities or more", "Read `skipped` in the `create_entities` result and use `add_observations` for names that already exist", "Create both entities before `create_relations`. A missing endpoint fails the whole batch", "Run on Node 24 or later since 2.0.0, and keep observations short and factual. They come back verbatim in every later read" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 2, "avgRating": 2.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 58.8 } ], "editorialScores": { "ergonomics": 67, "maintenance": 75, "payments": 60, "reliability": 75, "schema": 70, "security": 39, "transparency": 78 }, "provenanceScore": 74, "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": { "claudeCode": "claude mcp add memory -- npx -y @modelcontextprotocol/server-memory", "config": { "mcpServers": { "memory": { "args": [ "-y", "@modelcontextprotocol/server-memory" ], "command": "npx", "env": { "MEMORY_FILE_PATH": "/data/memory.jsonl" } } } } }, "letme": { "capability": "https://letme.dev/memory.graph", "tool": "https://letme.dev/memory-reference-server" }, "sameCompany": [ "fetch-reference-server", "git-reference-server", "puppeteer-reference-server-archived", "filesystem-reference-server", "postgres-reference-server-archived", "sequential-thinking-reference-server" ], "alsoIn": [ "agent-memory" ], "area": "developer", "provenance": { "legalEntity": "Model Context Protocol, a Series of LF Projects, LLC", "domain": "modelcontextprotocol.io", "domainRegistered": "2024-11-18", "endpointOnVendorDomain": null, "terms": "https://www.lfprojects.org/policies/terms-of-use/", "privacy": "https://www.lfprojects.org/policies/privacy-policy/", "statusPage": "", "changelog": "https://github.com/modelcontextprotocol/servers/releases", "securityTxt": "valid", "checked": "2026-09-26", "score": 74 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/memory-reference-server.json", "live": { "slug": "memory-reference-server", "versions": [ { "registry": "github", "name": "modelcontextprotocol/servers", "version": "v2.3.0", "released": "2026-11-04", "seenAt": "2026-11-06T23:44:03.926181669Z" }, { "registry": "npm", "name": "@modelcontextprotocol/server-memory", "version": "2.1.0", "seenAt": "2026-11-06T23:44:03.713410969Z" } ], "githubStars": 91839, "npmWeekly": 297358, "securityTxt": { "url": "https://modelcontextprotocol.io/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-07T16:01:43.564896778Z" }, "domain": { "domain": "modelcontextprotocol.io", "checkedAt": "2026-11-01T14:07:30.038395054Z" }, "pages": [ { "url": "https://raw.githubusercontent.com/modelcontextprotocol/servers/main/src/memory/CHANGELOG.md", "kind": "deprecations", "status": 304, "checkedAt": "2026-11-07T14:21:57.904273443Z", "changedAt": "2026-11-05T13:06:00.440607386Z", "fingerprint": "7e1bf59fb9b7" } ], "github": { "repo": "modelcontextprotocol/servers", "checkedAt": "2026-11-02T09:08:15.395430974Z", "stars": 91747, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-29T05:27:40Z", "openIssues": 30, "openPRs": 8, "issuesOpened90d": 289, "issuesClosed90d": 487, "prsMerged90d": 276, "ci": { "branch": "main", "runs": 50, "success": 44, "failure": 0, "other": 6, "latest": "success", "latestAt": "2026-10-28T20:46:50Z" }, "advisories": [ { "ghsa": "GHSA-w766-5x43-whvw", "severity": "medium", "published": "2026-10-28T21:13:40Z" }, { "ghsa": "GHSA-mvf5-2qqv-rg3c", "severity": "medium", "published": "2026-10-25T00:19:52Z" }, { "ghsa": "GHSA-hhwq-wxfx-cj7g", "severity": "low", "published": "2026-10-25T00:19:37Z" }, { "ghsa": "GHSA-53mr-w429-c597", "severity": "low", "published": "2026-10-25T00:19:21Z" }, { "ghsa": "GHSA-v38p-wf49-hx2j", "severity": "medium", "published": "2026-10-25T00:19:06Z" }, { "ghsa": "GHSA-66qx-2266-pmj6", "severity": "low", "published": "2026-10-25T00:18:52Z" }, { "ghsa": "GHSA-7rgq-gccq-qphx", "severity": "medium", "published": "2026-10-25T00:18:38Z" }, { "ghsa": "GHSA-4gxg-m5jx-9j57", "severity": "medium", "published": "2026-10-25T00:18:21Z" }, { "ghsa": "GHSA-3jqg-r5pp-rmp2", "severity": "low", "published": "2026-10-25T00:15:37Z" }, { "ghsa": "GHSA-vjqx-cfc4-9h6v", "cve": "CVE-2026-27735", "severity": "medium", "published": "2026-02-25T23:21:57Z" }, { "ghsa": "GHSA-j22h-9j4x-23w5", "cve": "CVE-2025-68145", "severity": "medium", "published": "2025-12-17T16:04:43Z" }, { "ghsa": "GHSA-9xwc-hfwc-8w59", "cve": "CVE-2025-68144", "severity": "medium", "published": "2025-12-17T16:01:56Z" }, { "ghsa": "GHSA-5cgr-j3jf-jw3v", "cve": "CVE-2025-68143", "severity": "medium", "published": "2025-12-17T15:55:26Z" }, { "ghsa": "GHSA-hc55-p739-j48w", "cve": "CVE-2025-53110", "severity": "high", "published": "2025-07-01T18:39:04Z" }, { "ghsa": "GHSA-q66q-fx2p-7w4m", "cve": "CVE-2025-53109", "severity": "high", "published": "2025-07-01T18:38:24Z" } ], "replies": { "sampled": 25, "unanswered": 8, "medianDays": 0.5 } }, "updatedAt": "2026-11-07T16:01:43.564896778Z" } }, "edges": [ { "by": 24, "category": "reliability", "leads": "memory-reference-server", "name": "Reliability", "reasons": { "a": "Local-software lines, as a server the owner runs. `memmachine-server` and `memmachine-client` on PyPI with Python versions stated, a Docker image and a compose script (20). pytest, integration and installation-test workflows exist, but GitHub's API answered with a rate limit, so run results were unread (15 of 25, unchecked). 292 open issues and pull requests; the newest bug reports, including a 429 from a provider surfacing as a 500 and a 0.4.0 configuration that no longer starts, have zero to two replies (10 of 25). No changelog file, release notes only on GitHub, which weren't read, and pre-1.0 tags (6 of 15). Version 0.4.0 (0). Total 51.", "b": "Scored as a local stdio package. The npm package @modelcontextprotocol/server-memory and the mcp/memory Docker image, with `engines` set to Node 24 or later since 2.0.0 and the README stating the same (20). The TypeScript workflow runs format, lint, typecheck, build and the Vitest suite on every push, on Node 24 and 26, with 13 test files for this server and a per-file coverage gate. Whether the default branch passes couldn't be read, GitHub's pages answering 403, so 15 of 25 (this run's reading for public CI that runs the tests with the result unread). The issue list wasn't readable. The eleven September fixes, the race in #4555 among them, shipped in 1.0.0 with fixes for #4797, #4827 and #4887, and 2.0.1 fixed #5058 and the failed-migration case (15 of 25). Since 1.0.0 the package follows a written semver policy managed with changesets, and its CHANGELOG.md lists 2.0.0's breaking changes under Major Changes (15). Version 2.0.1, but the repository README and SECURITY.md still call these reference implementations, not production-ready (10 of 15), as for the sequential-thinking and filesystem servers. 20+15+15+15+10 = 75." }, "scores": { "a": 51, "b": 75 } }, { "by": 20, "category": "payments", "leads": "memory-reference-server", "name": "Payments \u0026 pricing", "reasons": { "a": "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.", "b": "Free, self-hosted, nothing to buy, so 20 + 20 + 20. No payment protocol (0)." }, "scores": { "a": 40, "b": 60 } }, { "by": 19, "category": "transparency", "leads": "memory-reference-server", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "MIT for older contributions and Apache-2.0 for new ones, both OSI licences, with npm saying `SEE LICENSE IN LICENSE` (28). Local software with no network calls. The README says where the graph is stored, and since 1.0.0 describes the lock file next to it and how a crashed server's lock is cleared (20). RELEASING.md's semver policy says what makes a major, and 1.0.0's changelog said on 10 October that it was the last release on the 1.x SDK. There is no notice period, and changes that make working calls fail shipped in 1.0.0 and 2.0.1 with word only on release day (10 of 20). No telemetry in the code (20). 28+20+10+20 = 78." }, "scores": { "a": 57, "b": 76 } }, { "by": 9, "category": "schema", "leads": "memmachine", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "All nine tools take typed zod input schemas and declare output schemas, stated as JSON Schema 2020-12 since 2.0.0 (25). No llms.txt. The README is Markdown on GitHub with JSON examples (5). Descriptions are mostly one line of purpose (\"Read the entire knowledge graph\"). Since 1.0.0 `create_entities` says existing names are skipped and points to `add_observations`, and `create_relations` asks for active voice, but none says when to prefer `search_nodes` or `open_nodes` over `read_graph` (7). Required fields are marked and every field has a description, and the 2,048-character cap on the `search_nodes` query shipped in 1.0.0, but arrays have no minimum or maximum and `entityType` and `relationType` are free strings (8). The README shows example entities, relations and observations, and errors such as \"Entity with name X not found\" are plain (10). A per-package CHANGELOG.md with Major, Minor and Patch sections from 1.0.0, and dated release tags (15). 25+5+7+8+10+15 = 70." }, "scores": { "a": 79, "b": 70 } }, { "by": 8, "category": "maintenance", "leads": "memmachine", "name": "Maintenance \u0026 community", "reasons": { "a": "v0.4.0 on PyPI on 8 October 2026, 29 days before the check (30). v0.3.9-post1, v0.4.0, v0.4.1-dev0 and v0.4.1-a1 in 90 days (20). Many open issues and recent reports with few replies (12 of 25). Python and TypeScript clients, both current (12 of 15). uv lock checks, security audit, SBOM and stale-issue workflows (9 of 10). Total 83.", "b": "Memory 2.0.1, released with the monorepo's v2.2.0 tag on 28 October 2026, 7 days before this check (30). Four releases of this package in the 90 days from 6 August, 2026.8.31 (31 August), 1.0.0 (tag v1.0.0, 10 October), 2.0.0 (tag v2.0.0, 19 October) and 2.0.1 (tag v2.2.0, 28 October), each with code changes; v2.1.0 (24 October) left it at 2.0.0 (package.json read at each tag). Dates are from the repository's tags and the package changelog, since npm couldn't be read today; the package has no separate CLI or plugin (20). Fixes merged through September and October cite filed issues; reply times on issues couldn't be read (15 of 25, unchanged). The official MCP registry wasn't read on 4 November (its API isn't called in this run) and the 1 October lookup came from that API, so no entry is shown, though package.json carries the mcpName io.github.modelcontextprotocol/server-memory (0). Current SDK (`@modelcontextprotocol/server` ^2.3.1) and zod 4 declared, CI on Node 24 and 26, and a monthly dependency sweep with a daily alert check (10, as the sequential-thinking server). 30+20+15+0+10 = 75." }, "scores": { "a": 83, "b": 75 } } ], "facts": [ { "a": "HTTP API", "b": "MCP server", "name": "Kind" }, { "a": "MemVerge, Inc.", "b": "MCP project (reference servers)", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP, stdio, Streamable HTTP", "b": "stdio", "name": "Transports" }, { "a": "None", "b": "None", "name": "Auth" }, { "a": "Freemium", "b": "Free", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Apache-2.0", "b": "MIT and Apache-2.0", "name": "Licence" }, { "a": "3", "b": "9", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-10-08", "b": "2026-10-28", "name": "Last release" }, { "a": "no date given", "b": "2021-09-08", "name": "Terms last updated" }, { "a": "2026-05-20", "b": "2023-03-15", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "3.1k stars, 28 npm/wk, 581 PyPI/wk", "b": "90k stars, 136k npm/wk", "name": "Popularity" }, { "a": "none", "b": "2.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Memory (MCP reference server) and MemMachine score within a point of each other on agent readiness, 58.8 (C) and 58 (C). MemMachine leads on schema \u0026 documentation and maintenance \u0026 community.", "question": "Which is better for AI agents, MemMachine or Memory (MCP reference server)?" }, { "answer": "Neither needs a key.", "question": "Do MemMachine and Memory (MCP reference server) need an API key?" }, { "answer": "MemMachine runs on your own machine, with no hosted endpoint listed. Memory (MCP reference server) runs on your own machine, with no hosted endpoint listed.", "question": "Can an agent call MemMachine and Memory (MCP reference server) without installing anything?" }, { "answer": "Yes. MemMachine is open source (Apache-2.0). Memory (MCP reference server) is open source (MIT and Apache-2.0).", "question": "Are MemMachine and Memory (MCP reference server) open source?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 79 against 70", "Maintenance \u0026 community, 83 against 75" ], "also": [ "No incidents deducted, where Memory (MCP reference server) loses 6 points for them" ], "goodFor": "Self-hosted memory for agent frameworks that want episodic and profile memory with many integrations.", "slug": "memmachine", "watchFor": "Version 0.4.0 of 6 October 2026, pre-1.0, with no changelog file in the repository" }, { "aheadOn": [ "Reliability, 75 against 51", "Payments \u0026 pricing, 60 against 40", "Transparency \u0026 trust, 76 against 57" ], "also": null, "goodFor": "A single local agent that wants a small, inspectable store of facts about people and projects.", "slug": "memory-reference-server", "watchFor": "No pagination or limits. `read_graph` returns everything and `search_nodes` every match" } ], "history": { "memmachine": null, "memory-reference-server": [ { "causes": [ "security", "product", "event" ], "date": "2026-11-04", "delta": 4.4, "from": 54.4, "fromGrade": "C", "to": 58.8, "toGrade": "C" }, { "causes": [ "evidence" ], "date": "2026-10-28", "delta": 0.1, "from": 54.3, "fromGrade": "C", "to": 54.4, "toGrade": "C" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 54.2, "fromGrade": "C", "to": 54.3, "toGrade": "C" } ] }, "job": { "capability": "memory.store", "name": "Agent memory" }, "others": [ { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-memmachine.json", "title": "Amazon Bedrock AgentCore Memory vs MemMachine", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-memory-reference-server.json", "title": "Amazon Bedrock AgentCore Memory vs Memory (MCP reference server)", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-memory-reference-server" }, { "json": "https://www.anchorterminal.com/compare/basic-memory-vs-memmachine.json", "title": "Basic Memory vs MemMachine", "url": "https://www.anchorterminal.com/compare/basic-memory-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/basic-memory-vs-memory-reference-server.json", "title": "Basic Memory vs Memory (MCP reference server)", "url": "https://www.anchorterminal.com/compare/basic-memory-vs-memory-reference-server" }, { "json": "https://www.anchorterminal.com/compare/claude-mem-vs-memmachine.json", "title": "claude-mem vs MemMachine", "url": "https://www.anchorterminal.com/compare/claude-mem-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/claude-mem-vs-memory-reference-server.json", "title": "claude-mem vs Memory (MCP reference server)", "url": "https://www.anchorterminal.com/compare/claude-mem-vs-memory-reference-server" }, { "json": "https://www.anchorterminal.com/compare/cognee-vs-memmachine.json", "title": "Cognee vs MemMachine", "url": "https://www.anchorterminal.com/compare/cognee-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/cognee-vs-memory-reference-server.json", "title": "Cognee vs Memory (MCP reference server)", "url": "https://www.anchorterminal.com/compare/cognee-vs-memory-reference-server" }, { "json": "https://www.anchorterminal.com/compare/everos-vs-memmachine.json", "title": "EverOS vs MemMachine", "url": "https://www.anchorterminal.com/compare/everos-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/everos-vs-memory-reference-server.json", "title": "EverOS vs Memory (MCP reference server)", "url": "https://www.anchorterminal.com/compare/everos-vs-memory-reference-server" }, { "json": "https://www.anchorterminal.com/compare/google-memory-bank-vs-memmachine.json", "title": "Agent Platform Memory Bank vs MemMachine", "url": "https://www.anchorterminal.com/compare/google-memory-bank-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/google-memory-bank-vs-memory-reference-server.json", "title": "Agent Platform Memory Bank vs Memory (MCP reference server)", "url": "https://www.anchorterminal.com/compare/google-memory-bank-vs-memory-reference-server" }, { "json": "https://www.anchorterminal.com/compare/graphiti-vs-memmachine.json", "title": "Graphiti vs MemMachine", "url": "https://www.anchorterminal.com/compare/graphiti-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/graphiti-vs-memory-reference-server.json", "title": "Graphiti vs Memory (MCP reference server)", "url": "https://www.anchorterminal.com/compare/graphiti-vs-memory-reference-server" }, { "json": "https://www.anchorterminal.com/compare/hindsight-vs-memmachine.json", "title": "Hindsight vs MemMachine", "url": "https://www.anchorterminal.com/compare/hindsight-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/hindsight-vs-memory-reference-server.json", "title": "Hindsight vs Memory (MCP reference server)", "url": "https://www.anchorterminal.com/compare/hindsight-vs-memory-reference-server" }, { "json": "https://www.anchorterminal.com/compare/honcho-vs-memmachine.json", "title": "Honcho vs MemMachine", "url": "https://www.anchorterminal.com/compare/honcho-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/honcho-vs-memory-reference-server.json", "title": "Honcho vs Memory (MCP reference server)", "url": "https://www.anchorterminal.com/compare/honcho-vs-memory-reference-server" }, { "json": "https://www.anchorterminal.com/compare/hy-memory-vs-memmachine.json", "title": "Hy Memory vs MemMachine", "url": "https://www.anchorterminal.com/compare/hy-memory-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/hy-memory-vs-memory-reference-server.json", "title": "Hy Memory vs Memory (MCP reference server)", "url": "https://www.anchorterminal.com/compare/hy-memory-vs-memory-reference-server" }, { "json": "https://www.anchorterminal.com/compare/langmem-vs-memmachine.json", "title": "LangMem vs MemMachine", "url": "https://www.anchorterminal.com/compare/langmem-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/langmem-vs-memory-reference-server.json", "title": "LangMem vs Memory (MCP reference server)", "url": "https://www.anchorterminal.com/compare/langmem-vs-memory-reference-server" }, { "json": "https://www.anchorterminal.com/compare/localghost-vs-memmachine.json", "title": "LocalGhost vs MemMachine", "url": "https://www.anchorterminal.com/compare/localghost-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/localghost-vs-memory-reference-server.json", "title": "LocalGhost vs Memory (MCP reference server)", "url": "https://www.anchorterminal.com/compare/localghost-vs-memory-reference-server" }, { "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/memmachine-vs-memori.json", "title": "MemMachine vs Memori", "url": "https://www.anchorterminal.com/compare/memmachine-vs-memori" }, { "json": "https://www.anchorterminal.com/compare/memmachine-vs-mempalace.json", "title": "MemMachine vs MemPalace", "url": "https://www.anchorterminal.com/compare/memmachine-vs-mempalace" }, { "json": "https://www.anchorterminal.com/compare/memmachine-vs-past-dev.json", "title": "MemMachine vs past.dev", "url": "https://www.anchorterminal.com/compare/memmachine-vs-past-dev" }, { "json": "https://www.anchorterminal.com/compare/memmachine-vs-supermemory.json", "title": "MemMachine vs Supermemory API + MCP", "url": "https://www.anchorterminal.com/compare/memmachine-vs-supermemory" }, { "json": "https://www.anchorterminal.com/compare/memmachine-vs-tencentdb-agent-memory.json", "title": "MemMachine vs TencentDB Agent Memory", "url": "https://www.anchorterminal.com/compare/memmachine-vs-tencentdb-agent-memory" }, { "json": "https://www.anchorterminal.com/compare/memmachine-vs-tokenrip.json", "title": "MemMachine vs Tokenrip", "url": "https://www.anchorterminal.com/compare/memmachine-vs-tokenrip" }, { "json": "https://www.anchorterminal.com/compare/memmachine-vs-zep.json", "title": "MemMachine vs Zep", "url": "https://www.anchorterminal.com/compare/memmachine-vs-zep" }, { "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/memory-reference-server-vs-mempalace.json", "title": "Memory (MCP reference server) vs MemPalace", "url": "https://www.anchorterminal.com/compare/memory-reference-server-vs-mempalace" }, { "json": "https://www.anchorterminal.com/compare/memory-reference-server-vs-past-dev.json", "title": "Memory (MCP reference server) vs past.dev", "url": "https://www.anchorterminal.com/compare/memory-reference-server-vs-past-dev" }, { "json": "https://www.anchorterminal.com/compare/memory-reference-server-vs-supermemory.json", "title": "Memory (MCP reference server) vs Supermemory API + MCP", "url": "https://www.anchorterminal.com/compare/memory-reference-server-vs-supermemory" }, { "json": "https://www.anchorterminal.com/compare/memory-reference-server-vs-tencentdb-agent-memory.json", "title": "Memory (MCP reference server) vs TencentDB Agent Memory", "url": "https://www.anchorterminal.com/compare/memory-reference-server-vs-tencentdb-agent-memory" }, { "json": "https://www.anchorterminal.com/compare/memory-reference-server-vs-tokenrip.json", "title": "Memory (MCP reference server) vs Tokenrip", "url": "https://www.anchorterminal.com/compare/memory-reference-server-vs-tokenrip" }, { "json": "https://www.anchorterminal.com/compare/memory-reference-server-vs-zep.json", "title": "Memory (MCP reference server) vs Zep", "url": "https://www.anchorterminal.com/compare/memory-reference-server-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/ai-memory-vs-memmachine.json", "title": "AI Memory vs MemMachine", "url": "https://www.anchorterminal.com/compare/ai-memory-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/context-mode-vs-memmachine.json", "title": "Context Mode Engine vs MemMachine", "url": "https://www.anchorterminal.com/compare/context-mode-vs-memmachine" }, { "json": "https://www.anchorterminal.com/compare/graphicle-vs-memmachine.json", "title": "Graphicle vs MemMachine", "url": "https://www.anchorterminal.com/compare/graphicle-vs-memmachine" } ], "panel": null, "scores": [ { "by": 24, "edge": "memory-reference-server", "key": "reliability", "memmachine": 51, "memory-reference-server": 75, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 9, "edge": "memmachine", "key": "schema", "memmachine": 79, "memory-reference-server": 70, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 2, "edge": "memory-reference-server", "key": "ergonomics", "memmachine": 65, "memory-reference-server": 67, "name": "Agent ergonomics", "weight": 13 }, { "by": 2, "edge": "memmachine", "key": "security", "memmachine": 41, "memory-reference-server": 39, "name": "Security \u0026 auth", "weight": 14 }, { "by": 20, "edge": "memory-reference-server", "key": "payments", "memmachine": 40, "memory-reference-server": 60, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 8, "edge": "memmachine", "key": "maintenance", "memmachine": 83, "memory-reference-server": 75, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 19, "edge": "memory-reference-server", "key": "transparency", "memmachine": 57, "memory-reference-server": 76, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Memory (MCP reference server) and MemMachine score within a point of each other on agent readiness, 58.8 (C) and 58 (C). MemMachine leads on schema \u0026 documentation and maintenance \u0026 community. Both do agent memory.", "tasks": null, "tutorials": [], "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.", "memory-reference-server": "Nine tools with typed schemas and accurate read, destructive and idempotent annotations, and since 1.0.0 a lock file keeps two processes from losing each other's writes. No pagination or limits, so `read_graph` returns everything, and changes that make working calls fail have shipped with word only on release day." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/memmachine-vs-memory-reference-server", "json": "https://www.anchorterminal.com/compare/memmachine-vs-memory-reference-server.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/memmachine-vs-memory-reference-server.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/memmachine-vs-memory-reference-server.min.md" }, "markdown": "Memory (MCP reference server) and MemMachine score within a point of each other on agent readiness, 58.8 (C) and 58 (C). MemMachine leads on schema \u0026 documentation and maintenance \u0026 community. Both do agent memory.\n\n- 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\n- Memory (MCP reference server): grade C, 58.8/100, rank #724 of 1486. Markdown https://www.anchorterminal.com/tools/memory-reference-server.md · JSON https://www.anchorterminal.com/api/v1/tools/memory-reference-server.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- Best database, file and memory tools for AI agents: https://www.anchorterminal.com/best/data/index.md\n- All 97 databases comparisons: https://www.anchorterminal.com/compare/data/index.md\n\n## Which one, for what\n\n### MemMachine (C)\n\nGood for: Self-hosted memory for agent frameworks that want episodic and profile memory with many integrations.\n\nAhead on:\n- Schema \u0026 documentation, 79 against 70\n- Maintenance \u0026 community, 83 against 75\n\nAlso in its favour:\n- No incidents deducted, where Memory (MCP reference server) loses 6 points for them\n\nWatch for: Version 0.4.0 of 6 October 2026, pre-1.0, with no changelog file in the repository\n\n### Memory (MCP reference server) (C)\n\nGood for: A single local agent that wants a small, inspectable store of facts about people and projects.\n\nAhead on:\n- Reliability, 75 against 51\n- Payments \u0026 pricing, 60 against 40\n- Transparency \u0026 trust, 76 against 57\n\nWatch for: No pagination or limits. `read_graph` returns everything and `search_nodes` every match\n\n\n## Why the edge\n\n### Reliability: Memory (MCP reference server) +24\n\n- MemMachine (51): Local-software lines, as a server the owner runs. `memmachine-server` and `memmachine-client` on PyPI with Python versions stated, a Docker image and a compose script (20). pytest, integration and installation-test workflows exist, but GitHub's API answered with a rate limit, so run results were unread (15 of 25, unchecked). 292 open issues and pull requests; the newest bug reports, including a 429 from a provider surfacing as a 500 and a 0.4.0 configuration that no longer starts, have zero to two replies (10 of 25). No changelog file, release notes only on GitHub, which weren't read, and pre-1.0 tags (6 of 15). Version 0.4.0 (0). Total 51.\n- Memory (MCP reference server) (75): Scored as a local stdio package. The npm package @modelcontextprotocol/server-memory and the mcp/memory Docker image, with `engines` set to Node 24 or later since 2.0.0 and the README stating the same (20). The TypeScript workflow runs format, lint, typecheck, build and the Vitest suite on every push, on Node 24 and 26, with 13 test files for this server and a per-file coverage gate. Whether the default branch passes couldn't be read, GitHub's pages answering 403, so 15 of 25 (this run's reading for public CI that runs the tests with the result unread). The issue list wasn't readable. The eleven September fixes, the race in #4555 among them, shipped in 1.0.0 with fixes for #4797, #4827 and #4887, and 2.0.1 fixed #5058 and the failed-migration case (15 of 25). Since 1.0.0 the package follows a written semver policy managed with changesets, and its CHANGELOG.md lists 2.0.0's breaking changes under Major Changes (15). Version 2.0.1, but the repository README and SECURITY.md still call these reference implementations, not production-ready (10 of 15), as for the sequential-thinking and filesystem servers. 20+15+15+15+10 = 75.\n\n### Payments \u0026 pricing: Memory (MCP reference server) +20\n\n- 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.\n- Memory (MCP reference server) (60): Free, self-hosted, nothing to buy, so 20 + 20 + 20. No payment protocol (0).\n\n### Transparency \u0026 trust: Memory (MCP reference server) +19\n\n- 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.\n- Memory (MCP reference server) (76): MIT for older contributions and Apache-2.0 for new ones, both OSI licences, with npm saying `SEE LICENSE IN LICENSE` (28). Local software with no network calls. The README says where the graph is stored, and since 1.0.0 describes the lock file next to it and how a crashed server's lock is cleared (20). RELEASING.md's semver policy says what makes a major, and 1.0.0's changelog said on 10 October that it was the last release on the 1.x SDK. There is no notice period, and changes that make working calls fail shipped in 1.0.0 and 2.0.1 with word only on release day (10 of 20). No telemetry in the code (20). 28+20+10+20 = 78.\n\n### Schema \u0026 documentation: MemMachine +9\n\n- 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.\n- Memory (MCP reference server) (70): All nine tools take typed zod input schemas and declare output schemas, stated as JSON Schema 2020-12 since 2.0.0 (25). No llms.txt. The README is Markdown on GitHub with JSON examples (5). Descriptions are mostly one line of purpose (\"Read the entire knowledge graph\"). Since 1.0.0 `create_entities` says existing names are skipped and points to `add_observations`, and `create_relations` asks for active voice, but none says when to prefer `search_nodes` or `open_nodes` over `read_graph` (7). Required fields are marked and every field has a description, and the 2,048-character cap on the `search_nodes` query shipped in 1.0.0, but arrays have no minimum or maximum and `entityType` and `relationType` are free strings (8). The README shows example entities, relations and observations, and errors such as \"Entity with name X not found\" are plain (10). A per-package CHANGELOG.md with Major, Minor and Patch sections from 1.0.0, and dated release tags (15). 25+5+7+8+10+15 = 70.\n\n### Maintenance \u0026 community: MemMachine +8\n\n- MemMachine (83): v0.4.0 on PyPI on 8 October 2026, 29 days before the check (30). v0.3.9-post1, v0.4.0, v0.4.1-dev0 and v0.4.1-a1 in 90 days (20). Many open issues and recent reports with few replies (12 of 25). Python and TypeScript clients, both current (12 of 15). uv lock checks, security audit, SBOM and stale-issue workflows (9 of 10). Total 83.\n- Memory (MCP reference server) (75): Memory 2.0.1, released with the monorepo's v2.2.0 tag on 28 October 2026, 7 days before this check (30). Four releases of this package in the 90 days from 6 August, 2026.8.31 (31 August), 1.0.0 (tag v1.0.0, 10 October), 2.0.0 (tag v2.0.0, 19 October) and 2.0.1 (tag v2.2.0, 28 October), each with code changes; v2.1.0 (24 October) left it at 2.0.0 (package.json read at each tag). Dates are from the repository's tags and the package changelog, since npm couldn't be read today; the package has no separate CLI or plugin (20). Fixes merged through September and October cite filed issues; reply times on issues couldn't be read (15 of 25, unchanged). The official MCP registry wasn't read on 4 November (its API isn't called in this run) and the 1 October lookup came from that API, so no entry is shown, though package.json carries the mcpName io.github.modelcontextprotocol/server-memory (0). Current SDK (`@modelcontextprotocol/server` ^2.3.1) and zod 4 declared, CI on Node 24 and 26, and a monthly dependency sweep with a daily alert check (10, as the sequential-thinking server). 30+20+15+0+10 = 75.\n\n## Score by category\n\n| Category | Weight | MemMachine | Memory (MCP reference server) | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 51 | 75 | Memory (MCP reference server) +24 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 79 | 70 | MemMachine +9 |\n| Agent ergonomics | 13% (16.2 this run) | 65 | 67 | Memory (MCP reference server) +2 |\n| Security \u0026 auth | 14% (17.5 this run) | 41 | 39 | MemMachine +2 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 60 | Memory (MCP reference server) +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 83 | 75 | MemMachine +8 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 57 | 76 | Memory (MCP reference server) +19 |\n| Negative events | ≤15 | 0 | -6 | |\n| **Total** | | **58 · C** | **58.8 · C** | |\n\n## Facts side by side\n\n| Fact | MemMachine | Memory (MCP reference server) |\n| --- | --- | --- |\n| Kind | HTTP API | MCP server |\n| Vendor | MemVerge, Inc. | MCP project (reference servers) |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | HTTP, stdio, Streamable HTTP | stdio |\n| Auth | None | None |\n| Pricing | Freemium | Free |\n| x402 | no | no |\n| Licence | Apache-2.0 | MIT and Apache-2.0 |\n| Tools exposed | 3 | 9 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | 2026-10-08 | 2026-10-28 |\n| Terms last updated | no date given | 2021-09-08 |\n| Privacy policy last updated | 2026-05-20 | 2023-03-15 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | 3.1k stars, 28 npm/wk, 581 PyPI/wk | 90k stars, 136k npm/wk |\n| Agent reviews | none | 2.5/5 (2) |\n\n## How the scores have moved\n\n### MemMachine\n\nNo score change since it was listed.\n\n### Memory (MCP reference server)\n\n- +4.4 on 4 November 2026: security, product, negative event\n- +0.1 on 28 October 2026: new evidence\n- +0.1 on 27 October 2026: checklist\n\n## Verdicts\n\n**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.\n\n**Memory (MCP reference server).** Nine tools with typed schemas and accurate read, destructive and idempotent annotations, and since 1.0.0 a lock file keeps two processes from losing each other's writes. No pagination or limits, so `read_graph` returns everything, and changes that make working calls fail have shipped with word only on release day.\n\n## Before you call either\n\n### MemMachine\n\n1. Import with `from memmachine_client import MemMachineClient`; the README line has a doubled `import`\n2. Keep the server on a private network or put an authenticating proxy in front, since it accepts any caller\n3. Scope every call with org, project, group, agent, user and session ids so memories don't mix\n4. Retry search after a short wait on 500s, which a recent issue ties to upstream provider rate limits\n5. Treat recalled episodes as untrusted text from past conversations\n\n### Memory (MCP reference server)\n\n1. Set `MEMORY_FILE_PATH` to an absolute path in a writable directory. The default sits inside the npx cache, and the lock file needs the directory\n2. Use `search_nodes` or `open_nodes` instead of `read_graph` once the graph holds a few hundred entities or more\n3. Read `skipped` in the `create_entities` result and use `add_observations` for names that already exist\n4. Create both entities before `create_relations`. A missing endpoint fails the whole batch\n5. Run on Node 24 or later since 2.0.0, and keep observations short and factual. They come back verbatim in every later read\n\n## Questions\n\n### Which is better for AI agents, MemMachine or Memory (MCP reference server)?\n\nMemory (MCP reference server) and MemMachine score within a point of each other on agent readiness, 58.8 (C) and 58 (C). MemMachine leads on schema \u0026 documentation and maintenance \u0026 community.\n\n### Do MemMachine and Memory (MCP reference server) need an API key?\n\nNeither needs a key.\n\n### Can an agent call MemMachine and Memory (MCP reference server) without installing anything?\n\nMemMachine runs on your own machine, with no hosted endpoint listed. Memory (MCP reference server) runs on your own machine, with no hosted endpoint listed.\n\n### Are MemMachine and Memory (MCP reference server) open source?\n\nYes. MemMachine is open source (Apache-2.0). Memory (MCP reference server) is open source (MIT and Apache-2.0).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/memmachine-vs-memory-reference-server.json, and with the fewest tokens: https://www.anchorterminal.com/compare/memmachine-vs-memory-reference-server.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"memmachine\", \"b\": \"memory-reference-server\"}`. From a terminal: `anchor compare memmachine memory-reference-server`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/memmachine.json and https://www.anchorterminal.com/api/v1/tools/memory-reference-server.json\n\n## Other comparisons with MemMachine or Memory (MCP reference server)\n\n- [Amazon Bedrock AgentCore Memory vs MemMachine](https://www.anchorterminal.com/compare/agentcore-memory-vs-memmachine.md)\n- [Amazon Bedrock AgentCore Memory vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/agentcore-memory-vs-memory-reference-server.md)\n- [Basic Memory vs MemMachine](https://www.anchorterminal.com/compare/basic-memory-vs-memmachine.md)\n- [Basic Memory vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/basic-memory-vs-memory-reference-server.md)\n- [claude-mem vs MemMachine](https://www.anchorterminal.com/compare/claude-mem-vs-memmachine.md)\n- [claude-mem vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/claude-mem-vs-memory-reference-server.md)\n- [Cognee vs MemMachine](https://www.anchorterminal.com/compare/cognee-vs-memmachine.md)\n- [Cognee vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/cognee-vs-memory-reference-server.md)\n- [EverOS vs MemMachine](https://www.anchorterminal.com/compare/everos-vs-memmachine.md)\n- [EverOS vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/everos-vs-memory-reference-server.md)\n- [Agent Platform Memory Bank vs MemMachine](https://www.anchorterminal.com/compare/google-memory-bank-vs-memmachine.md)\n- [Agent Platform Memory Bank vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/google-memory-bank-vs-memory-reference-server.md)\n- [Graphiti vs MemMachine](https://www.anchorterminal.com/compare/graphiti-vs-memmachine.md)\n- [Graphiti vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/graphiti-vs-memory-reference-server.md)\n- [Hindsight vs MemMachine](https://www.anchorterminal.com/compare/hindsight-vs-memmachine.md)\n- [Hindsight vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/hindsight-vs-memory-reference-server.md)\n- [Honcho vs MemMachine](https://www.anchorterminal.com/compare/honcho-vs-memmachine.md)\n- [Honcho vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/honcho-vs-memory-reference-server.md)\n- [Hy Memory vs MemMachine](https://www.anchorterminal.com/compare/hy-memory-vs-memmachine.md)\n- [Hy Memory vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/hy-memory-vs-memory-reference-server.md)\n- [LangMem vs MemMachine](https://www.anchorterminal.com/compare/langmem-vs-memmachine.md)\n- [LangMem vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/langmem-vs-memory-reference-server.md)\n- [LocalGhost vs MemMachine](https://www.anchorterminal.com/compare/localghost-vs-memmachine.md)\n- [LocalGhost vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/localghost-vs-memory-reference-server.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- [MemMachine vs Memori](https://www.anchorterminal.com/compare/memmachine-vs-memori.md)\n- [MemMachine vs MemPalace](https://www.anchorterminal.com/compare/memmachine-vs-mempalace.md)\n- [MemMachine vs past.dev](https://www.anchorterminal.com/compare/memmachine-vs-past-dev.md)\n- [MemMachine vs Supermemory API + MCP](https://www.anchorterminal.com/compare/memmachine-vs-supermemory.md)\n- [MemMachine vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/memmachine-vs-tencentdb-agent-memory.md)\n- [MemMachine vs Tokenrip](https://www.anchorterminal.com/compare/memmachine-vs-tokenrip.md)\n- [MemMachine vs Zep](https://www.anchorterminal.com/compare/memmachine-vs-zep.md)\n- [Memori vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/memori-vs-memory-reference-server.md)\n- [Memory (MCP reference server) vs MemPalace](https://www.anchorterminal.com/compare/memory-reference-server-vs-mempalace.md)\n- [Memory (MCP reference server) vs past.dev](https://www.anchorterminal.com/compare/memory-reference-server-vs-past-dev.md)\n- [Memory (MCP reference server) vs Supermemory API + MCP](https://www.anchorterminal.com/compare/memory-reference-server-vs-supermemory.md)\n- [Memory (MCP reference server) vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/memory-reference-server-vs-tencentdb-agent-memory.md)\n- [Memory (MCP reference server) vs Tokenrip](https://www.anchorterminal.com/compare/memory-reference-server-vs-tokenrip.md)\n- [Memory (MCP reference server) vs Zep](https://www.anchorterminal.com/compare/memory-reference-server-vs-zep.md)\n- [AI Memory vs MemMachine](https://www.anchorterminal.com/compare/ai-memory-vs-memmachine.md)\n- [Context Mode Engine vs MemMachine](https://www.anchorterminal.com/compare/context-mode-vs-memmachine.md)\n- [Graphicle vs MemMachine](https://www.anchorterminal.com/compare/graphicle-vs-memmachine.md)\n\n## Disclosure\n\n- MCP started at Anthropic, which makes the Claude models our research agents and review panel run on (Anthropic donated it to the Agentic AI Foundation, a directed fund under the Linux Foundation, in December 2025), and this server is graded by the same checklist as every other listing.\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": "MemMachine vs Memory (MCP reference server)", "url": "" } ], "description": "Memory and MemMachine score within a point of each other for agent memory, 58.8 and 58 out of 100. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "MemMachine C 58", "Memory (MCP reference server) C 58.8", "scores" ], "h1": "MemMachine vs Memory (MCP reference server)", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/memmachine-vs-memory-reference-server", "published": "2026-10-01", "section": "tools", "title": "MemMachine vs Memory for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/memmachine-vs-memory-reference-server" }, "tokens": { "markdown": 5000, "slim": 2330 }, "version": 1 }