Basic Memory vs Tokenrip

Basic Memory 83

Local-software lines, as a stdio MCP server the owner runs. basic-memory on PyPI with Python 3.12 or newer stated, installed with uv (20). Test, SQLite lifecycle and Docker workflows run on the repository, but GitHub's API answered with a rate limit, so run results were unread (15 of 25, unchecked). 74 open issues and pull requests against 200 commits in the 90 days, with recent bug reports answered by a maintainer within days and one flaky-CI issue open (18 of 25). The changelog calls out breaking changes in their own sections (15). v1.0.0 on 29 October 2026 (15). Total 83.

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

Basic Memory 91

v1.0.0 on 29 October 2026 (30). v0.24.0 and v0.24.1 on 22 October and v1.0.0, three releases in 90 days (20). Recent issues from outside users got maintainer replies within a few days (20 of 25). Verified namespace io.github.basicmachines-co/basic-memory in the official MCP registry, published by a workflow (15). uv.lock and CI, with an open report of an unmaintained dependency (6 of 10). Total 91.

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

Basic Memory 85

13 tools, one hidden unless enabled, so the 11 to 30 band (15), with 6 back for the manual tool and the progressive-discovery tags (21 of 25). Search narrows by mode, filters, note types, items, since, path and line context (18 of 20). Refusals are tool errors with typed codes an agent can act on (17 of 20). Every tool has readOnly, destructive and idempotent hints, and edits take an expected checksum that refuses a stale write (19 of 20). Most arguments are optional and the server starts with one command, but there is one language and no SDK beyond the CLI (10 of 15). Total 85.

Tokenrip 70

Graded on the MCP server. 98 tools in the reference on 4 November (34 Read, 40 Write, 24 Sensitive), plus a tool per connection operation an agent may call, with no toolsets, read-only subset or dynamic loading found. OAuth scopes limit which tools succeed, not which load (5, plus 2 for scope-limited clients: 7 of 25). Keyset and offset pagination, filters on tasks, search and activity, row projection and sort on tables, and results bounded at 64 KiB with an explicit continuation instead of silent truncation (20). Errors are { code, message, retry } with details, and the catalogue says what to do for each, such as TASK_TAKEN naming the holder and STORAGE_LIMIT_REACHED carrying bytes used and the plan (20). Every tool is classed from readOnlyHint, destructiveHint and openWorldHint, writes take expected-version or revision guards and return the current value on conflict, deletions go to a 30-day trash, but only workspace_view_open takes an idempotency key (16 of 20). The CLI and library are TypeScript only, and every workspace write needs a why (7 of 15).

Basic Memory 82

AGPL-3.0, an OSI licence (30). The terms and privacy policy of 27 October 2026 agree on 30-day retention after cancellation, backups up to 90 days and no training on or sale of content, and name the infrastructure providers (26 of 30). The 1.0 release ships a migration guide mapping every removed tool and command, without a written deprecation period (14 of 20). Telemetry is disclosed in the README with what is and isn't sent and one opt-out, but it is on by default (16 of 20). Total 86.

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

Basic Memory 61

Local stdio server with no credential, and cloud OAuth 2.1 through WorkOS with read-only or project-scoped keys on Pro (22 of 30). Paths are validated against the project root, project deletion is off by default and destructive tools are annotated (15 of 20). SECURITY.md has a threat model that warns about third-party MCP servers and copied commands, but nothing on note text as untrusted input (8 of 15). A local log file, and cloud audit logs only on Business (8 of 15). SECURITY.md gives an email and a 72-hour response aim but lists only 0.x.x as supported; no security.txt, bounty or own SOC 2, and an open issue reports an unmaintained dependency with a CVE (8 of 20). Total 61.

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