# Usefulapi Vital MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.usefulapi%2Fvital
Registry id: `mcp-registry/io.usefulapi/vital`
Status: auth-required (checked 2026-10-27T06:20:23.914Z)

## Verdict

Usefulapi Vital MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 64 ms median handshake and 0 outages in 90 days. Its agent-readiness grade is A (96/100) across 21 tools, costing an agent about 3,386 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 64 ms | 88% of MCP servers |
| p95 handshake latency | 283 ms | — |
| Checks in 30 days | 219 | — |
| Outages, 90 days | 0 | — |
| Median recovery | — | — |
| Agent-readiness score | 96/100 (A) | 82% of MCP servers |
| Tools | 21 | — |
| Tool-list size for an agent | ~3,386 tokens | 44% of MCP servers |
| Days observed | 28 | — |

## Install

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

Claude Code:

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

## Tools (21)

- `vital_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.
- `vital_create_user`: Creates a Vital user record (additive). Returns the Vital user_id. Vital API: POST /v2/user.
- `vital_get_activity`: Get activity summaries for a user over a date range. Vital API: GET /v2/summary/activity/{user_id}.
- `vital_get_body`: Get body summaries for a user over a date range. Vital API: GET /v2/summary/body/{user_id}.
- `vital_get_lab_test`: Get a single lab test by id. Vital API: GET /v3/lab_tests/{lab_test_id}.
- `vital_get_meal`: Get meal summaries for a user over a date range. Vital API: GET /v2/summary/meal/{user_id}.
- `vital_get_menstrual_cycle`: Get menstrual cycle summaries for a user over a date range. Vital API: GET /v2/summary/menstrual_cycle/{user_id}.
- `vital_get_order`: Get a single lab-test order by id. Vital API: GET /v3/order/{order_id}.
- `vital_get_order_results`: Get the lab-test results for an order. Vital API: GET /v3/order/{order_id}/result.
- `vital_get_profile`: Get a user's profile summary (height, and other static attributes). Vital API: GET /v2/summary/profile/{user_id}.
- `vital_get_sleep`: Get sleep summaries for a user over a date range. Vital API: GET /v2/summary/sleep/{user_id}.
- `vital_get_timeseries`: Get timeseries data points for a user and resource over a date range. Supported resources: heartrate, hrv, glucose, blood_pressure, blood_oxygen, steps, respira
- `vital_get_user`: Get a single Vital user by their Vital user_id. Vital API: GET /v2/user/{user_id}.
- `vital_get_user_connected_providers`: List the wearables/data sources (providers) a user has connected. Vital API: GET /v2/user/providers/{user_id}.
- `vital_get_user_latest_info`: Get the latest device/app info reported for a user. Vital API: GET /v2/user/{user_id}/info/latest.
- `vital_get_workouts`: Get workouts summaries for a user over a date range. Vital API: GET /v2/summary/workouts/{user_id}.
- `vital_list_lab_tests`: List the lab tests available/configured for your team. Vital API: GET /v3/lab_tests.
- `vital_list_orders`: List lab-test orders with filters, paginated. Vital API: GET /v3/orders.
- `vital_list_providers`: List all providers (wearables/data sources) Vital supports. Vital API: GET /v2/providers.
- `vital_list_users`: List all Vital users in your team, paginated. Vital API: GET /v2/user.
- `vital_resolve_user`: 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}.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.