Akute Health MCP by usefulapi
REMOTE · AKUTE-HEALTH.USEFULAPI.IO
Read Akute Health patients, appointments, tasks, notes, medications, allergies and observations.
Available components
Last scanned (16 minutes 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 1617 tokens (~107/item across 15 items; 15 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 Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 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
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
- Schema quality: pass → fail ▼ functional
- 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 59
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://akute-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 akute-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://akute-health.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://akute-health.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://akute-health.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://akute-health.usefulapi.io/mcp |
| Authorisation server | https://akute-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://akute-health.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/akute-health/ |
| http (plaintext) | http://akute-health.usefulapi.io/mcp | Inconclusive | 302 | http://akute-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 →
akutehealth_get_appointment Get appointment ~42
One appointment by id: times, status, patient, practitioner and appointment type. GET /appointments/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| appointment_id | string | yes | – |
No output schema declared.
No examples provided.
akutehealth_get_availability Get practitioner availability ~104
Open appointment slots of one practitioner between two date-times. GET /availability.
| Name | Type | Req | Description |
|---|---|---|---|
| end_time | string | yes | Window end, ISO 8601 with offset. |
| start_time | string | yes | Window start, ISO 8601 with offset, e.g. 2026-10-12T00:00:00-06:00. |
| user_id | string | yes | Practitioner (user) id from akutehealth_list_practitioners. |
No output schema declared.
No examples provided.
akutehealth_get_note Get clinical note ~45
One clinical note by id with all its sections (subjective, objective, assessment, plan ...). GET /notes/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| note_id | string | yes | – |
No output schema declared.
No examples provided.
akutehealth_get_patient Get patient ~45
One patient by id: demographics, address, status, provider, custom properties and membership billing state. GET /patients/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| patient_id | string | yes | – |
No output schema declared.
No examples provided.
akutehealth_get_practitioner Get practitioner ~39
One user by id: name, NPI and roles. GET /users/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | – |
No output schema declared.
No examples provided.
akutehealth_get_task Get task ~47
One task by id: title, description, due date, priority, status, tags, comments and activity. GET /tasks/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | – |
No output schema declared.
No examples provided.
akutehealth_list_allergies List patient allergies ~46
A patient's allergies and intolerances: substance, reaction, type, clinical status, onset date. GET /allergies.
| Name | Type | Req | Description |
|---|---|---|---|
| patient_id | string | yes | – |
No output schema declared.
No examples provided.
akutehealth_list_appointment_types List appointment types ~42
The practice's appointment types (beta in Akute): name, duration, video flag, who can book, practitioners. GET /appointment_types.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
akutehealth_list_appointments List appointments ~151
Appointments by patient and/or date range, practitioner and status. Give a patient_id, or both start_range and end_range (at most 31 days apart). At most 100 are returned; narrow the dates if truncated. Room links are not returned. GET /appointments.
| Name | Type | Req | Description |
|---|---|---|---|
| end_range | string | – | Latest start: a date (yyyy-mm-dd) or ISO date-time. |
| patient_id | string | – | – |
| practitioner_user_id | string | – | Practitioner (user) id from akutehealth_list_practitioners. |
| start_range | string | – | Earliest start: a date (yyyy-mm-dd) or ISO date-time. |
| status | string | – | – |
No output schema declared.
No examples provided.
akutehealth_list_medications List patient medications ~90
A patient's medications: name, strength, directions, quantity, refills, status, diagnoses and prescriber. Optional date window on the start date. At most 100 are returned. GET /medications.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | A date, yyyy-mm-dd. |
| patient_id | string | yes | – |
| start_date | string | – | A date, yyyy-mm-dd. |
No output schema declared.
No examples provided.
akutehealth_list_notes List clinical notes ~156
Clinical notes (encounters) of ONE patient, newest first as Akute returns them: type, service date, status, authors and section text. A patient_id is required and pages are capped at 10. 'entered-in-error' notes appear only when asked for. GET /notes.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records per page, 1-10 (default 10). |
| offset | integer | – | Number of records to skip, 0-500 (default 0). Pass the previous reply's next_offset. Narrow the filters instead of paging deeper. |
| patient_id | string | yes | – |
| service_date_start | string | – | Only notes from this day on. |
| status | string | – | – |
No output schema declared.
No examples provided.
akutehealth_list_observations List patient observations ~68
A patient's vital signs (default) or laboratory results: name, value, unit, date, LOINC code. At most 100 are returned. GET /observations.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Default vital-signs. |
| patient_id | string | yes | – |
No output schema declared.
No examples provided.
akutehealth_list_practitioners List practitioners ~57
The practice's users: id, name, NPI and roles (Practitioner, Prescriber, Staff, Admin ...). Date of birth, DEA number, email and licences are not returned. GET /users.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
akutehealth_list_tasks List tasks ~204
Tasks filtered by patient, status, owner, priority, tag, due date or archive state; at least one filter except archived is required. Pages are capped at 25. GET /tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | – |
| due_date_end_range | string | – | A date, yyyy-mm-dd. |
| due_date_start_range | string | – | A date, yyyy-mm-dd. |
| limit | integer | – | Records per page, 1-25 (default 25). |
| offset | integer | – | Number of records to skip, 0-500 (default 0). Pass the previous reply's next_offset. Narrow the filters instead of paging deeper. |
| owner_id | string | – | User id of the task owner. |
| patient_id | string | – | – |
| priority | string | – | For example p1. |
| status | array | – | Statuses, e.g. not-started, in-progress. |
| tags | array | – | – |
No output schema declared.
No examples provided.
akutehealth_search_patients Search patients ~271
Search patients by name, email, phone (with phone_type), date of birth or external id, optionally narrowed by sex and status. At least one identifying filter is required (no bulk listing); pages are capped at 25 and paging stops at offset 500. Returns demographics, address, status, provider and membership billing state. Government and insurance identifiers are never returned. GET /patients.
| Name | Type | Req | Description |
|---|---|---|---|
| date_of_birth | string | – | A date, yyyy-mm-dd. |
| string | – | – | |
| external_id | string | – | Your own id for the patient. |
| first_name | string | – | – |
| last_name | string | – | – |
| limit | integer | – | Records per page, 1-25 (default 25). |
| offset | integer | – | Number of records to skip, 0-500 (default 0). Pass the previous reply's next_offset. Narrow the filters instead of paging deeper. |
| phone | string | – | Primary phone number, digits only. Needs phone_type. |
| phone_type | string | – | Type of the phone number: mobile, home or work. Required with phone (Akute ignores the number without it). |
| sex | string | – | For example female or male. |
| status | string | – | Patient status, for example active. |
No output schema declared.
No examples provided.
How do I install the Akute Health MCP by usefulapi server?
Akute Health MCP by usefulapi is a hosted endpoint at https://akute-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 · akute-health.usefulapi.io
claude mcp add --transport http io-usefulapi-akute-health 'https://akute-health.usefulapi.io/mcp'
What is the Akute Health MCP by usefulapi server?
Akute Health MCP by usefulapi is listed in the public MCP registry as io.usefulapi/akute-health. Read Akute Health patients, appointments, tasks, notes, medications, allergies and observations. This page covers its hosted endpoint (https://akute-health.usefulapi.io/mcp).
Is the Akute Health MCP by usefulapi server safe to use?
Akute Health MCP by usefulapi scores 63 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 Akute Health MCP by usefulapi server expose?
Akute Health MCP by usefulapi exposes 15 tools: akutehealth_search_patients, akutehealth_get_patient, akutehealth_list_appointments, akutehealth_get_appointment, akutehealth_list_appointment_types, and 10 more. Their descriptions and schemas cost roughly 1,407 tokens of context every time the server is loaded.
Does the Akute Health MCP by usefulapi server require authentication?
Yes. Akute 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 Akute Health MCP by usefulapi server still maintained?
Akute 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.