io.usefulapi/healthie
REMOTE · HEALTHIE.USEFULAPI.IO · SCANNED SEP 20
Hosted MCP server for the Healthie EHR & telehealth API: patients, appointments, charting, tasks.
Available components
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 answered with HTTP 401, which proves neither a plaintext path nor enforcement. 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1431 tokens (~89/item across 16 items; 16 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 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
How do I install the io.usefulapi/healthie MCP server?
io.usefulapi/healthie 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'
{
"mcpServers": {
"io-usefulapi-healthie": {
"url": "https://healthie.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-healthie": {
"type": "http",
"url": "https://healthie.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-healthie] url = "https://healthie.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-healthie": {
"type": "remote",
"url": "https://healthie.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-healthie --url 'https://healthie.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-healthie:
url: "https://healthie.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-healthie": {
"Transport": "http",
"Url": "https://healthie.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-healthie -t streamable-http -u 'https://healthie.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-healthie": {
"type": "http",
"url": "https://healthie.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Sept 26 +68
- Transport: unverified → pass ▲ security
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 14 Sept 26 −55
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 13 Sept 26 −10
- Authorization: fail → unverified ▼ security
- Stability: pass → fail ▼ security
- 12 Sept 26 −4
- Authorization: pass → fail ▼ security
- 11 Sept 26 +1
No change was recorded against any check on this day. Endpoint Security went from 78 to 80.
- 10 Sept 26 −1
No change was recorded against any check on this day. Endpoint Security went from 80 to 78.
- 9 Sept 26 +56
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: fail → pass ▲ security
- Schema quality: unverified → fail ▼ functional
- Schema quality: unverified → excellent ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → pass ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 8 Sept 26 −56
- Authorization: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: pass → fail ▼ security
- Schema quality: excellent → unverified ▼ functional
- Schema quality: fail → unverified ▼ functional
- Schema quality: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day 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 20 Sept 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 | 14 Sept 2026 | 13 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 33c1f4335b8f9e02133d5d3a7ad73407 |
| SANs: usefulapi.io, healthie.usefulapi.io, *.healthie.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 | 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 | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://healthie.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://healthie.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://healthie.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://healthie.usefulapi.io/mcp |
| Authorisation server | https://healthie.usefulapi.io |
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 | Verified | 200 | |
| http (plaintext) | http://healthie.usefulapi.io/mcp | Inconclusive | 401 |
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.
What is the io.usefulapi/healthie MCP server?
io.usefulapi/healthie is an MCP server 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 io.usefulapi/healthie MCP server safe to use?
io.usefulapi/healthie scores 86 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 io.usefulapi/healthie MCP server expose?
io.usefulapi/healthie 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 io.usefulapi/healthie MCP server require authentication?
Yes. io.usefulapi/healthie 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 io.usefulapi/healthie MCP server still maintained?
io.usefulapi/healthie is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.