Head to head · Patient record retrieval · October 2026 research run
Medblocks vs Medplum
Medplum scores 68.7 (B) on agent readiness against Medblocks's 52.7 (D), and leads in 6 of 7 scored categories. Both do patient record retrieval.
Best health record and wellness data APIs for AI agents · All 63 health comparisons
Which one, for what
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.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
No status page, SLA or published rate limits for the Platform API
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
- Reliability, 75 against 28
- Schema & documentation, 82 against 62
- Security & auth, 74 against 67
- Maintenance & community, 93 against 69
- Transparency & trust, 72 against 51
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
Score by category
| Category | Weight this run | Medblocks | Medplum | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 28 | 75 | Medplum +47 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 62 | 82 | Medplum +20 |
| Agent ergonomics | 13%16.2 | 72 | 73 | Medplum +1 |
| Security & auth | 14%17.5 | 67 | 74 | Medplum +7 |
| Payments & pricing | 10%12.5 | 25 | 25 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 69 | 93 | Medplum +24 |
| Transparency & trust | 7%8.8 | 51 | 72 | Medplum +21 |
| Negative events | ≤15 | 0 | -2 | |
| Total | D 52.7/100 | B 68.7/100 |
Facts side by side
| Fact | Medblocks | Medplum |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Medblocks Inc. | Orangebot, Inc. (dba Medplum) |
| Hosted endpoint | https://app.medblocks.com/mcp | https://api.medplum.com/mcp/stream |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, SSE (legacy) |
| Auth | OAuth or key | OAuth |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary 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 file | 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 |
| Tools exposed | 10 | 3 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | not listed | com.medplum/mcp |
| Last release | 2026-09-14 | 2026-10-08 |
| Terms last updated | 2026-10-05 | 2023-04-11 |
| Privacy policy last updated | 2026-10-05 | 2022-04-05 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 36 npm/wk | 2.7k stars, 270k npm/wk |
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.
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.
Before you call either
Medblocks
- Connect with
claude mcp add --transport http medblocks https://app.medblocks.com/mcpand sign in, or send a workspace API key as a Bearer token from a backend - Ask the person before calling
disconnect_health_systemordelete_person. Both are permanent - Wait for the connection webhook or check connection status before reading records. Pulls run in the background after the patient approves
- Branch on
error.code, not the message, and wait theRetry-Afterseconds on a 429 - Use a Sandbox workspace and the Synthetic Hospital (password
demopass) for tests. Sandbox keys cannot reach production sources
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
Questions
Which is better for AI agents, Medblocks or Medplum?
Medplum scores 68.7 (B) on agent readiness against Medblocks's 52.7 (D), and leads in 6 of 7 scored categories.
Do Medblocks and Medplum need an API key?
Medblocks takes an API key or an OAuth sign-in. Medplum uses an OAuth sign-in.
Can an agent call Medblocks and Medplum without installing anything?
Yes. Medblocks has a hosted endpoint at https://app.medblocks.com/mcp and Medplum at https://api.medplum.com/mcp/stream.
Are Medblocks and Medplum open source?
No open-source release is listed for Medblocks. 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).
Other comparisons with Medblocks or Medplum
- Aidbox vs Medblocks
- Aidbox vs Medplum
- Medplum vs Metriport Medical API
- Medplum vs Particle Health
- Medplum vs Redox
- Medplum vs ROOK
- Medplum vs Terra API
- Medplum vs Zus Health
- 1upHealth vs Medblocks
- 1upHealth vs Medplum
- Health Gorilla vs Medblocks
- Health Gorilla vs Medplum
- Medblocks vs Metriport Medical API
- Medblocks vs Particle Health
- Medblocks vs Redox
- Medblocks vs Zus Health
- Medblocks vs ROOK
- Medblocks vs Terra API
- Medblocks vs Validic Inform
Machine-readable
- This page as Markdown
/compare/medblocks-vs-medplum.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/medblocks.json·/api/v1/tools/medplum.json - From a terminal
anchor compare medblocks medplum(the CLI) - Over MCP
compare_tools {"a": "medblocks", "b": "medplum"}at/mcp, no key