Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Particlehealth is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Query Particle Health patient records across connected clinical networks.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http particlehealth-mcp https://particlehealth.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# particle_get_patient, particle_search_patient, particle_get_query_status and 8 more
Particlehealth costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http particlehealth-mcp https://particlehealth.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Fetch a single patient record by its Particle patient id. Endpoint: GET /api/v2/patients/{particle_patient_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| particle_patient_id | string | yes | Particle-assigned patient id (from submit/search). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| given_name | string | yes | Patient's legal first / given name. |
| family_name | string | yes | Patient's legal last / family name. |
| date_of_birth | string | yes | Date of birth, YYYY-MM-DD. |
| gender | string | yes | Administrative gender: MALE or FEMALE. |
| patient_id | string | yes | Your own external identifier for this patient (echoed back by Particle). |
| address_city | string | yes | City of the patient's home address. |
| address_state | string | yes | Two-letter US state code, e.g. NY. |
| postal_code | string | yes | 5-digit ZIP / postal code. |
| address_lines | array | no | Street address lines, e.g. ["123 Main St"]. |
| string | no | Patient email address. | |
| telephone | string | no | Patient phone number. |
| ssn | string | no | Social Security Number (optional; improves demographic match quality). |
| consent | array | no | Consent objects, if required by your Particle data-sharing agreement. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| particle_patient_id | string | yes | Particle-assigned patient id. |
| query_id | string | no | Specific query id; omit for the latest COMPLETE query. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| particle_patient_id | string | yes | Particle-assigned patient id. |
| _since | string | no | RFC3339 timestamp; only return resources updated since then. |
| _count | integer | no | Page size (max resources per page). |
| _page_token | string | no | Opaque token from a previous page's link to fetch the next page. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| particle_patient_id | string | yes | Particle-assigned patient id. |
| resource_type | string | yes | FHIR resource type, e.g. Condition, MedicationRequest, Observation, AllergyIntolerance. |
| _since | string | no | RFC3339 timestamp; only return resources updated since then. |
| _count | integer | no | Page size (max resources per page). |
| _page_token | string | no | Opaque token from a previous page's link to fetch the next page. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| particle_patient_id | string | yes | Particle-assigned patient id. |
| _since | string | no | RFC3339 timestamp; only return data updated since then. |
| domain | string | no | Filter to a single clinical domain, e.g. Condition, Medication, Encounter. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| particle_patient_id | string | yes | Particle-assigned patient id. |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | no | Two-letter US state code to filter participants, e.g. NY. |
| zipcode | string | no | 5-digit ZIP code to filter participants (ignored if state is set). |
| continuation_token | string | no | Token from a previous response to fetch the next page. |
List the documents uploaded / available for a patient. Endpoint: GET /api/v1/documents/{patient_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| patient_id | string | yes | Patient id whose documents to list. |
⚠️ 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| given_name | string | yes | Patient's legal first / given name. |
| family_name | string | yes | Patient's legal last / family name. |
| date_of_birth | string | yes | Date of birth, YYYY-MM-DD. |
| gender | string | yes | Administrative gender: MALE or FEMALE. |
| patient_id | string | yes | Your own external identifier for this patient (echoed back by Particle). |
| address_city | string | yes | City of the patient's home address. |
| address_state | string | yes | Two-letter US state code, e.g. NY. |
| postal_code | string | yes | 5-digit ZIP / postal code. |
| address_lines | array | no | Street address lines, e.g. ["123 Main St"]. |
| string | no | Patient email address. | |
| telephone | string | no | Patient phone number. |
| ssn | string | no | Social Security Number (optional; improves demographic match quality). |
| consent | array | no | Consent objects, if required by your Particle data-sharing agreement. |
⚠️ 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| particle_patient_id | string | yes | Particle-assigned patient id to run the query for. |
| purpose_of_use | string | yes | Purpose of use for the request, e.g. TREATMENT. |
| hints | array | no | Postal codes to hint where records may be found. |
| specialties | array | no | Specialties to focus the query, e.g. ["ONCOLOGY"]. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Particlehealth or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.11.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Particlehealth can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.