Tab

# Fix list: Tab

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/tab-bot, the October 2026 research run, assessed 14 October 2026. Grade F, 10.7 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 Tab: 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, 5 out of 100, up to 19 more on the total

Why it scored 5: Read with the hosted lines. No status page found (0). No readable incident history (5). No limits published (0). No overload or retry guidance (0). No SLA found (0). Private beta behind a waitlist, which the Dots listing scored 0 for a gradual rollout (0).

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. Security & auth, 4 out of 100, up to 16.8 more on the total

Why it scored 4: Graded on the interface an outside agent can use. With none for Tab, the credential, least-privilege, injection and audit lines score nothing (0 of 30, 0 of 20, 0 of 15, 0 of 15), whatever the service does for its owner. The security programme line doesn't need an interface and is scored. For the record, the security page sets out saved passwords encrypted with AES-256-GCM and filled inside a separate boundary, masked screenshots, write actions denied unless the exact action is enabled, and checkout bound to the approved cart and exact total and charged once. The security page, last reviewed on 21 August 2026, asks for reports by email with the subject Security to an address that decodes to privacy@tab.bot. No security.txt (404), bug bounty, certification or advisories found. A reporting route on a security page is a little more than Instinct's 3 for a support address in security.txt (4 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.

## 3. Schema & documentation, 0 out of 100, up to 16.3 more on the total

Why it scored 0: Graded on the interface an outside agent can use, as GRADER.md asks. Tab has no API, MCP server or A2A endpoint for an agent, so the contract, description, typed-input and example lines score nothing (0 of 25, 0 of 20, 0 of 15, 0 of 15). That is a statement about agent access, not about the product for people. tab.bot/llms.txt returns 404 and no Markdown docs for agents were found (0). The versioning and changelog line versions an agent interface, and with none there is nothing to version, so it scores nothing (0 of 15). This is the reading the 12 October auditor applied to every listing without an agent interface, and app release notes count under maintenance instead.

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.

## 4. Agent ergonomics, 0 out of 100, up to 16.3 more on the total

Why it scored 0: Graded on the interface an outside agent can use. Tab has none, so context cost, pagination, errors, retries and defaults have nothing to score (0 on each line). This says nothing about the product for people.

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. Payments & pricing, 0 out of 100, up to 12.5 more on the total

Why it scored 0: Read with the hosted rule. No x402, MPP or L402 (0). No price or plan is published on tab.bot (0). No free plan or trial is stated, and access is by waitlist (0). A person joins the waitlist with a name and mobile number (0).

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.

## 6. Transparency & trust, 45 out of 100, up to 4.8 more on the total

Made of editorial 30, provenance 59.

Why it scored 45: Closed service under terms effective 2 September 2026 naming Terrasoft, Inc. (15). The privacy policy, effective the same day, names providers by category and says nothing on training models with user content, and the home page loads Meta and TikTok pixels and other attribution scripts. No retention periods were found (10 of 30). No deprecation policy or dated notices found (2 of 20). Providers by category only, with no names or regions, the Instinct dossier's 3 (3 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: tab.bot, registered 2026-08-21 (under a year) (0 of 15)
- Status page: not found (0 of 10)
- security.txt: not found (0 of 10)

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

Why it scored 58: Read for a closed service. The updates page's latest entries are dated 14 September 2026, 30 days before this check (30). One grader read dated entries on eight days from 4 to 14 September 2026, and the lister's read of the same day agrees on the latest date. tab.bot refused the other grader's requests with 403 and the auditor didn't request it, so the count rests on that read (20). A public updates page and a reporting route on the security page, untested, below the 10 given to near-daily changelogs with an address (8 of 15). No MCP server or SDK (0). No package or CI to judge (0).

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 by the auditor: tab.bot, which answered 403 to ClaudeBot on 14 October 2026. The updates count rests on one grader's read and the lister's.
- Price and plans after the private beta.
- Whether user content trains models, which the privacy policy doesn't address.

## Weaknesses

- Private beta behind a waitlist.
- No API, MCP server or A2A endpoint for an outside agent.
- No price or plan published.
- The privacy policy says nothing on training with user content, and the home page loads ad pixels.

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

- Don't plan to call Tab from another agent. It answers only the owner's Messages or WhatsApp thread.
- Tell the owner that access needs a waitlist place and no price is published.

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