Tokenrip

# Fix list: Tokenrip

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/tokenrip, the October 2026 research run, assessed 21 October 2026. Grade C, 59.6 out of 100.

This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public.

For a coding agent working on Tokenrip: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published.

## 1. Reliability, 27 out of 100, up to 14.6 more on the total

Why it scored 27: Graded with the hosted lines, on the remote MCP server and REST API. No status page found: tokenrip.com/status answers 404, status.tokenrip.com doesn't resolve, and none is linked from the site or docs (0). No readable incident history (5). Rate limits are described per IP address and per identity per minute without numbers, and hourly caps on key creation (a default of 10 an hour in the OpenAPI file), sign-in codes and invite emails are named (5 of 15). A 429 carries `{ ok: false, error: "RATE_LIMITED" }` and the docs say to wait and not retry in a loop, with no Retry-After. Every error carries `retry` of never, safe or unknown, writes use version and revision guards, `WORKSPACE_BUSY` says to retry the same call, and connection calls are never retried and report their outcome (12 of 15). The terms provide the service as is with no uptime promise, and no SLA is published (0). Nothing is labelled beta, but the API is /v0, the OpenAPI file is version 0.2.0 and the pricing page calls itself early (5 of 10).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability):

Hosted APIs, MCP servers, models and platforms.

- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).
- 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so.
- 15, rate limits documented with numbers.
- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.
- 10, an SLA published for any paid tier.
- 10, the surface agents use is generally available, not beta or preview.

Local packages, SDKs, frameworks and stdio MCP servers.

- 20, installs from an official package with supported runtimes stated.
- 25, a public CI and test suite, passing on the default branch.
- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).
- 15, semver discipline and breaking changes called out in a changelog.
- 15, version 1.0 or later, or declared stable.

Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors.

## 2. Payments & pricing, 50 out of 100, up to 6.3 more on the total

Why it scored 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 by storage (Free 1 GB, Pro $20 a month for 10 GB, Team $50 a month for 100 GB), with no per-call or per-GB 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).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments):

The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).

- 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which.
- 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login.
- 20, a free tier or trial that doesn't need a card.
- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).

Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied.

Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol.

## 3. Security & auth, 69 out of 100, up to 5.4 more on the total

Why it scored 69: 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). No security.txt (404) and no security page (404). The CLI's SECURITY.md names security@tokenrip.com with a 2-business-day acknowledgement, but lists 1.1.x as supported and links a monorepo that isn't public. No bug bounty, no certifications, no published advisories. The privacy policy promises notice within 48 hours of a confirmed incident (5 of 20).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-security):

- 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option.
- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.
- 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10.
- 0 to 15, audit logs or per-call visibility for the operator.
- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.

Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing.

## 4. Agent ergonomics, 70 out of 100, up to 4.9 more on the total

Why it scored 70: Graded on the MCP server. 99 tools, which the docs call a frozen catalogue, 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).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics):

- 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries).
- 20, pagination, filtering and output-size controls.
- 20, actionable, documented error responses, codes and messages an agent can recover from.
- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.
- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.

Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs.

## 5. Transparency & trust, 56 out of 100, up to 3.9 more on the total

Made of editorial 57, provenance 55.

Why it scored 56: 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. It also says workspace activity history (reasons, agents, titles) is kept indefinitely after deletion, emails sent are kept indefinitely, and account deletion is by email request only (24 of 30). No deprecation policy. 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), but no hosting region or data location is stated (12 of 20).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency):

- 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms.
- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).
- 0 to 20, a deprecation policy or notices with dates.
- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).

The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two.

Provenance checks not met in full (half of this category, computed from checked facts):

- Domain age: tokenrip.com, registered 2026-03-25 (under a year) (0 of 15)
- Status page: not found (0 of 10)
- Changelog: not found (0 of 10)
- security.txt: not found (0 of 10)

## 6. Schema & documentation, 83 out of 100, up to 2.8 more on the total

Why it scored 83: 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). 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, but there's no public changelog, no GitHub releases and no changelog file; tokenrip.com/changelog answers 404 (5 of 15).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema):

APIs and MCP servers.

- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).
- 10, llms.txt or Markdown docs served for agents.
- 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference.
- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.
- 0 to 15, examples and documented error responses.
- 15, versioning and a public changelog.

Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference.

## 7. Maintenance & community, 70 out of 100, up to 2.6 more on the total

Why it scored 70: Read for a closed service with an open-source CLI. `@tokenrip/cli` 2.6.4 was published on 21 October 2026, the day of the check (30). 10 npm versions in the last 90 days, seven of them in October (20). No issues or pull requests have ever been opened on the repository, there's no public changelog, and support is by email, which the about page says a founder answers; untested (5 of 25). Listed in the official MCP registry as `io.github.silostack/tokenrip`, a GitHub-verified namespace on the founder's personal account rather than the tokenrip organisation (12 of 15). The repository has no CI workflows and no tests, and npm 2.6.4 has no provenance attestations. Dependencies are current (axios 1.20, commander 12) and there are no install scripts (3 of 10).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance):

- 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older.
- 20, at least three releases or dated changelog entries in the last 90 days.
- 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15.
- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).
- 10, package health, current dependencies and CI.

Models are read for deprecation notice periods and model churn rather than release counts.

## What we couldn't check

What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it.

- unchecked: the MCP tools' JSON input schemas and annotations as served, because no MCP session was opened; the Read, Write and Sensitive classes and scopes come from the published tool reference.
- unchecked: the numeric per-minute rate limits, which the tool reference describes without numbers.
- firstReleased is the first npm version, 1 April 2026, when the product was a CLI for publishing and sharing assets. The shared-workspace product with tasks and connections dates from 2.0.0 on 29 September 2026, and the MCP registry entry from 6 May 2026. The listing request and the registry's 1.1.0 entry are from 21 October 2026.
- The pricing page calls itself "early, October 2026". That's the vendor's word; no beta label was found on the product.
- Whether a keypair account made with `POST /v0/accounts` gets the free 1 GB plan. The docs call the route advanced and don't say.
- Our own products. Tokenrip doesn't do LocalGhost's job (a personal AI server on hardware its owner keeps) or letme's (picking a tool for a job from our grades), so it was graded the normal way.
- Category. The vendor's FAQ says Tokenrip isn't a memory tool. agent-memory was kept as the closest fit, beside AI Memory; file-storage and project-management each cover only part of it.

## Weaknesses

- 99 tool definitions with no toolsets or dynamic loading found
- `tr_` API keys have full access to the account, with no read-only key
- No status page, public changelog or SLA found, and per-minute rate limits are unpublished
- No CI or tests in the CLI repository, and its SECURITY.md is out of date
- Paid plans can be started only by a person in Billing

## What costs an agent a turn today

The notes we give agents before they call it. Each one is a workaround an agent shouldn't need.

- Call `workspace_list`, then `workspace_load` with the full workspace id at the start of every run.
- Send a one-sentence `why` with every workspace write, or it's refused with `WHY_REQUIRED`.
- Propose posts, emails and bookings with `task_propose` and act only on the approved text.
- Ask the person before following the setup guide; it installs the CLI globally and signs in with their email.
- Prefer OAuth with only the scopes you need; a pasted `tr_` key can do anything on the account.

## What the review panel asked for

- read-only or scoped API keys
- a current security policy
- Add a smaller toolset
- Publish a changelog
- read-only API keys
- Publish tool schema size

## When it's done

Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.