# Akute Health MCP by usefulapi (remote · akute-health.usefulapi.io)

Read Akute Health patients, appointments, tasks, notes, medications, allergies and observations.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `akute-health.usefulapi.io`: 63/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-akute-health/akute-health.md), [page](https://verifymcp.io/servers/io-usefulapi-akute-health/akute-health)

## Channel facts

- Endpoint: `https://akute-health.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 60% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-akute-health 'https://akute-health.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-akute-health": {
      "url": "https://akute-health.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-akute-health": {
      "type": "http",
      "url": "https://akute-health.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-akute-health]
url = "https://akute-health.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-akute-health": {
      "type": "remote",
      "url": "https://akute-health.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-akute-health --url 'https://akute-health.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-akute-health:
    url: "https://akute-health.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-akute-health": {
      "Transport": "http",
      "Url": "https://akute-health.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-akute-health -t streamable-http -u 'https://akute-health.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-akute-health": {
      "type": "http",
      "url": "https://akute-health.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-16 (score 63, +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.

### 2026-10-14 (score 62, +3)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] 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

### 2026-10-13 (score 59, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 59)

First indexed and scored.

## MCP tools (15)

### `akutehealth_search_patients` (~271 tokens)

Search patients

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.

Input parameters:

- `date_of_birth` (string): A date, yyyy-mm-dd.
- `email` (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.

### `akutehealth_get_patient` (~45 tokens)

Get patient

One patient by id: demographics, address, status, provider, custom properties and membership billing state. GET /patients/{id}.

Input parameters:

- `patient_id` (string, required)

### `akutehealth_list_appointments` (~151 tokens)

List appointments

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.

Input parameters:

- `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)

### `akutehealth_get_appointment` (~42 tokens)

Get appointment

One appointment by id: times, status, patient, practitioner and appointment type. GET /appointments/{id}.

Input parameters:

- `appointment_id` (string, required)

### `akutehealth_list_appointment_types` (~42 tokens)

List appointment types

The practice's appointment types (beta in Akute): name, duration, video flag, who can book, practitioners. GET /appointment_types.

### `akutehealth_get_availability` (~104 tokens)

Get practitioner availability

Open appointment slots of one practitioner between two date-times. GET /availability.

Input parameters:

- `end_time` (string, required): Window end, ISO 8601 with offset.
- `start_time` (string, required): Window start, ISO 8601 with offset, e.g. 2026-10-12T00:00:00-06:00.
- `user_id` (string, required): Practitioner (user) id from akutehealth_list_practitioners.

### `akutehealth_list_tasks` (~204 tokens)

List tasks

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.

Input parameters:

- `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)

### `akutehealth_get_task` (~47 tokens)

Get task

One task by id: title, description, due date, priority, status, tags, comments and activity. GET /tasks/{id}.

Input parameters:

- `task_id` (string, required)

### `akutehealth_list_notes` (~156 tokens)

List clinical notes

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.

Input parameters:

- `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, required)
- `service_date_start` (string): Only notes from this day on.
- `status` (string)

### `akutehealth_get_note` (~45 tokens)

Get clinical note

One clinical note by id with all its sections (subjective, objective, assessment, plan ...). GET /notes/{id}.

Input parameters:

- `note_id` (string, required)

### `akutehealth_list_medications` (~90 tokens)

List patient medications

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.

Input parameters:

- `end_date` (string): A date, yyyy-mm-dd.
- `patient_id` (string, required)
- `start_date` (string): A date, yyyy-mm-dd.

### `akutehealth_list_allergies` (~46 tokens)

List patient allergies

A patient's allergies and intolerances: substance, reaction, type, clinical status, onset date. GET /allergies.

Input parameters:

- `patient_id` (string, required)

### `akutehealth_list_observations` (~68 tokens)

List patient observations

A patient's vital signs (default) or laboratory results: name, value, unit, date, LOINC code. At most 100 are returned. GET /observations.

Input parameters:

- `category` (string): Default vital-signs.
- `patient_id` (string, required)

### `akutehealth_list_practitioners` (~57 tokens)

List practitioners

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.

### `akutehealth_get_practitioner` (~39 tokens)

Get practitioner

One user by id: name, NPI and roles. GET /users/{id}.

Input parameters:

- `user_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-akute-health/akute-health#diagnostics

## Score history

- 2026-10-17: 63
- 2026-10-16: 63
- 2026-10-15: 62
- 2026-10-14: 62
- 2026-10-13: 59
- 2026-10-12: 59

## Common questions

### 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.

## Links

- Remote endpoint: https://akute-health.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/akute-health/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-akute-health/akute-health.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-akute-health/akute-health.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-akute-health/akute-health