Tigris by Tigris Data

# Fix list: Tigris

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/tigris, the October 2026 research run, assessed 1 October 2026. Grade E, 44.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 Tigris: 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, 35 out of 100, up to 13 more on the total

Why it scored 35: Status page on incident.io with an RSS feed and per-region uptime (20). 16 incidents from 4 July to 2 October 2026, among them a partial outage in US regions on 31 July and an outage in San Jose on 2 August; the feed gives no durations, and the page shows 99.78 per cent for North America (5). No rate limits found in the docs or their llms.txt (0). No error-handling or retry guidance found (0). No SLA found (0). The S3 API is GA (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, 30 out of 100, up to 8.8 more on the total

Why it scored 30: No x402, MPP or L402 (0). Per-GB and per-request prices public without a login, per the 30 September check (20). A free 5 GB and 110,000 requests a month; we didn't establish whether signup asks for a card (10). A person signs up in a browser (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.

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

Why it scored 51: Access keys scoped per bucket with ReadOnly, ReadWrite or Editor roles and IAM policies with conditions, revocable and rotatable through the IAM API. No STS or expiring keys, so every key lives until revoked (25). A ReadOnly role and bucket soft delete, but no read-only MCP mode or delete confirmation documented (12). Returns stored bytes, with no guidance on treating them as untrusted (8). No audit log found (0). No security.txt. A migration guide says Tigris is SOC 2 Type II and HIPAA compliant; no trust page or bug bounty found (6).

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. Schema & documentation, 50 out of 100, up to 8.1 more on the total

Why it scored 50: No OpenAPI. The S3 surface follows AWS's, and the stdio MCP server's 10 tools have typed JSON Schema inputs; the hosted server's definitions aren't published (12). llms.txt with 250-odd Markdown pages (10). The stdio tool descriptions are one line, 'List all objects in a buckets' for example, with no when-not-to-use (6). String inputs with required fields, no enums or bounds (8). Examples in the docs, but no documented error responses (6). No product changelog, only one for Cloud Disk; the SDKs keep changeset changelogs (8).

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.

## 5. Agent ergonomics, 53 out of 100, up to 7.6 more on the total

Why it scored 53: The stdio MCP server has 10 compact tools, but tigris_list_objects pages through a whole bucket with no limit or prefix (20). The S3 API pages and filters; the MCP list tool doesn't (10). No documented error codes or recovery guidance (5). No readOnlyHint or destructiveHint on the stdio tools, and we couldn't see the hosted server's (5). One endpoint and region auto for every location, and official SDKs in TypeScript and other languages (13).

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.

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

Made of editorial 52, provenance 50.

Why it scored 51: Closed service; the SDKs, CLI and MCP server are MIT (20). Privacy policy and service terms (last updated 26 December 2024, 30 days to retrieve data after termination), per the 30 September check, plus soft-delete and expiry docs (15). No deprecation policy; the old fly.storage.tigris.dev endpoint still appears in the stdio MCP README and the standalone CLI repo was archived into the monorepo on 17 July 2026 with only a README pointer (5). Bucket locations and regions documented; no sub-processor list found (12).

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: tigrisdata.com, no registry record we could read (0 of 15)
- Endpoint on the vendor's domain: t3.storage.dev is not on tigrisdata.com (0 of 15)
- Changelog: not found (0 of 10)
- security.txt: not found (0 of 10)

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

Why it scored 77: @tigrisdata/storage 3.22.0 and the CLI 3.14.0 on 30 September 2026 (30). Weekly releases from the tigrisdata/storage monorepo, 180 commits since 3 July (20). Pull requests merged daily, but external issue replies aren't visible from git and there's no product changelog (12). Current official SDKs, but the stdio MCP server's last release was 1.14.0 on 17 November 2025 and it isn't in the MCP registry (7). Renovate and CI in the monorepo (8).

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.

## Deductions

Each comes off the total. A fixed and documented problem counts for less at the next check.

- 2026-09-21. @tigrisdata/iam 2.6.0 fixed policy create, update and read dropping the Condition and Sid fields, so IP-restricted or time-limited policies made with Tigris's own SDK or CLI had silently become unrestricted. Fixed and documented in the changelog, so we deduct less (-3). https://github.com/tigrisdata/storage/blob/main/packages/iam/CHANGELOG.md

## 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: incident durations, which the status feed doesn't carry
- unchecked: whether Tigris publishes an SLA, rate limits or an audit log anywhere outside its docs llms.txt
- unchecked: whether Tigris signup asks for a card
- The hosted MCP server's tool list, scopes and annotations aren't published, so ergonomics and security are graded on the stdio server and the docs
- The listing's lastRelease (2025-11-17) was the stdio MCP server's; the SDK monorepo shipped on 2026-09-30, so lastRelease was patched and @tigrisdata/storage added to packages

## Weaknesses

- 16 status incidents between 4 July and 2 October 2026, including outages in US regions on 31 July and 2 August
- No STS or expiring keys; presigned URLs, which can run to 90 days, are the only short-lived credential
- No published rate limits, retry guidance, OpenAPI, product changelog or audit logs
- The stdio MCP server last released on 17 November 2025, lists whole buckets with no limit and carries no tool annotations
- @tigrisdata/iam dropped Condition fields from policies until 2.6.0 on 21 September 2026

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

- Point the AWS SDK at https://t3.storage.dev with region `auto`; the stdio MCP README still shows the older fly.storage.tigris.dev endpoint
- Ask for an access key with a ReadOnly or ReadWrite role on one bucket rather than an org-wide key
- Keep presigned URLs short; Tigris accepts up to 90 days
- Don't call tigris_list_objects on a large bucket; it walks every object with no limit or prefix
- Use @tigrisdata/iam 2.6.0 or later before writing policies with conditions

## What the review panel asked for

- State card requirement
- STS session credentials
- shorter presigned URL ceiling

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