Particle Health MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

Particle Health MCP by usefulapi is answering right now. Last checked 8 min ago. It exposes 11 tools. Last commit 12 Oct 2026.

Query Particle Health patient records across connected clinical networks.

Uptime history 13 days of history

13 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

92 ms

Response time

average over 24h

Stars

last commit 12 Oct 2026

What changed 6

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 30 September 2026. No other catalogue keeps this.

9 Oct a tool changed version4 times that day

1 Oct a tool changed version

30 Sep a tool changed version

and 3 more, back to 30 September 2026

Nothing serious here today

Today is the operative word: we check Particle Health MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add particlehealth --transport http https://particlehealth.usefulapi.io/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "particlehealth": {
      "url": "https://particlehealth.usefulapi.io/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.particlehealth]
url = "https://particlehealth.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "particlehealth": {
      "url": "https://particlehealth.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "particlehealth": {
      "url": "https://particlehealth.usefulapi.io/mcp"
    }
  }
}

Available tools 11

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

particle

particle_create_query

⚠️ WRITE: initiate a nationwide clinical-record retrieval for a patient. Returns a query_id — poll particle_get_query_status for progress. Endpoint: POST /api/v2/patients/{particle_patient_id}/query.

particle_get_ccda

Retrieve the patient's C-CDA clinical document(s). May be large and returned as XML/text — parsed if JSON, otherwise passed through as-is. Endpoint: GET /api/v2/patients/{particle_patient_id}/ccda.

particle_get_fhir

Retrieve the patient's complete clinical record as a FHIR searchset Bundle. Supports incremental sync and pagination. Endpoint: GET /api/v2/patients/{particle_patient_id}/fhir.

particle_get_fhir_by_type

Retrieve only one FHIR resource type for a patient (e.g. Condition, MedicationRequest, Observation) as a Bundle. Supports the same pagination as particle_get_fhir. Endpoint: GET /api/v2/patients/{particle_patient_id}/fhir/{type}.

particle_get_flat

Retrieve the patient's clinical data in Particle's flattened (de-nested) format, easier to read than raw FHIR. Optionally filter to one domain. Endpoint: GET /api/v2/patients/{particle_patient_id}/flat.

particle_get_patient

Fetch a single patient record by its Particle patient id. Endpoint: GET /api/v2/patients/{particle_patient_id}.

particle_get_patient_documents

List the documents uploaded / available for a patient. Endpoint: GET /api/v1/documents/{patient_id}.

particle_get_query_status

Get the status of a clinical-record retrieval query (state, timing, demographics, files). Omit query_id to get the latest COMPLETE query. Endpoint: GET /api/v2/patients/{particle_patient_id}/query.

particle_search_network_participants

List the health-data network participants (organizations Particle can query). Optionally filter by state or zipcode, and page with continuation_token. Endpoint: GET /api/v1/networkparticipants (with /state/{state} and /zipcode/{zip} variants).

particle_search_patient

Search for an existing patient by demographics (non-mutating). Returns an array of matching patient objects (or a 204 message when none match). Endpoint: POST /api/v2/patients/search.

particle_submit_patient

⚠️ WRITE: register a new patient with Particle Health. Returns the patient with a system-generated particle_patient_id (use it for subsequent queries). Endpoint: POST /api/v2/patients.

Endpoints

URL	Transport	State	Latency	Checked
https://particlehealth.usefulapi.io/mcp	streamable-http	answering	67 ms	8 min ago

Alternatives to Particle Health MCP by usefulapi

same job, measured the same way

Health Gorilla MCP by usefulapi

by usefulapi

Query Health Gorilla FHIR patients, conditions, medications and lab results.

16 tools answering

Metriport MCP by usefulapi

by usefulapi

Read and write patients, facilities, medical documents, and consolidated FHIR records in Metriport.

12 tools answering

DrChrono MCP by usefulapi

by usefulapi

Read and write DrChrono patients, appointments, offices and clinical notes.

15 tools answering

Healthie MCP by usefulapi

by usefulapi

Hosted MCP server for the Healthie EHR & telehealth API: patients, appointments, charting, tasks.

16 tools answering

Hint Health MCP by usefulapi

by usefulapi

Read Hint Health patients, memberships, plans, invoices and payments for direct primary care.

17 tools answering

NexHealth MCP by usefulapi

by usefulapi

Read and write NexHealth appointments, patients, providers and locations.

16 tools answering

Akute Health MCP by usefulapi

by usefulapi

Read Akute Health patients, appointments, tasks, notes, medications, allergies and observations.

15 tools answering

Elation Health MCP by usefulapi

by usefulapi

Read Elation Health patients, appointments, problems, allergies, medications, notes and vitals.

14 tools answering

Particle Health MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Particle Health MCP by usefulapi do?

It exposes 11 tools, read directly from the server on our last check. Among them: particle_create_query, particle_get_ccda, particle_get_fhir, particle_get_fhir_by_type, particle_get_flat, particle_get_patient and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Particle Health MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 92 ms. The bar chart above shows every period we have measured.

How do I connect Particle Health MCP by usefulapi?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Particle Health MCP by usefulapi need an API key?

No. Particle Health MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Particle Health MCP by usefulapi?

It answers our handshake in 92 ms on average, which is faster than 87% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Particle Health MCP by usefulapi open source?

Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.