Healthie MCP by usefulapi
REMOTE · HEALTHIE.USEFULAPI.IO
Hosted MCP server for the Healthie EHR & telehealth API: patients, appointments, charting, tasks.
Available components
Last scanned (5 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 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.
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.
- 2 Nov 26 −62
- 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
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “add_an_internal_to_do_for_the_team” functional
- New prompt “check_practice_details_and_account” functional
- New prompt “list_the_practice_s_charting_and_intake_form_templates” functional
- New prompt “list_the_practice_s_services” 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 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 0
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.0 → 1.21.3 functional
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.20.0 → 1.21.0 functional
- Server version: 1.19.0 → 1.20.0 functional
- Server version: 1.17.0 → 1.19.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 5 Nov 2026 · Probed https://healthie.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 healthie.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | 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://healthie.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/healthie/ |
| http (plaintext) | http://healthie.usefulapi.io/mcp | Inconclusive | 302 | http://healthie.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 →
healthie_create_note Create a note / chat entry (WRITE — creates a record) ~100
Creates a note/chat entry in Healthie (additive). Requires content (the note text); optionally attach it to a client (user_id) or mark it as an org chat. GraphQL: mutation createNote(input: createNoteInput).
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The note text. |
| org_chat | boolean | – | True if created in the organization chat context. |
| user_id | string | – | The client/user the note is about. |
No output schema declared.
No examples provided.
healthie_create_task Create a task (WRITE — creates a record) ~128
Creates a task in Healthie (additive). Requires content (the task text); optionally attach it to a client (user_id), set a due_date, priority, or created_by_id. GraphQL: mutation createTask(input: createTaskInput).
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The task text/description. |
| created_by_id | string | – | Id of the user creating the task. |
| due_date | string | – | Due date (YYYY-MM-DD). |
| priority | integer | – | Priority (integer). |
| user_id | string | – | The client/user the task is about. |
No output schema declared.
No examples provided.
healthie_current_user Current user / account ~43
Fetch the authenticated Healthie account (the provider/user that owns the API key). Good first call to verify auth. Read-only. GraphQL: query currentUser.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
healthie_get_appointment Get an appointment ~38
Fetch a single appointment by id. Read-only. GraphQL: query appointment(id).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The appointment id. |
No output schema declared.
No examples provided.
healthie_get_organization Get organization ~37
Fetch the current organization / practice (name, NPI, contact, user counts). Read-only. GraphQL: query organization.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
healthie_get_user Get a user / patient ~42
Fetch a single user (patient or provider) by id. Read-only. GraphQL: query user(id).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The user id. |
No output schema declared.
No examples provided.
healthie_list_appointment_types List appointment types ~89
List the practice's appointment types (services), optionally keyword-filtered. Read-only. GraphQL: query appointmentTypes(keywords, offset, page_size, should_paginate).
| Name | Type | Req | Description |
|---|---|---|---|
| keywords | string | – | Free-text search over appointment type names. |
| offset | integer | – | Pagination offset. Default 0. |
| page_size | integer | – | Results per page. Default 25. |
No output schema declared.
No examples provided.
healthie_list_appointments List appointments ~167
List appointments, optionally filtered by patient, provider, date range, time-filter or status. Read-only. GraphQL: query appointments(user_id, provider_id, filter, startDate, endDate, filter_by_appointment_status).
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | – | End date (YYYY-MM-DD) to bound results. |
| filter | string | – | Time filter: "future" (default), "past", "ended", "didnt-occur". |
| filter_by_appointment_status | string | – | Filter by appointment status label. |
| provider_id | string | – | Filter to appointments for this provider id. |
| startDate | string | – | Start date (YYYY-MM-DD) to bound results. |
| user_id | string | – | Filter to appointments for this patient/client id. |
No output schema declared.
No examples provided.
healthie_list_conversations List conversations ~54
List messaging conversations, optionally between the current user and a given user. Read-only. GraphQL: query conversations(user_id).
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | – | Get conversations between the current user and this user id. |
No output schema declared.
No examples provided.
healthie_list_documents List documents ~109
List documents, optionally scoped to a patient (viewable_user_id) or by keyword. Read-only. GraphQL: query documents(viewable_user_id, keywords, offset, page_size, should_paginate).
| Name | Type | Req | Description |
|---|---|---|---|
| keywords | string | – | Free-text search over document names. |
| offset | integer | – | Pagination offset. Default 0. |
| page_size | integer | – | Results per page. Default 25. |
| viewable_user_id | string | – | Patient id whose documents to list. |
No output schema declared.
No examples provided.
healthie_list_form_answer_groups List completed forms / charting notes ~105
List completed form submissions (charting notes / filled intake forms), optionally scoped to a patient or a form template. Read-only. GraphQL: query formAnswerGroups(user_id, custom_module_form_id, should_paginate, offset).
| Name | Type | Req | Description |
|---|---|---|---|
| custom_module_form_id | string | – | Filter to submissions of this form template id. |
| offset | integer | – | Pagination offset. Default 0. |
| user_id | string | – | Filter to submissions for this patient id. |
No output schema declared.
No examples provided.
healthie_list_forms List charting / intake form templates ~105
List custom module form templates (charting notes, intake forms), optionally by keyword or category. Read-only. GraphQL: query customModuleForms(keywords, category, offset, page_size, should_paginate).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by form category. |
| keywords | string | – | Free-text search over form names. |
| offset | integer | – | Pagination offset. Default 0. |
| page_size | integer | – | Results per page. Default 25. |
No output schema declared.
No examples provided.
healthie_list_goals List goals ~79
List goals, optionally scoped to a patient. Read-only. GraphQL: query goals(user_id, offset, per_page).
| Name | Type | Req | Description |
|---|---|---|---|
| offset | integer | – | Pagination offset. Default 0. |
| per_page | integer | – | Results per page. Default 25. |
| user_id | string | – | Filter to goals for this patient id. |
No output schema declared.
No examples provided.
healthie_list_metric_entries List metric entries ~116
List tracked metric entries (weight, blood pressure, etc.), optionally scoped to a client or a category. Read-only. GraphQL: query entries(client_id, category, offset, page_size).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Entry category, e.g. "MetricEntry", "Weight". |
| client_id | string | – | Filter to entries for this client id. |
| offset | integer | – | Pagination offset. Default 0. |
| page_size | integer | – | Results per page (max 500). Default 25. |
No output schema declared.
No examples provided.
healthie_list_patients List patients / clients ~112
List patients/clients, optionally filtered by keyword search or active status. Read-only. GraphQL: query users(keywords, offset, page_size, should_paginate, active_status).
| Name | Type | Req | Description |
|---|---|---|---|
| active_status | string | – | Filter by status: "active" or "archived". |
| keywords | string | – | Free-text search over name/email. |
| offset | integer | – | Pagination offset. Default 0. |
| page_size | integer | – | Results per page (max 100). Default 25. |
No output schema declared.
No examples provided.
healthie_list_tasks List tasks ~107
List tasks, optionally scoped to a client or filtered by completion status. Read-only. GraphQL: query tasks(client_id, completed_status, offset, per_page).
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | – | Filter to tasks about this client id. |
| completed_status | string | – | Completion filter, e.g. "complete" or "incomplete". |
| offset | integer | – | Pagination offset. Default 0. |
| per_page | integer | – | Results per page. Default 25. |
No output schema declared.
No examples provided.
How do I install the Healthie MCP by usefulapi server?
Healthie MCP by usefulapi is a hosted endpoint at https://healthie.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 · healthie.usefulapi.io
claude mcp add --transport http io-usefulapi-healthie 'https://healthie.usefulapi.io/mcp'
What is the Healthie MCP by usefulapi server?
Healthie MCP by usefulapi is listed in the public MCP registry as io.usefulapi/healthie. Hosted MCP server for the Healthie EHR & telehealth API: patients, appointments, charting, tasks. This page covers its hosted endpoint (https://healthie.usefulapi.io/mcp).
Is the Healthie MCP by usefulapi server safe to use?
Healthie 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 Healthie MCP by usefulapi server expose?
Healthie MCP by usefulapi exposes 16 tools: healthie_current_user, healthie_get_organization, healthie_list_patients, healthie_get_user, healthie_list_appointments, and 11 more. Their descriptions and schemas cost roughly 1,431 tokens of context every time the server is loaded.
Does the Healthie MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Healthie 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 Healthie MCP by usefulapi server still maintained?
Healthie MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.