Redox

# Fix list: Redox

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/redox, the October 2026 research run, assessed 14 October 2026. Grade C, 58.3 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 Redox: 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. Payments & pricing, 15 out of 100, up to 10.6 more on the total

Why it scored 15: Read with the hosted rubric. No x402, MPP or L402 (0). Plan starting prices are public ($15,000 and $35,000 a year), with consumption and Advanced pricing by quote (10 of 20). A dashboard account needs no card, but a sandbox with a FHIR sandbox is a paid plan, and what a free account can call is not stated (5 of 20). Sign-up and email verification are done by a person 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.

## 2. Agent ergonomics, 54 out of 100, up to 7.5 more on the total

Why it scored 54: The MCP server lists 107 live tools in one set, with no toolsets or read-only subset documented. FHIR search sizes data responses (10 of 25). FHIR search and log search with metadata filters (15 of 20). Errors documented with causes and next steps, such as the 429 and 5XX entries (16 of 20). No idempotency keys. MCP tools are labelled Read, Write and Delete in the docs, and we did not confirm readOnlyHint or destructiveHint annotations, since we read the tool list rather than calling the server (8 of 20). No official SDK. Postman collections and OpenAPI files come from the dashboard (5 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.

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

Why it scored 56: OpenAPI files exist but only as downloads inside the dashboard. Public reference pages cover each FHIR resource, data model and Platform API endpoint (12 of 25). docs.redoxengine.com/llms.txt returns the HTML site, and no Markdown copies were found (0). Guides explain when to use data on demand, polling or notifications, and each MCP tool is labelled Read, Write or Delete with a one-line purpose (15 of 20). Data model fields are documented with types and required markers in the reference pages (11 of 15). An error handling page with codes and actions and several troubleshooting pages (13 of 15). Pages carry 'Last updated' dates, with no public changelog or version history (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.

## 4. Maintenance & community, 31 out of 100, up to 6 more on the total

Why it scored 31: No dated release was found. The MCP page was updated on 13 October 2026 with tools marked coming soon, and the AI settings page on 2 September 2026, which we read as recent changes without a release record (20 of 30). No public changelog with three dated entries (0). Closed service with a help centre and support email. We did not test support (6 of 15). No official SDK, and we did not find Redox in the official MCP registry, though Claude's directory carries a connector (3 of 15). Nothing public to judge package health (2 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.

## 5. Security & auth, 78 out of 100, up to 3.9 more on the total

Why it scored 78: OAuth API keys signed with the client's private key, with JWKS entry or URL options, key rotation guidance and user-level keys. MCP access is per user through OAuth (28 of 30). Development, staging and production environments, role-restricted PHI payload visibility, and an owner opt-in for the MCP server. MCP write and delete tools have no documented confirmation step, and the docs advise testing in staging (13 of 20). The MCP server returns log payloads, which may hold PHI and outside content, with no prompt-injection guidance (4 of 15). An audit events API and log search for operators (15). HITRUST r2, SOC 2 Type 2 and a public HackerOne bug bounty, with no security.txt (18 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.

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

Made of editorial 37, provenance 80.

Why it scored 59: Closed service. The website terms date from 2015, the SLA from 2016, and the Cloud Services Agreement and EULA were not read (13 of 30). The privacy policy (January 2023) excludes customer data. Enabling AI assistants consents to usage and prompt data being used for training with PHI excluded (12 of 30). A migration guide from legacy to OAuth API keys, with no dated deprecation policy (6 of 20). AWS and Google Cloud are named as hosts under BAAs, with no sub-processor list or regions (6 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):

- Changelog: not found (0 of 10)
- security.txt: not found (0 of 10)

## 7. Reliability, 85 out of 100, up to 3 more on the total

Why it scored 85: Read with the hosted lines, on the FHIR and Platform APIs and the MCP server. status.redoxengine.com on Statuspage with 19 components and history (20). In the last 90 days, a third-party outage disrupted processing for about 40 minutes on 8 September 2026 with a postmortem, and log visibility lagged on 9 September (20 of 30). 7,500 requests per IP per five minutes, with a lower DevTools limit (15). The 429 description says to wait and retry and 5XX guidance asks for exponential backoff, with automatic retries for asynchronous messages, but no idempotency keys (10 of 15). A published SLA of 99.95 per cent with credits, dated 2016 (10). The APIs and MCP server are in production use, with some MCP tools marked coming soon (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.

## 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: whether the MCP tools carry readOnlyHint or destructiveHint annotations; we read the published tool list and did not call the server
- unchecked: the Cloud Services Agreement and EULA
- What a free dashboard account can call before buying a plan is not stated
- unchecked: whether Redox is in the official MCP registry

## Weaknesses

- The MCP server loads 107 tools in one set, including write and delete tools with no confirmation step
- OpenAPI files and Postman collections are behind the dashboard login, and llms.txt is missing
- No public changelog or dated releases
- The cheapest plan with a sandbox starts at $15,000 a year

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

- Name the environment in every MCP prompt and try configuration changes in staging first, as Redox advises
- Stay under 7,500 requests per IP per five minutes, and back off exponentially on 5XX
- Sign the token request with the private key whose public key is registered on the OAuth API key
- Ask an organisation owner to enable the MCP server before connecting a client
- Treat log payloads returned through MCP as PHI and as untrusted text

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