# io.usefulapi/vital (remote · vital.usefulapi.io)

Read wearables and lab health data — sleep, activity, workouts, timeseries, lab tests and orders.

- Trust score: 18/100 (low)
- Change this week: −51
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

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

## Channel facts

- Endpoint: `https://vital.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

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

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 429.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 4 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.

## Install

### Claude

```bash
claude mcp add --transport http io-usefulapi-vital https://vital.usefulapi.io/mcp
```

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-vital": {
      "type": "http",
      "url": "https://vital.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-08-03 (score 18, −55)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Authorization: pass → unverified
- [security regression] Stability: 0.20 → unverified
- [security regression] Transport: pass → fail
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: fail → unverified

### 2026-08-02 (score 73, +55)

- [security improvement] Authorization: unverified → pass
- [security improvement] Transport: fail → pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.20

### 2026-08-01 (score 18, −54)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.13 → unverified
- [security regression] Authorization: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-07-31 (score 72, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 69, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 70, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-07-27 (score 69, +57)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (21)

### `vital_list_users` (~49 tokens)

List users

List all Vital users in your team, paginated. Vital API: GET /v2/user.

Input parameters:

- `limit` (integer): Max users to return.
- `offset` (integer): Pagination offset.

### `vital_get_user` (~46 tokens)

Get user

Get a single Vital user by their Vital user_id. Vital API: GET /v2/user/{user_id}.

Input parameters:

- `user_id` (string, required): The Vital user id (UUID).

### `vital_resolve_user` (~59 tokens)

Resolve user by client_user_id

Look up a Vital user by your own client_user_id (the stable id you assigned). Vital API: GET /v2/user/resolve/{client_user_id}.

Input parameters:

- `client_user_id` (string, required): Your own stable id for the user.

### `vital_get_user_connected_providers` (~53 tokens)

Get user's connected providers

List the wearables/data sources (providers) a user has connected. Vital API: GET /v2/user/providers/{user_id}.

Input parameters:

- `user_id` (string, required): The Vital user id (UUID).

### `vital_get_user_latest_info` (~51 tokens)

Get user's latest info

Get the latest device/app info reported for a user. Vital API: GET /v2/user/{user_id}/info/latest.

Input parameters:

- `user_id` (string, required): The Vital user id (UUID).

### `vital_list_providers` (~31 tokens)

List supported providers

List all providers (wearables/data sources) Vital supports. Vital API: GET /v2/providers.

### `vital_get_sleep` (~108 tokens)

Sleep

Get sleep summaries for a user over a date range. Vital API: GET /v2/summary/sleep/{user_id}.

Input parameters:

- `end_date` (string): End date yyyy-mm-dd (inclusive). Defaults to today upstream.
- `provider` (string): Filter to a single provider slug (e.g. oura, fitbit).
- `start_date` (string, required): Start date yyyy-mm-dd (inclusive, required).
- `user_id` (string, required): The Vital user id (UUID).

### `vital_get_activity` (~107 tokens)

Activity

Get activity summaries for a user over a date range. Vital API: GET /v2/summary/activity/{user_id}.

Input parameters:

- `end_date` (string): End date yyyy-mm-dd (inclusive). Defaults to today upstream.
- `provider` (string): Filter to a single provider slug (e.g. oura, fitbit).
- `start_date` (string, required): Start date yyyy-mm-dd (inclusive, required).
- `user_id` (string, required): The Vital user id (UUID).

### `vital_get_workouts` (~109 tokens)

Workouts

Get workouts summaries for a user over a date range. Vital API: GET /v2/summary/workouts/{user_id}.

Input parameters:

- `end_date` (string): End date yyyy-mm-dd (inclusive). Defaults to today upstream.
- `provider` (string): Filter to a single provider slug (e.g. oura, fitbit).
- `start_date` (string, required): Start date yyyy-mm-dd (inclusive, required).
- `user_id` (string, required): The Vital user id (UUID).

### `vital_get_body` (~107 tokens)

Body

Get body summaries for a user over a date range. Vital API: GET /v2/summary/body/{user_id}.

Input parameters:

- `end_date` (string): End date yyyy-mm-dd (inclusive). Defaults to today upstream.
- `provider` (string): Filter to a single provider slug (e.g. oura, fitbit).
- `start_date` (string, required): Start date yyyy-mm-dd (inclusive, required).
- `user_id` (string, required): The Vital user id (UUID).

### `vital_get_meal` (~109 tokens)

Meal

Get meal summaries for a user over a date range. Vital API: GET /v2/summary/meal/{user_id}.

Input parameters:

- `end_date` (string): End date yyyy-mm-dd (inclusive). Defaults to today upstream.
- `provider` (string): Filter to a single provider slug (e.g. oura, fitbit).
- `start_date` (string, required): Start date yyyy-mm-dd (inclusive, required).
- `user_id` (string, required): The Vital user id (UUID).

### `vital_get_menstrual_cycle` (~114 tokens)

Menstrual cycle

Get menstrual cycle summaries for a user over a date range. Vital API: GET /v2/summary/menstrual_cycle/{user_id}.

Input parameters:

- `end_date` (string): End date yyyy-mm-dd (inclusive). Defaults to today upstream.
- `provider` (string): Filter to a single provider slug (e.g. oura, fitbit).
- `start_date` (string, required): Start date yyyy-mm-dd (inclusive, required).
- `user_id` (string, required): The Vital user id (UUID).

### `vital_get_profile` (~72 tokens)

Profile

Get a user's profile summary (height, and other static attributes). Vital API: GET /v2/summary/profile/{user_id}.

Input parameters:

- `provider` (string): Filter to a single provider slug (e.g. oura, fitbit).
- `user_id` (string, required): The Vital user id (UUID).

### `vital_get_timeseries` (~186 tokens)

Get timeseries data

Get timeseries data points for a user and resource over a date range. Supported resources: heartrate, hrv, glucose, blood_pressure, blood_oxygen, steps, respiratory_rate, body_weight, body_fat, distance, water, vo2_max, stress_level, mindfulness_minutes, calories_active, calories_basal, floors_climbed, caffeine, cholesterol. Vital API: GET /v2/timeseries/{user_id}/{resource}.

Input parameters:

- `end_date` (string): End date yyyy-mm-dd (inclusive). Defaults to today upstream.
- `provider` (string): Filter to a single provider slug (e.g. oura, fitbit).
- `resource` (string, required): Timeseries resource to fetch.
- `start_date` (string, required): Start date yyyy-mm-dd (inclusive, required).
- `user_id` (string, required): The Vital user id (UUID).

### `vital_list_lab_tests` (~93 tokens)

List lab tests

List the lab tests available/configured for your team. Vital API: GET /v3/lab_tests.

Input parameters:

- `lab_slug` (string): Filter by lab slug.
- `name` (string): Filter by lab test name.
- `order_direction` (string): Sort direction.
- `order_key` (string): Sort key.
- `status` (string): Filter by lab test status (e.g. active).

### `vital_get_lab_test` (~48 tokens)

Get lab test

Get a single lab test by id. Vital API: GET /v3/lab_tests/{lab_test_id}.

Input parameters:

- `lab_test_id` (string, required): The lab test id (UUID).

### `vital_list_orders` (~120 tokens)

List orders

List lab-test orders with filters, paginated. Vital API: GET /v3/orders.

Input parameters:

- `end_date` (string): Filter by created-at end (ISO datetime).
- `page` (integer): Page number (1-based).
- `search_input` (string): Free-text search.
- `size` (integer): Page size.
- `start_date` (string): Filter by created-at start (ISO datetime).
- `status` (string): Filter by order status.
- `user_id` (string): Filter to a single Vital user id (UUID).

### `vital_get_order` (~43 tokens)

Get order

Get a single lab-test order by id. Vital API: GET /v3/order/{order_id}.

Input parameters:

- `order_id` (string, required): The order id (UUID).

### `vital_get_order_results` (~46 tokens)

Get order results

Get the lab-test results for an order. Vital API: GET /v3/order/{order_id}/result.

Input parameters:

- `order_id` (string, required): The order id (UUID).

### `vital_create_user` (~124 tokens)

Create user

Creates a Vital user record (additive). Returns the Vital user_id. Vital API: POST /v2/user.

Input parameters:

- `client_user_id` (string, required): Your own stable id for the user (required).
- `fallback_birth_date` (string): Fallback birth date yyyy-mm-dd.
- `fallback_time_zone` (string): IANA time zone used if the provider doesn't report one.
- `ingestion_end` (string): Latest date to ingest data to (yyyy-mm-dd).
- `ingestion_start` (string): Earliest date to ingest data from (yyyy-mm-dd).

### `vital_create_link_token` (~112 tokens)

Create link token

Creates a short-lived Link token to connect a user's wearable/provider (no health data is modified). Vital API: POST /v2/link/token.

Input parameters:

- `filter_on_providers` (array): Restrict the connectable providers to this list of slugs.
- `provider` (string): Pre-select a single provider slug to connect.
- `redirect_url` (string): URL to redirect to after the connection flow.
- `user_id` (string, required): The Vital user id to create the link token for (required).

## Diagnostics

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

## Score history

- 2026-08-03: 18
- 2026-08-02: 73
- 2026-08-01: 18
- 2026-07-31: 72
- 2026-07-30: 69
- 2026-07-29: 71
- 2026-07-28: 70
- 2026-07-27: 69
- 2026-07-26: 12

## Links

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