Particle Health MCP by usefulapi
io.usefulapi/particlehealthusefulapi.iostreamable-httpv1.41.0Scanned
Query Particle Health patient records across connected clinical networks.
11 tools: 2 can delete or cancel things and 9 only read.
- Reads private data · 3
- Reads text others write · 0
- Can send data out · 0
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
2 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Particle Health MCP by usefulapi can do
The Particle Health MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 11 tools. It can delete or cancel things (2 tools: particle_submit_patient and particle_create_query). 9 tools only read.
3 tools read private data (particle_get_query_status, particle_get_ccda and particle_get_patient_documents).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.41.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
11 tools
Deletes or cancels 2Claude Code: deny
particle_create_query⚠[U+FE0F] WRITE: initiate a nationwide clinical-record retrieval for a patient.No findings
Why it is in this group
- The name "particle_create_query" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote itContains invisible characters, shown as [U+…] ⚠[U+FE0F] 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.
Annotations the server declares
- title: Create clinical-record query (WRITE)
- destructiveHint: true
particle_submit_patient⚠[U+FE0F] WRITE: register a new patient with Particle Health.No findings
Why it is in this group
- The name "particle_submit_patient" says "submit": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote itContains invisible characters, shown as [U+…] ⚠[U+FE0F] 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.
Annotations the server declares
- title: Submit (register) patient (WRITE)
- destructiveHint: true
Only reads 9Show 9 read-only tools
particle_get_ccdaRetrieve the patient's C-CDA clinical document(s).Reads private dataNo findings
Why it is in this group
- The name "particle_get_ccda" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "retrieve" and "document": it reads documents.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get C-CDA document(s)
- readOnlyHint: true
particle_get_fhirRetrieve the patient's complete clinical record as a FHIR searchset Bundle.No findings
Why it is in this group
- The name "particle_get_fhir" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get FHIR bundle
- readOnlyHint: true
particle_get_fhir_by_typeRetrieve only one FHIR resource type for a patient (e.g.No findings
Why it is in this group
- The name "particle_get_fhir_by_type" says "get": a word for reading.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Get FHIR resources by type
- readOnlyHint: true
particle_get_flatRetrieve the patient's clinical data in Particle's flattened (de-nested) format, easier to read than raw FHIR.No findings
Why it is in this group
- The name "particle_get_flat" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get flattened clinical data
- readOnlyHint: true
particle_get_patientFetch a single patient record by its Particle patient id.No findings
Why it is in this group
- The name "particle_get_patient" says "get": a word for reading.
Description, as the server wrote it Fetch a single patient record by its Particle patient id. Endpoint: GET /api/v2/patients/{particle_patient_id}.
Annotations the server declares
- title: Get patient record
- readOnlyHint: true
particle_get_patient_documentsList the documents uploaded / available for a patient.Reads private dataNo findings
Why it is in this group
- The name "particle_get_patient_documents" says "get": a word for reading.
What it can reach
- private-dataThe name "particle_get_patient_documents" says "get" and "document": it reads documents.
- private-dataThe description's first sentence says "list" and "document": it reads documents.
Description, as the server wrote it List the documents uploaded / available for a patient. Endpoint: GET /api/v1/documents/{patient_id}.
Annotations the server declares
- title: List patient documents
- readOnlyHint: true
particle_get_query_statusGet the status of a clinical-record retrieval query (state, timing, demographics, files).Reads private dataNo findings
Why it is in this group
- The name "particle_get_query_status" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "file": it reads files.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get query status
- readOnlyHint: true
particle_search_network_participantsList the health-data network participants (organizations Particle can query).No findings
Why it is in this group
- The name "particle_search_network_participants" says "search": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- title: Search network participants
- readOnlyHint: true
particle_search_patientSearch for an existing patient by demographics (non-mutating).No findings
Why it is in this group
- The name "particle_search_patient" says "search": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Search for a patient
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data3
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://particlehealth.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://particlehealth.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://particlehealth.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://particlehealth.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.41.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http particlehealth https://particlehealth.usefulapi.io/mcpclaude mcp add --transport http particlehealth https://particlehealth.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__particlehealth__particle_get_patient",
"mcp__particlehealth__particle_search_patient",
"mcp__particlehealth__particle_get_query_status",
"mcp__particlehealth__particle_get_fhir",
"mcp__particlehealth__particle_get_fhir_by_type",
"mcp__particlehealth__particle_get_flat",
"mcp__particlehealth__particle_get_ccda",
"mcp__particlehealth__particle_search_network_participants",
"mcp__particlehealth__particle_get_patient_documents"
],
"ask": [],
"deny": [
"mcp__particlehealth__particle_submit_patient",
"mcp__particlehealth__particle_create_query"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as particlehealth. Review it before you use it.
Capability tags behind 3 rules
- mcp__particlehealth__particle_get_query_status private-data
- mcp__particlehealth__particle_get_ccda private-data
- mcp__particlehealth__particle_get_patient_documents private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/particlehealth/verify?hash=bdcb2ffc29b37b62f5b6c7e6d108e8d399506ce9c7522e19dc79db9e99907df6" | jq -e '.changed == false'Pinned hash bdcb2ffc29b3, from Oct 25, 2026, 23:19 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/particlehealth/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/particlehealth)Source: MCP Registry · repository. Synced Nov 21, 2026, 08:17 UTC.
Particle Health MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Particle Health MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 11 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Particle Health MCP by usefulapi delete data?
- Yes. 2 tools can delete, cancel or revoke something: particle_submit_patient and particle_create_query.
Can the Particle Health MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Particle Health MCP by usefulapi have?
- 11 tools: 2 destructive, 9 read. particle_submit_patient, particle_create_query, particle_get_patient, particle_search_patient, particle_get_query_status, particle_get_fhir, particle_get_fhir_by_type, particle_get_flat and 3 more.
Does the Particle Health MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Particle Health MCP by usefulapi send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Particle Health MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.