Particle Health MCP by usefulapi
REMOTE · PARTICLEHEALTH.USEFULAPI.IO
Query Particle Health patient records across connected clinical networks.
Available components
Last scanned (15 hours ago)
Scores higher than 3% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Nov 26 −61
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 +4
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 0
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 0
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 +1
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://particlehealth.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 11 Nov 2026 | 9 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 93e2fea3bbc31354138c8a47c5e87592 |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of particlehealth.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://particlehealth.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/particlehealth/ |
| http (plaintext) | http://particlehealth.usefulapi.io/mcp | Inconclusive | 302 | http://particlehealth.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
particle_create_query Create clinical-record query (WRITE) ~133
⚠️ 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.
| Name | Type | Req | Description |
|---|---|---|---|
| hints | array | – | Postal codes to hint where records may be found. |
| 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. |
| specialties | array | – | Specialties to focus the query, e.g. ["ONCOLOGY"]. |
No output schema declared.
No examples provided.
particle_get_ccda Get C-CDA document(s) ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| particle_patient_id | string | yes | Particle-assigned patient id. |
No output schema declared.
No examples provided.
particle_get_fhir Get FHIR bundle ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _count | integer | – | Page size (max resources per page). |
| _page_token | string | – | Opaque token from a previous page's `link` to fetch the next page. |
| _since | string | – | RFC3339 timestamp; only return resources updated since then. |
| particle_patient_id | string | yes | Particle-assigned patient id. |
No output schema declared.
No examples provided.
particle_get_fhir_by_type Get FHIR resources by type ~166
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| _count | integer | – | Page size (max resources per page). |
| _page_token | string | – | Opaque token from a previous page's `link` to fetch the next page. |
| _since | string | – | RFC3339 timestamp; only return resources updated since then. |
| particle_patient_id | string | yes | Particle-assigned patient id. |
| resource_type | string | yes | FHIR resource type, e.g. Condition, MedicationRequest, Observation, AllergyIntolerance. |
No output schema declared.
No examples provided.
particle_get_flat Get flattened clinical data ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _since | string | – | RFC3339 timestamp; only return data updated since then. |
| domain | string | – | Filter to a single clinical domain, e.g. Condition, Medication, Encounter. |
| particle_patient_id | string | yes | Particle-assigned patient id. |
No output schema declared.
No examples provided.
particle_get_patient Get patient record ~53
Fetch a single patient record by its Particle patient id. Endpoint: GET /api/v2/patients/{particle_patient_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| particle_patient_id | string | yes | Particle-assigned patient id (from submit/search). |
No output schema declared.
No examples provided.
particle_get_patient_documents List patient documents ~47
List the documents uploaded / available for a patient. Endpoint: GET /api/v1/documents/{patient_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| patient_id | string | yes | Patient id whose documents to list. |
No output schema declared.
No examples provided.
particle_get_query_status Get query status ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| particle_patient_id | string | yes | Particle-assigned patient id. |
| query_id | string | – | Specific query id; omit for the latest COMPLETE query. |
No output schema declared.
No examples provided.
particle_search_network_participants Search network participants ~122
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).
| Name | Type | Req | Description |
|---|---|---|---|
| continuation_token | string | – | Token from a previous response to fetch the next page. |
| state | string | – | Two-letter US state code to filter participants, e.g. NY. |
| zipcode | string | – | 5-digit ZIP code to filter participants (ignored if `state` is set). |
No output schema declared.
No examples provided.
particle_search_patient Search for a patient ~255
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address_city | string | yes | City of the patient's home address. |
| address_lines | array | – | Street address lines, e.g. ["123 Main St"]. |
| address_state | string | yes | Two-letter US state code, e.g. NY. |
| consent | array | – | Consent objects, if required by your Particle data-sharing agreement. |
| date_of_birth | string | yes | Date of birth, YYYY-MM-DD. |
| string | – | Patient email address. | |
| family_name | string | yes | Patient's legal last / family name. |
| gender | string | yes | Administrative gender: MALE or FEMALE. |
| given_name | string | yes | Patient's legal first / given name. |
| patient_id | string | yes | Your own external identifier for this patient (echoed back by Particle). |
| postal_code | string | yes | 5-digit ZIP / postal code. |
| ssn | string | – | Social Security Number (optional; improves demographic match quality). |
| telephone | string | – | Patient phone number. |
No output schema declared.
No examples provided.
particle_submit_patient Submit (register) patient (WRITE) ~255
⚠️ 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.
| Name | Type | Req | Description |
|---|---|---|---|
| address_city | string | yes | City of the patient's home address. |
| address_lines | array | – | Street address lines, e.g. ["123 Main St"]. |
| address_state | string | yes | Two-letter US state code, e.g. NY. |
| consent | array | – | Consent objects, if required by your Particle data-sharing agreement. |
| date_of_birth | string | yes | Date of birth, YYYY-MM-DD. |
| string | – | Patient email address. | |
| family_name | string | yes | Patient's legal last / family name. |
| gender | string | yes | Administrative gender: MALE or FEMALE. |
| given_name | string | yes | Patient's legal first / given name. |
| patient_id | string | yes | Your own external identifier for this patient (echoed back by Particle). |
| postal_code | string | yes | 5-digit ZIP / postal code. |
| ssn | string | – | Social Security Number (optional; improves demographic match quality). |
| telephone | string | – | Patient phone number. |
No output schema declared.
No examples provided.
How do I install the Particle Health MCP by usefulapi server?
Particle Health MCP by usefulapi is a hosted endpoint at https://particlehealth.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · particlehealth.usefulapi.io
claude mcp add --transport http io-usefulapi-particlehealth 'https://particlehealth.usefulapi.io/mcp'
What is the Particle Health MCP by usefulapi server?
Particle Health MCP by usefulapi is listed in the public MCP registry as io.usefulapi/particlehealth. Query Particle Health patient records across connected clinical networks. This page covers its hosted endpoint (https://particlehealth.usefulapi.io/mcp).
Is the Particle Health MCP by usefulapi server safe to use?
Particle Health MCP by usefulapi scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Particle Health MCP by usefulapi server expose?
Particle Health MCP by usefulapi exposes 11 tools: particle_get_patient, particle_search_patient, particle_get_query_status, particle_get_fhir, particle_get_fhir_by_type, and 6 more. Their descriptions and schemas cost roughly 1,423 tokens of context every time the server is loaded.
Does the Particle Health MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Particle Health MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Particle Health MCP by usefulapi server still maintained?
Particle Health MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Particle Health MCP by usefulapi server?
VerifyMCP ran 4 checks on Particle Health MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Particle Health MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.