Elation Health MCP by usefulapi
REMOTE · ELATION-HEALTH.USEFULAPI.IO
Read Elation Health patients, appointments, problems, allergies, medications, notes and vitals.
Available components
Last scanned (7 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 17 Oct 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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
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 Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2172 tokens (~155/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +3
- The server rewrote its instructions, which are the text every model session reads security
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “getting_started” functional
- Server version: 1.0.0 → 1.1.0 functional
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 60
First indexed and scored.
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 17 Oct 2026 · Probed https://elation-health.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 | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| 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 elation-health.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://elation-health.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://elation-health.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://elation-health.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://elation-health.usefulapi.io/mcp |
| Authorisation server | https://elation-health.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://elation-health.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/elation-health/ |
| http (plaintext) | http://elation-health.usefulapi.io/mcp | Inconclusive | 302 | http://elation-health.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 →
elationhealth_get_appointment Get an appointment ~66
Get one appointment by id: scheduled date, duration, status, reason, instructions, patient, physician, practice, service location, telehealth and billing details. Elation: GET /appointments/{id}/.
| Name | Type | Req | Description |
|---|---|---|---|
| appointment_id | integer | yes | Elation appointment id. |
No output schema declared.
No examples provided.
elationhealth_get_patient Get a patient ~76
Get one patient chart header by id (PHI): demographics, contact details, address, insurance, emergency contact, primary physician, tags. The SSN is redacted. Elation: GET /patients/{id}/.
| Name | Type | Req | Description |
|---|---|---|---|
| patient_id | integer | yes | Elation patient id (from elationhealth_list_patients). |
No output schema declared.
No examples provided.
elationhealth_get_visit_note Get a visit note ~70
Get one visit note by id (PHI): visit date, type, physician, signed state and the full note body. Elation: GET /visit_notes/{id}/.
| Name | Type | Req | Description |
|---|---|---|---|
| visit_note_id | integer | yes | Elation visit note id (from elationhealth_list_visit_notes). |
No output schema declared.
No examples provided.
elationhealth_list_allergies List a patient's allergies ~125
List one patient's allergies (PHI): allergen name, reaction, severity, status, start date. Elation: GET /allergies/?patient=.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Cursor from a previous reply's next_cursor, to get the next page. |
| limit | integer | – | Page size (default 25, max 100). |
| offset | integer | – | Offset paging instead of a cursor (the reply then has count and next_offset). |
| patient | integer | yes | Elation patient id (from elationhealth_list_patients). |
No output schema declared.
No examples provided.
elationhealth_list_appointment_types List appointment types ~119
List the appointment types (visit reasons with default duration) a practice offers. Elation: GET /appointment_types/.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Cursor from a previous reply's next_cursor, to get the next page. |
| limit | integer | – | Page size (default 25, max 100). |
| name | string | – | Filter by name. |
| offset | integer | – | Offset paging instead of a cursor (the reply then has count and next_offset). |
| practice | integer | – | Only this practice's appointment types. |
No output schema declared.
No examples provided.
elationhealth_list_appointments List appointments ~208
List appointments and calendar time slots, filterable by date range, patient, physician and practice. Each has the scheduled date, duration, status, reason, patient, physician and service location. Elation: GET /appointments/.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Cursor from a previous reply's next_cursor, to get the next page. |
| from_date | string | – | Start of the range (ISO date or date-time). |
| limit | integer | – | Page size (default 25, max 100). |
| offset | integer | – | Offset paging instead of a cursor (the reply then has count and next_offset). |
| patient | integer | – | Only this patient's appointments (patient id). |
| physician | integer | – | Only this physician's appointments (physician id). |
| practice | integer | – | Only this practice's appointments. |
| time_slot_type | string | – | Kind of calendar entry. |
| to_date | string | – | End of the range (ISO date or date-time). |
No output schema declared.
No examples provided.
elationhealth_list_medications List a patient's medications ~184
List one patient's medication documents (PHI): drug name, strength, directions, quantity, authorized refills, prescribing physician, start date, and the discontinue order if any. Current and discontinued entries both appear unless you filter. Elation: GET /medications/?patient=.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Cursor from a previous reply's next_cursor, to get the next page. |
| discontinued | boolean | – | true = only medications with a discontinue order, false = only those without. |
| limit | integer | – | Page size (default 25, max 100). |
| offset | integer | – | Offset paging instead of a cursor (the reply then has count and next_offset). |
| patient | integer | yes | Elation patient id (from elationhealth_list_patients). |
| permanent | boolean | – | true = only permanent (chronic) medications. |
No output schema declared.
No examples provided.
elationhealth_list_non_visit_notes List a patient's non-visit notes ~131
List one patient's non-visit notes (PHI): free-text chart notes outside a visit, such as phone calls and administrative notes. Elation: GET /non_visit_notes/?patient=.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Cursor from a previous reply's next_cursor, to get the next page. |
| limit | integer | – | Page size (default 25, max 100). |
| offset | integer | – | Offset paging instead of a cursor (the reply then has count and next_offset). |
| patient | integer | yes | Elation patient id (from elationhealth_list_patients). |
No output schema declared.
No examples provided.
elationhealth_list_patients List patients ~213
Search the practice's patient charts (PHI): id, name, date of birth, sex, contact details, address, status. First and last name match exactly (case-insensitive, no partial names). The SSN is redacted. Elation: GET /patients/.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Cursor from a previous reply's next_cursor, to get the next page. |
| dob | string | – | Date of birth, YYYY-MM-DD. |
| first_name | string | – | Exact, case-insensitive first name. |
| last_modified_after | string | – | Only patients changed after this date or date-time. |
| last_name | string | – | Exact, case-insensitive last name. |
| limit | integer | – | Page size (default 25, max 100). |
| offset | integer | – | Offset paging instead of a cursor (the reply then has count and next_offset). |
| phone_number | string | – | Phone number. |
| practice | integer | – | Only patients of this practice id. |
No output schema declared.
No examples provided.
elationhealth_list_physicians List physicians ~145
List the practice's physicians (providers): id, name, NPI, specialty, credentials, license, practice, user id. Elation: GET /physicians/.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Cursor from a previous reply's next_cursor, to get the next page. |
| first_name | string | – | Filter by first name. |
| last_name | string | – | Filter by last name. |
| limit | integer | – | Page size (default 25, max 100). |
| npi | string | – | Filter by 10-digit NPI. |
| offset | integer | – | Offset paging instead of a cursor (the reply then has count and next_offset). |
No output schema declared.
No examples provided.
elationhealth_list_practices List practices ~107
List the practices this API key can access: id, name, address, status, time zone, physicians and service locations. Elation: GET /practices/.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Cursor from a previous reply's next_cursor, to get the next page. |
| limit | integer | – | Page size (default 25, max 100). |
| offset | integer | – | Offset paging instead of a cursor (the reply then has count and next_offset). |
No output schema declared.
No examples provided.
elationhealth_list_problems List a patient's problems ~152
List one patient's problem list (PHI): description, ICD-9/ICD-10/SNOMED codes, status (Active, Controlled, Resolved), start and resolved dates, synopsis. Elation: GET /problems/?patient=.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Cursor from a previous reply's next_cursor, to get the next page. |
| limit | integer | – | Page size (default 25, max 100). |
| offset | integer | – | Offset paging instead of a cursor (the reply then has count and next_offset). |
| patient | integer | yes | Elation patient id (from elationhealth_list_patients). |
| status | string | – | Problem status. |
No output schema declared.
No examples provided.
elationhealth_list_visit_notes List a patient's visit notes ~213
List one patient's visit notes (PHI): visit date, type, physician, signed state and the note body (bullets by category such as Subjective, Objective, Assessment, Plan). Filter by signed date or last change. Elation: GET /visit_notes/?patient=.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Cursor from a previous reply's next_cursor, to get the next page. |
| from_signed_date | string | – | Only notes signed on or after this date or date-time. |
| limit | integer | – | Page size (default 25, max 100). |
| offset | integer | – | Offset paging instead of a cursor (the reply then has count and next_offset). |
| patient | integer | yes | Elation patient id (from elationhealth_list_patients). |
| physician | integer | – | Only notes of this physician id. |
| to_signed_date | string | – | Only notes signed on or before this date or date-time. |
| unsigned | boolean | – | true = only unsigned notes. |
No output schema declared.
No examples provided.
elationhealth_list_vitals List a patient's vitals ~154
List one patient's vital signs (PHI): height, weight, BMI, blood pressure, heart rate, respiratory rate, temperature, oxygen saturation, pain, with chart dates. Elation: GET /vitals/?patient=.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Cursor from a previous reply's next_cursor, to get the next page. |
| limit | integer | – | Page size (default 25, max 100). |
| offset | integer | – | Offset paging instead of a cursor (the reply then has count and next_offset). |
| patient | integer | yes | Elation patient id (from elationhealth_list_patients). |
| visit_note | integer | – | Only vitals recorded in this visit note id. |
No output schema declared.
No examples provided.
How do I install the Elation Health MCP by usefulapi server?
Elation Health MCP by usefulapi is a hosted endpoint at https://elation-health.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 · elation-health.usefulapi.io
claude mcp add --transport http io-usefulapi-elation-health 'https://elation-health.usefulapi.io/mcp'
What is the Elation Health MCP by usefulapi server?
Elation Health MCP by usefulapi is listed in the public MCP registry as io.usefulapi/elation-health. Read Elation Health patients, appointments, problems, allergies, medications, notes and vitals. This page covers its hosted endpoint (https://elation-health.usefulapi.io/mcp).
Is the Elation Health MCP by usefulapi server safe to use?
Elation Health MCP by usefulapi scores 64 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 Elation Health MCP by usefulapi server expose?
Elation Health MCP by usefulapi exposes 14 tools: elationhealth_list_patients, elationhealth_get_patient, elationhealth_list_appointments, elationhealth_get_appointment, elationhealth_list_appointment_types, and 9 more. Their descriptions and schemas cost roughly 1,963 tokens of context every time the server is loaded.
Does the Elation Health MCP by usefulapi server require authentication?
Yes. Elation Health MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Elation Health MCP by usefulapi server still maintained?
Elation Health MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.