Healthclaw Guardrails vs Medplum MCP

A side-by-side look at the Healthclaw Guardrails and Medplum MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Healthclaw Guardrails logoHealthclaw GuardrailsBiology & Bioinformatics · Remote HTTP/SSEGuardrailed FHIR access for AI agents: PHI redaction, audit trail, step-up auth, tenant isolation63GoodAuth: not declaredMedplum MCP logoMedplum MCPBiology & BioinformaticsSecurely access and manage FHIR healthcare data stored in Medplum.41FairAuth: not declared

Verdict: choose Healthclaw Guardrails for biology & bioinformatics work over a hosted endpoint; choose Medplum MCP for biology & bioinformatics. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Healthclaw Guardrails logoChoose Healthclaw Guardrails when

  • You need dedicated capabilities in the Biology & Bioinformatics domain.
  • You prefer a remote HTTP/SSE transport.
  • You want tools like context_get, fhir_read, fhir_search.
Explore Healthclaw Guardrails

Medplum MCP logoChoose Medplum MCP when

  • You need dedicated capabilities in the Biology & Bioinformatics domain.
Explore Medplum MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecHealthclaw Guardrails logoHealthclaw GuardrailsMedplum MCP logoMedplum MCP
CategoryBiology & BioinformaticsBiology & Bioinformatics
Quality signal63/100 · Good41/100 · Fair
Install commandConfirmedNot confirmed yet
TransportRemote HTTP/SSE—
AuthNot declaredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars312,753
Directory activity 4 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools27Not listed

Tools & capabilities

Healthclaw Guardrails tools 27

  • context_getRetrieve a pre-built context envelope with patient-centric FHIR resources. Returns bounded, policy-stamped, time-limited context.
  • fhir_readRead a specific FHIR resource by type and ID. Supports FHIR R4 US Core v9 stable resources and FHIR R6 ballot3 experimental resources. Returns redacted resource with PHI protection.
  • fhir_searchSearch for FHIR resources. Supports FHIR R4 US Core v9 stable resources and FHIR R6 ballot3 experimental resources. Supports patient, code, status, _lastUpdated, _count, _sort parameters. Returns paginated, redacted Bundle.
  • fhir_validateValidate a proposed FHIR R6 resource against structural rules. Returns OperationOutcome.
  • questionnaire_populateSDC $populate — pre-fill a Questionnaire for a subject. Returns a QuestionnaireResponse. Read tier; mints a tenant token for non-public tenants.
  • questionnaire_extractSDC $extract — extract FHIR resources from a completed QuestionnaireResponse into a transaction Bundle. Write tier; requires step-up authorization, including for dry_run=true previews.
  • fhir_propose_writePropose a write — validates the resource and returns a preview. Does NOT commit. Write tier: step-up authorization is required and is supplied by the deployment as an X-Step-Up-Token header. You cannot obtain or pass it yourself. If it is absent this returns requires_step_up; tell the patient authorization is needed rather than attempting another route.
  • fhir_commit_writeCommit a previously proposed write. Requires step-up authorization token. This is a destructive operation.
  • fhir_statsCompute statistics (count, min, max, mean) over numeric Observation values. Standard FHIR $stats (since R4). Only supports valueQuantity. Filter by patient and/or code.
  • fhir_interpret_labsInterpret lab Observations against reference ranges — flags each value low/normal/high/critical (HL7 v3 ObservationInterpretation) and returns clinician + consumer summaries. Decision support, not diagnosis. Read-tier. Response includes _meta.ui.resourceUri pointing to an embeddable trend timeline.
  • care_gapsCheck which preventive-care screenings/immunizations a patient may be due for (blood pressure, cholesterol, colorectal/cervical/breast cancer screening, flu, diabetes A1c), from their own connected records. Decision support based on USPSTF/ACIP/ADA guidelines — not a diagnosis or directive. Response includes _meta.ui.resourceUri pointing to an embeddable review UI.
  • guardrail_conformanceRun the guardrail conformance self-test on the connected HealthClaw deployment and return the graded scorecard across seven guardrail properties: PHI redaction, immutable audit, step-up auth, human-in-the-loop, tenant isolation, medical disclaimers, and error fidelity. Uses synthetic data only. Set fresh=true to force a new run instead of the cached result.
  • +15 more on the listing page

Medplum MCP tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Healthclaw Guardrails

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "healthclaw-guardrails": {
      "url": "https://mcp-server-production-5112.up.railway.app/mcp"
    }
  }
}

Medplum MCP

No confirmed install command for Medplum MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Healthclaw Guardrails is categorized under Biology & Bioinformatics and uses a remote HTTP/SSE transport. Medplum MCP belongs to Biology & Bioinformatics and uses an install path we have not confirmed yet. Pick Healthclaw Guardrails for biology & bioinformatics work and Medplum MCP for biology & bioinformatics.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Medplum MCP has no confirmed install command yet — follow its own setup instructions.

Healthclaw Guardrails is listed as free. Medplum MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add healthclaw-guardrails and mcp-112 as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Healthclaw Guardrails has a quality signal of 63/100 (Good) with 4 views, 0 installs and 31 GitHub stars. Medplum MCP has 41/100 (Fair) with 2 views, 0 installs and 2,753 GitHub stars.