Vital MCP by usefulapi
REMOTE · VITAL.USEFULAPI.IO
Read wearables and lab health data — sleep, activity, workouts, timeseries, lab tests and orders.
Available components
Last scanned (7 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- 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
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 Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 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.
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.
- 2 Nov 26 −62
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “check_which_lab_tests_you_offer” functional
- New prompt “check_which_wearables_a_user_has_connected” functional
- New prompt “create_a_user_and_a_link_token_for_a_wearable” functional
- New prompt “find_a_user_by_id_or_list_your_team_s_users” functional
- New prompt “read_wearable_timeseries_and_body_summaries” functional
- New prompt “review_sleep_activity_and_workouts_for_a_user” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 0
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 0
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 0
- Stability: 0.97 → pass security
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.0 → 1.21.3 functional
- 24 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.20.0 → 1.21.0 functional
- Server version: 1.19.0 → 1.20.0 functional
- Server version: 1.17.0 → 1.19.0 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 5 Nov 2026 · Probed https://vital.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 vital.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://vital.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/vital/ |
| http (plaintext) | http://vital.usefulapi.io/mcp | Inconclusive | 302 | http://vital.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 →
vital_create_link_token Create link token ~112
Creates a short-lived Link token to connect a user's wearable/provider (no health data is modified). Vital API: POST /v2/link/token.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The Vital user id to create the link token for (required). |
No output schema declared.
No examples provided.
vital_create_user Create user ~124
Creates a Vital user record (additive). Returns the Vital user_id. Vital API: POST /v2/user.
| Name | Type | Req | Description |
|---|---|---|---|
| client_user_id | string | yes | 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). |
No output schema declared.
No examples provided.
vital_get_activity Activity ~107
Get activity summaries for a user over a date range. Vital API: GET /v2/summary/activity/{user_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Start date yyyy-mm-dd (inclusive, required). |
| user_id | string | yes | The Vital user id (UUID). |
No output schema declared.
No examples provided.
vital_get_body Body ~107
Get body summaries for a user over a date range. Vital API: GET /v2/summary/body/{user_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Start date yyyy-mm-dd (inclusive, required). |
| user_id | string | yes | The Vital user id (UUID). |
No output schema declared.
No examples provided.
vital_get_lab_test Get lab test ~48
Get a single lab test by id. Vital API: GET /v3/lab_tests/{lab_test_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| lab_test_id | string | yes | The lab test id (UUID). |
No output schema declared.
No examples provided.
vital_get_meal Meal ~109
Get meal summaries for a user over a date range. Vital API: GET /v2/summary/meal/{user_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Start date yyyy-mm-dd (inclusive, required). |
| user_id | string | yes | The Vital user id (UUID). |
No output schema declared.
No examples provided.
vital_get_menstrual_cycle Menstrual cycle ~114
Get menstrual cycle summaries for a user over a date range. Vital API: GET /v2/summary/menstrual_cycle/{user_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Start date yyyy-mm-dd (inclusive, required). |
| user_id | string | yes | The Vital user id (UUID). |
No output schema declared.
No examples provided.
vital_get_order Get order ~43
Get a single lab-test order by id. Vital API: GET /v3/order/{order_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | The order id (UUID). |
No output schema declared.
No examples provided.
vital_get_order_results Get order results ~46
Get the lab-test results for an order. Vital API: GET /v3/order/{order_id}/result.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | The order id (UUID). |
No output schema declared.
No examples provided.
vital_get_profile Profile ~72
Get a user's profile summary (height, and other static attributes). Vital API: GET /v2/summary/profile/{user_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | – | Filter to a single provider slug (e.g. oura, fitbit). |
| user_id | string | yes | The Vital user id (UUID). |
No output schema declared.
No examples provided.
vital_get_sleep Sleep ~108
Get sleep summaries for a user over a date range. Vital API: GET /v2/summary/sleep/{user_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Start date yyyy-mm-dd (inclusive, required). |
| user_id | string | yes | The Vital user id (UUID). |
No output schema declared.
No examples provided.
vital_get_timeseries Get timeseries data ~186
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Timeseries resource to fetch. |
| start_date | string | yes | Start date yyyy-mm-dd (inclusive, required). |
| user_id | string | yes | The Vital user id (UUID). |
No output schema declared.
No examples provided.
vital_get_user Get user ~46
Get a single Vital user by their Vital user_id. Vital API: GET /v2/user/{user_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | The Vital user id (UUID). |
No output schema declared.
No examples provided.
vital_get_user_connected_providers Get user's connected providers ~53
List the wearables/data sources (providers) a user has connected. Vital API: GET /v2/user/providers/{user_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | The Vital user id (UUID). |
No output schema declared.
No examples provided.
vital_get_user_latest_info Get user's latest info ~51
Get the latest device/app info reported for a user. Vital API: GET /v2/user/{user_id}/info/latest.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | The Vital user id (UUID). |
No output schema declared.
No examples provided.
vital_get_workouts Workouts ~109
Get workouts summaries for a user over a date range. Vital API: GET /v2/summary/workouts/{user_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Start date yyyy-mm-dd (inclusive, required). |
| user_id | string | yes | The Vital user id (UUID). |
No output schema declared.
No examples provided.
vital_list_lab_tests List lab tests ~93
List the lab tests available/configured for your team. Vital API: GET /v3/lab_tests.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
vital_list_orders List orders ~120
List lab-test orders with filters, paginated. Vital API: GET /v3/orders.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
vital_list_providers List supported providers ~31
List all providers (wearables/data sources) Vital supports. Vital API: GET /v2/providers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vital_list_users List users ~49
List all Vital users in your team, paginated. Vital API: GET /v2/user.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max users to return. |
| offset | integer | – | Pagination offset. |
No output schema declared.
No examples provided.
vital_resolve_user Resolve user by client_user_id ~59
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| client_user_id | string | yes | Your own stable id for the user. |
No output schema declared.
No examples provided.
How do I install the Vital MCP by usefulapi server?
Vital MCP by usefulapi is a hosted endpoint at https://vital.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 · vital.usefulapi.io
claude mcp add --transport http io-usefulapi-vital 'https://vital.usefulapi.io/mcp'
What is the Vital MCP by usefulapi server?
Vital MCP by usefulapi is listed in the public MCP registry as io.usefulapi/vital. Read wearables and lab health data, sleep, activity, workouts, timeseries, lab tests and orders. This page covers its hosted endpoint (https://vital.usefulapi.io/mcp).
Is the Vital MCP by usefulapi server safe to use?
Vital MCP by usefulapi scores 18 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 Vital MCP by usefulapi server expose?
Vital MCP by usefulapi exposes 21 tools: vital_list_users, vital_get_user, vital_resolve_user, vital_get_user_connected_providers, vital_get_user_latest_info, and 16 more. Their descriptions and schemas cost roughly 1,787 tokens of context every time the server is loaded.
Does the Vital MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Vital MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Vital MCP by usefulapi server still maintained?
Vital MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.