# MemMachine vs Tokenrip (slim)

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

- Full: https://www.anchorterminal.com/compare/memmachine-vs-tokenrip.md (~5,550 tokens) · this version ~3,230 tokens · JSON https://www.anchorterminal.com/compare/memmachine-vs-tokenrip.json · canonical https://www.anchorterminal.com/compare/memmachine-vs-tokenrip
- 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)

Tokenrip scores 60.3 (C) on agent readiness against MemMachine's 58 (C), and leads in 6 of 7 scored categories. MemMachine leads on maintenance & community. Both do agent memory.

- MemMachine: C 58, rank #767 of 1486 · https://www.anchorterminal.com/tools/memmachine.min.md
- Tokenrip: C 60.3, rank #654 of 1486 · https://www.anchorterminal.com/tools/tokenrip.min.md
- MemMachine, good for Self-hosted memory for agent frameworks that want episodic and profile memory with many integrations. Ahead on Maintenance & community, 83 against 75. Also No key needed to call it; Runs on your own machine; Open source; No incidents deducted, where Tokenrip loses 9 points for them.
- Tokenrip, good for Small teams, or one person with several agents in different tools (Claude, ChatGPT, Codex, Cursor, Grok), who want one place for shared files, tasks, decisions and handoffs with a person approving outside actions. Ahead on Reliability, 57 against 51; Schema & documentation, 93 against 79; Agent ergonomics, 70 against 65; Security & auth, 71 against 41; Payments & pricing, 50 against 40; Transparency & trust, 71 against 57. Also A hosted endpoint, with nothing to install; Free to start without a card.

| Category | MemMachine | Tokenrip |
| --- | --- | --- |
| Reliability (16%) | 51 | 57 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 79 | 93 |
| Agent ergonomics (13%) | 65 | 70 |
| Security & auth (14%) | 41 | 71 |
| Payments & pricing (10%) | 40 | 50 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 83 | 75 |
| Transparency & trust (7%) | 57 | 71 |

| Fact (where they differ) | MemMachine | Tokenrip |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | MemVerge, Inc. | Quintel, LLC |
| Hosted endpoint | no (local only) | `https://api.tokenrip.com/mcp` |
| Transports | HTTP, stdio, Streamable HTTP | Streamable HTTP, HTTP |
| Auth | None | OAuth or key |
| Licence | Apache-2.0 | Proprietary hosted service under Tokenrip's terms of service (Quintel, LLC, Texas law). The `rip` CLI and library `@tokenrip/cli` is MIT-licensed on GitHub |
| Tools exposed | 3 | 98 |
| MCP registry | not listed | `io.github.silostack/tokenrip` |
| Last release | 2026-10-08 | 2026-11-02 |
| Terms last updated | no date given | 2026-10-16 |
| Privacy policy last updated | 2026-05-20 | 2026-10-16 |
| 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 | 5 stars, 401 npm/wk |
| Agent reviews | none | 3.8/5 (4) |

Why the edge:
- Security & auth, Tokenrip +30: MemMachine 41 (Framework reading for software the owner runs. The server has no authentication and no security scheme in its OpenAPI document (15 of 30). No read-only mode or confirmation for deletes (5 of 20). No guidance on recalled memories as untrusted text (4 of 15). No audit log on the self-hosted server; the hosted console shows usage (5 of 15). SECURITY.md with GitHub private reporting and a two-business-day acknowledgement, with security-audit and SBOM workflows; no security.txt or certification (12 of 20). Total 41.); Tokenrip 71 (OAuth 2.1 for MCP with PKCE S256, 25 read and write scopes requested per tool, opaque access tokens and rotating refresh tokens whose replay revokes the family. Each agent has its own key, revocable on its own and rotatable, and run keys expire within 24 hours and can't manage keys. But `tr_` API keys have full access to the account, with no read-only or scoped key (25 of 30). Tools are classed Sensitive where they delete, widen visibility or call outside, and the docs ask hosts to confirm those. Actions outside the workspace go through `task_propose` for approval, and only the person writes an agent's instructions. A pasted key can still do anything (15 of 20). Shared workspaces return text written by other people's agents and external members. The setup guide and notices tell agents never to act on an email or use a code from a web page or document, but we found no general guidance on treating workspace content as untrusted (9 of 15). Every action is recorded with the agent, the tool it ran in and its reason, connections have per-call logs, and the Agents page shows each key's last use (15). Since 31 October a security page and a security.txt (Expires 3 May 2027) name security@tokenrip.com, and the CLI's SECURITY.md, updated on 2 November, points to the public repository. SECURITY.md takes private reports by email or a GitHub private advisory, with no acknowledgement time. No bug bounty, no certifications, no published advisories. The security page and the privacy policy of 3 November say affected people are told of a confirmed incident as the law and agreements require, where the 21 October policy promised 48 hours. Read against mails-ai (7, valid security.txt and a disclosure policy, no reply commitment) and blockrun-ai (10, valid security.txt and a 72-hour acknowledgement) (7 of 20).)
- Schema & documentation, Tokenrip +14: 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.); Tokenrip 93 (OpenAPI 3.1.0 at api.tokenrip.com/v0/openapi.json with 111 paths and 144 operations, which the docs say is the same contract as each MCP tool's input. The MCP tool schemas themselves weren't read, because no session was opened (25, per the 21 October reading of the file). llms.txt on tokenrip.com and docs.tokenrip.com, every docs page as Markdown, and `Accept: text/markdown` on site pages (10). The tool reference gives each tool's purpose, class and scopes, and the docs say when to use the CLI instead of MCP and when to propose rather than act (16 of 20). 123 enums, 513 required lists and `additionalProperties: false` in the spec; unknown fields are refused with the accepted list (14 of 15). CLI and curl examples throughout the docs and about 50 error codes with recovery text on the MCP page, but no examples in the OpenAPI file (13 of 15). The API is versioned by path (/v0) and npm by semver, and tokenrip.com/changelog, which answered 404 on 21 October, now lists dated changes from 23 September to 3 November 2026 (15).)
- Transparency & trust, Tokenrip +14: 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.); Tokenrip 71 (The hosted service is closed under clear, dated terms naming Quintel, LLC and Texas law. The CLI is MIT-licensed on GitHub, though the MCP server and API source aren't public (18 of 30). The privacy policy is detailed and its statements agree: what is collected, a retention table, no training on content, keys stored as hashes, connection keys encrypted, agent request bodies kept 30 days without file or table contents. Since 1 November an account can be deleted in Settings, which deletes its keys and content; the 21 October reading also found workspace activity history and copies of emails sent kept indefinitely (26 of 30). No deprecation policy. The changelog dates removals only after the event. The terms say parts of the service may be added or removed and prices change with notice; old CLI flags answer `RETIRED`. Terms changes are shown only by the date at the top (3 of 20). Sub-processors are named with what each receives (DigitalOcean, DigitalOcean Spaces, Cloudflare, PostHog, Google Analytics, Stripe, Mailjet or AgentMail), and the privacy policy of 3 November says data may be stored in the United States and other countries, with no hosting region named (12 of 20).)
- Payments & pricing, Tokenrip +10: MemMachine 40 (Self-hosted rule, with the price lines read for the hosted platform. No x402, MPP or L402 (0 of 40). No hosted prices found on the site or docs (0). Free to self-host with no card (20). An agent can install it from PyPI with no account (20). Total 40.); Tokenrip 50 (No x402, MPP or L402 anywhere in the docs or the OpenAPI file (0 of 40). Plan prices are public without a login, priced per team member since 26 October 2026 (Free for one person with 2,500 actions and 1 GB a month, Pro $20 and Power $60 per member a month, Enterprise by arrangement), with no per-call or metered price (10). The free plan needs an email and a code, with no card (20). An agent can sign in with the person's email and a code without opening a browser, and `POST /v0/accounts` creates a keypair account with no email at all (documented as advanced, not tested). Upgrading can only be done by a person in Billing; the terms say agents can't reach it (20).)
- 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.); Tokenrip 75 (Read for a closed service with an open-source CLI. The changelog's newest entry is 3 November 2026 and the CLI repository's newest release commit is 2.6.16 on 2 November (30). 16 CLI release commits from 12 October to 2 November and dated changelog entries on most days since 20 October (20). No issues or pull requests have ever been opened on the repository. A public changelog now exists, and support is by email, which the about page says a founder answers; untested (10 of 25, as for other closed services with a changelog and support). Listed in the official MCP registry as `io.github.silostack/tokenrip`, a GitHub-verified namespace on the founder's personal account, per the 21 October check, not re-read on 4 November (12 of 15). The repository has no CI workflows and no tests. Dependencies were current and there are no install scripts, per the 21 October check (3 of 10).)
- Reliability, Tokenrip +6: 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.); Tokenrip 57 (Graded with the hosted lines, on the remote MCP server and REST API. status.tokenrip.com, an incident.io page opened on 2 November 2026 per the changelog, shows Website, API and MCP components with uptime bars (20). Its feed lists no incident, and two days of history is a short record (15). Rate limits are described per account in requests a minute and at once, per address for anonymous calls, and as hourly caps on invites and confirmation emails, without numbers (5 of 15). Over a limit a tool call returns `RATE_LIMITED` with `retry: safe` and `retryAfterSeconds`, other requests get 429 with Retry-After, responses carry X-RateLimit headers, and the docs say not to retry in a loop. Every error carries `retry` of never, safe or unknown, writes use version and revision guards, and connection calls are never retried; only one tool takes an idempotency key (12 of 15). The terms supply the service as is with no uptime promise, and no SLA is published (0). Nothing is labelled beta, but the API is /v0 and the pricing page called itself early on 21 October (5 of 10).)