Head to head · FHIR servers · October 2026 research run

Medplum vs Redox

Medplum scores 68.7 (B) on agent readiness against Redox's 58.3 (C), and leads in 5 of 7 scored categories. Redox leads on reliability. Both do fhir servers.

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

Which one, for what

Medplum B

Best for An agent working inside a digital health company's own FHIR store, reading and writing patients, observations and appointments under a BAA.

Ahead on

  • Schema & documentation, 82 against 56
  • Agent ergonomics, 73 against 54
  • Payments & pricing, 25 against 15
  • Maintenance & community, 93 against 31
  • Transparency & trust, 72 against 59

Also in its favour

  • Open source

Watch for

The MCP fhir-request tool can delete or overwrite any resource the token allows, with no readOnlyHint or destructiveHint

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 75

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 runMedplumRedoxEdge
Reliability16%207585Redox +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28256Medplum +26
Agent ergonomics13%16.27354Medplum +19
Security & auth14%17.57478Redox +4
Payments & pricing10%12.52515Medplum +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.89331Medplum +62
Transparency & trust7%8.87259Medplum +13
Negative events≤15-20
TotalB 68.7/100C 58.3/100

Facts side by side

FactMedplumRedox
KindHTTP APIHTTP API
VendorOrangebot, Inc. (dba Medplum)Redox, Inc.
Hosted endpointhttps://api.medplum.com/mcp/streamhttps://api.redoxengine.com/mcp
TransportsHTTP, Streamable HTTP, SSE (legacy)HTTP
AuthOAuthOAuth
PricingFreemiumPaid
x402nono
LicenceApache 2.0 for the server, SDKs and apps in medplum/medplum. The hosted service at api.medplum.com runs under Medplum's terms of serviceProprietary service under Redox's Cloud Services Agreement, EULA and SLA (version 2016.1)
Tools exposed3107
Read-only variant documentedyesno
llms.txtyesno
MCP registrycom.medplum/mcpnot listed
Last release2026-10-08none
Terms last updated2023-04-112015-10-17
Privacy policy last updated2022-04-052023-01-18
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity2.7k stars, 270k npm/wknone

Verdicts

Medplum

Graded on the hosted FHIR API at api.medplum.com. Rate limits, a RateLimit header and a 99.99 per cent SLA are published, AccessPolicy resources allow read-only clients, and an official MCP server sits in the registry. Its main tool can delete records with no annotation, the status page could not be read, and the privacy policy dates from 2022.

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

Medplum

  1. Use a ClientApplication with an AccessPolicy limited to the resources the task needs, and set readonly where no writes are needed
  2. Read the RateLimit header and wait for the reset time after a 429. Writes cost 100 quota points, searches 20 and reads 1
  3. Create patients with conditional create (If-None-Exist) or upsert on an identifier so a retry doesn't make a duplicate
  4. Pass paths to fhir-request relative to the FHIR R4 base, with no leading slash or /fhir/R4 prefix
  5. Use Prefer: respond-async for large bundles. Operations inside the background job don't count against the quota

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, Medplum or Redox?

Medplum scores 68.7 (B) on agent readiness against Redox's 58.3 (C), and leads in 5 of 7 scored categories. Redox leads on reliability.

Do Medplum and Redox need an API key?

Both use an OAuth sign-in.

Can an agent call Medplum and Redox without installing anything?

Yes. Medplum has a hosted endpoint at https://api.medplum.com/mcp/stream and Redox at https://api.redoxengine.com/mcp.

Are Medplum and Redox open source?

Medplum is open source (Apache 2.0 for the server, SDKs and apps in medplum/medplum. The hosted service at api.medplum.com runs under Medplum's terms of service). No open-source release is listed for Redox.

Other comparisons with Medplum 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.