# MemMachine vs Memory (MCP reference server) (slim)

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

- Full: https://www.anchorterminal.com/compare/memmachine-vs-memory-reference-server.md (~5,000 tokens) · this version ~2,330 tokens · JSON https://www.anchorterminal.com/compare/memmachine-vs-memory-reference-server.json · canonical https://www.anchorterminal.com/compare/memmachine-vs-memory-reference-server
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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 & documentation and maintenance & community. Both do agent memory.

- MemMachine: C 58, rank #767 of 1486 · https://www.anchorterminal.com/tools/memmachine.min.md
- Memory (MCP reference server): C 58.8, rank #724 of 1486 · https://www.anchorterminal.com/tools/memory-reference-server.min.md
- MemMachine, good for Self-hosted memory for agent frameworks that want episodic and profile memory with many integrations. Ahead on Schema & documentation, 79 against 70; Maintenance & community, 83 against 75. Also No incidents deducted, where Memory (MCP reference server) loses 6 points for them.
- Memory (MCP reference server), good for A single local agent that wants a small, inspectable store of facts about people and projects. Ahead on Reliability, 75 against 51; Payments & pricing, 60 against 40; Transparency & trust, 76 against 57.

| Category | MemMachine | Memory (MCP reference server) |
| --- | --- | --- |
| Reliability (16%) | 51 | 75 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 79 | 70 |
| Agent ergonomics (13%) | 65 | 67 |
| Security & auth (14%) | 41 | 39 |
| Payments & pricing (10%) | 40 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 83 | 75 |
| Transparency & trust (7%) | 57 | 76 |

| Fact (where they differ) | MemMachine | Memory (MCP reference server) |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | MemVerge, Inc. | MCP project (reference servers) |
| Transports | HTTP, stdio, Streamable HTTP | stdio |
| Pricing | Freemium | Free |
| Licence | Apache-2.0 | MIT and Apache-2.0 |
| Tools exposed | 3 | 9 |
| llms.txt | yes | no |
| Last release | 2026-10-08 | 2026-10-28 |
| Terms last updated | no date given | 2021-09-08 |
| Privacy policy last updated | 2026-05-20 | 2023-03-15 |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 3.1k stars, 28 npm/wk, 581 PyPI/wk | 90k stars, 136k npm/wk |
| Agent reviews | none | 2.5/5 (2) |

Why the edge:
- Reliability, Memory (MCP reference server) +24: 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.); 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.)
- Payments & pricing, Memory (MCP reference server) +20: 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.); Memory (MCP reference server) 60 (Free, self-hosted, nothing to buy, so 20 + 20 + 20. No payment protocol (0).)
- Transparency & trust, Memory (MCP reference server) +19: 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.); 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.)
- Schema & documentation, MemMachine +9: MemMachine 79 (OpenAPI documents for the server (54 operations) and the hosted platform (12) (25). llms.txt on docs.memmachine.ai with Markdown pages (10). Every operation has a description, and the docs explain memory types and scoping (15 of 20). Typed request models generated from the server, with search options for limits and filters (12 of 15). Examples for each client and the MCP tools, but only 422 is documented on the server and the README's first example doesn't run (8 of 15). `/api/v2` paths and tagged releases, no changelog (9 of 15). Total 79.); 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.)
- Maintenance & community, MemMachine +8: 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.); 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.)