Write a review

Head to head · Patient record retrieval · October 2026 research run

Medblocks vs Redox

Redox scores 58.3 (C) on agent readiness against Medblocks's 52.7 (D), and leads in 3 of 7 scored categories. Medblocks leads on schema & documentation, agent ergonomics, payments & pricing and maintenance & community. Both do patient record retrieval.

Best health record and wellness data APIs for AI agents · All 63 health comparisons

MedblocksMedblocks Inc. · HTTP API D52.7/100#780 of 1094 RedoxRedox, Inc. · HTTP API C58.3/100#623 of 1094

Which one, for what

Medblocks D

Best for A consumer or care app, or an assistant, that needs a patient's own records from US hospitals and payers with the patient's consent, and wants an MCP route as well as REST.

Ahead on

  • Schema & documentation, 62 against 56
  • Agent ergonomics, 72 against 54
  • Payments & pricing, 25 against 15
  • Maintenance & community, 69 against 31

Watch for

No status page, SLA or published rate limits for the Platform API

Redox C

Best for Health software vendors integrating with many hospital EHRs and networks, and integration teams who want an agent to manage Redox configuration.

Ahead on

  • Reliability, 85 against 28
  • Security & auth, 78 against 67
  • Transparency & trust, 59 against 51

Watch for

The MCP server loads 107 tools in one set, including write and delete tools with no confirmation step

Score by category

CategoryWeight this runMedblocksRedoxEdge
Reliability16%202885Redox +57
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26256Medblocks +6
Agent ergonomics13%16.27254Medblocks +18
Security & auth14%17.56778Redox +11
Payments & pricing10%12.52515Medblocks +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86931Medblocks +38
Transparency & trust7%8.85159Redox +8
Negative events≤1500
TotalD 52.7/100C 58.3/100

Facts side by side

FactMedblocksRedox
KindHTTP APIHTTP API
VendorMedblocks Inc.Redox, Inc.
Hosted endpointhttps://app.medblocks.com/mcphttps://api.redoxengine.com/mcp
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyOAuth
PricingFreemiumPaid
x402nono
LicenceProprietary service under Medblocks' terms. The medblocks TypeScript SDK on npm carries a proprietary licence that forbids redistribution and reverse engineering. The agent skills repository has no licence fileProprietary service under Redox's Cloud Services Agreement, EULA and SLA (version 2016.1)
Tools exposed10107
Read-only variant documentednono
llms.txtyesno
Last release2026-09-14none
Terms last updated2026-10-052015-10-17
Privacy policy last updated2026-10-052023-01-18
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity36 npm/wknone

Verdicts

Medblocks

Patient-authorised record retrieval with a ten-tool remote MCP server, OAuth with per-capability consent, an audit entry for every call and a free plan for 1,000 active patients. No status page, no published rate limits and no idempotency keys were found, and the OpenAPI file behind the reference is not published.

Redox

Redox connects to EHRs and clinical networks behind a FHIR API, with signed-JWT OAuth keys, a 99.95 per cent SLA, a HackerOne bug bounty and a hosted MCP server for managing integrations. The MCP server exposes 107 tools at once with write and delete tools unconfirmed, OpenAPI files sit behind login, and the sandbox plan costs $15,000 a year.

Before you call either

Medblocks

  1. Connect with claude mcp add --transport http medblocks https://app.medblocks.com/mcp and sign in, or send a workspace API key as a Bearer token from a backend
  2. Ask the person before calling disconnect_health_system or delete_person. Both are permanent
  3. Wait for the connection webhook or check connection status before reading records. Pulls run in the background after the patient approves
  4. Branch on error.code, not the message, and wait the Retry-After seconds on a 429
  5. Use a Sandbox workspace and the Synthetic Hospital (password demopass) for tests. Sandbox keys cannot reach production sources

Redox

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

Questions

Which is better for AI agents, Medblocks or Redox?

Redox scores 58.3 (C) on agent readiness against Medblocks's 52.7 (D), and leads in 3 of 7 scored categories. Medblocks leads on schema & documentation, agent ergonomics, payments & pricing and maintenance & community.

Do Medblocks and Redox need an API key?

Medblocks takes an API key or an OAuth sign-in. Redox uses an OAuth sign-in.

Can an agent call Medblocks and Redox without installing anything?

Yes. Medblocks has a hosted endpoint at https://app.medblocks.com/mcp and Redox at https://api.redoxengine.com/mcp.

Other comparisons with Medblocks or Redox

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report