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

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.

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

CategoryWeight this runMedblocksMedplumEdge
Reliability16%202875Medplum +47
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26282Medplum +20
Agent ergonomics13%16.27273Medplum +1
Security & auth14%17.56774Medplum +7
Payments & pricing10%12.52525even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86993Medplum +24
Transparency & trust7%8.85172Medplum +21
Negative events≤150-2
TotalD 52.7/100B 68.7/100

Facts side by side

FactMedblocksMedplum
KindHTTP APIHTTP API
VendorMedblocks Inc.Orangebot, Inc. (dba Medplum)
Hosted endpointhttps://app.medblocks.com/mcphttps://api.medplum.com/mcp/stream
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, SSE (legacy)
AuthOAuth or keyOAuth
PricingFreemiumFreemium
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 fileApache 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 exposed103
Read-only variant documentednoyes
llms.txtyesyes
MCP registrynot listedcom.medplum/mcp
Last release2026-09-142026-10-08
Terms last updated2026-10-052023-04-11
Privacy policy last updated2026-10-052022-04-05
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 noticeyesyes
Arbitration or class-action waivernot found in the textyes
Popularity36 npm/wk2.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

  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

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

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

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.