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
| Category | Weight this run | Medplum | Redox | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 75 | 85 | Redox +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 82 | 56 | Medplum +26 |
| Agent ergonomics | 13%16.2 | 73 | 54 | Medplum +19 |
| Security & auth | 14%17.5 | 74 | 78 | Redox +4 |
| Payments & pricing | 10%12.5 | 25 | 15 | Medplum +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 93 | 31 | Medplum +62 |
| Transparency & trust | 7%8.8 | 72 | 59 | Medplum +13 |
| Negative events | ≤15 | -2 | 0 | |
| Total | B 68.7/100 | C 58.3/100 |
Facts side by side
| Fact | Medplum | Redox |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Orangebot, Inc. (dba Medplum) | Redox, Inc. |
| Hosted endpoint | https://api.medplum.com/mcp/stream | https://api.redoxengine.com/mcp |
| Transports | HTTP, Streamable HTTP, SSE (legacy) | HTTP |
| Auth | OAuth | OAuth |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | 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 | Proprietary service under Redox's Cloud Services Agreement, EULA and SLA (version 2016.1) |
| Tools exposed | 3 | 107 |
| Read-only variant documented | yes | no |
| llms.txt | yes | no |
| MCP registry | com.medplum/mcp | not listed |
| Last release | 2026-10-08 | none |
| Terms last updated | 2023-04-11 | 2015-10-17 |
| Privacy policy last updated | 2022-04-05 | 2023-01-18 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 2.7k stars, 270k npm/wk | none |
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
- Use a ClientApplication with an AccessPolicy limited to the resources the task needs, and set
readonlywhere no writes are needed - Read the
RateLimitheader and wait for the reset time after a 429. Writes cost 100 quota points, searches 20 and reads 1 - Create patients with conditional create (
If-None-Exist) or upsert on an identifier so a retry doesn't make a duplicate - Pass paths to
fhir-requestrelative to the FHIR R4 base, with no leading slash or/fhir/R4prefix - Use
Prefer: respond-asyncfor large bundles. Operations inside the background job don't count against the quota
Redox
- 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
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
- Aidbox vs Medplum
- Aidbox vs Redox
- Medplum vs Metriport Medical API
- Medplum vs Particle Health
- Medplum vs ROOK
- Medplum vs Terra API
- Medplum vs Zus Health
- Redox vs ROOK
- Redox vs Terra API
- 1upHealth vs Medplum
- 1upHealth vs Redox
- Health Gorilla vs Medplum
- Health Gorilla vs Redox
- Medblocks vs Medplum
- Medblocks vs Redox
- Metriport Medical API vs Redox
- Particle Health vs Redox
- Redox vs Zus Health
Machine-readable
- This page as Markdown
/compare/medplum-vs-redox.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/medplum.json·/api/v1/tools/redox.json - From a terminal
anchor compare medplum redox(the CLI) - Over MCP
compare_tools {"a": "medplum", "b": "redox"}at/mcp, no key