io.usefulapi/vital

REMOTE · VITAL.USEFULAPI.IO · SCANNED AUG 3

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

Available components

−51 this week 18 18 Trust /100

Trust breakdown (6 categories)

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 →

Endpoint Security46

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. 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 returned HTTP 429. See how to fix → View diagnostics → Fail

Schema Quality & AI Usability0

Schema not yet verified: we couldn't read the endpoint's schema.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.Unverified

Capabilities0

Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

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

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · vital.usefulapi.io

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.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
    }
  }
}

# add to OpenClaw

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

# ~/.hermes/config.yaml

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

// mcp.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 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.

3 Aug 26 −55
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.20 → unverified ▼ security
- Transport: pass → fail ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
2 Aug 26 +55
- Authorization: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.20 ▲ functional
1 Aug 26 −54
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.13 → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 26 +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.
28 Jul 26 +1
- Stability: unverified → 0.03 ▲ functional
27 Jul 26 +57
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional

Show 5 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 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	17 Jul 2026	15 Oct 2026	ECDSA 256	ECDSA-SHA256	553efc875bf700720e76411f325a0854
SANs: usefulapi.io, vital.usefulapi.io, *.vital.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

DNSSEC insecure

Validation of vital.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 No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	429

Header	Value
x-frame-options	SAMEORIGIN
referrer-policy	same-origin

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://vital.usefulapi.io/mcp	HTTP error	429
http (plaintext)	http://vital.usefulapi.io/mcp	Inconclusive	429

MCP tools — 21 exposed · ~1,787 tokens

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.

Tool Tokens

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.

Input Output Examples

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.

Input Output Examples

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

Input Output Examples

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

Input Output Examples

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

Input Output Examples

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

Input Output Examples

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

Input Output Examples

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

Input Output Examples

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.

Input Output Examples

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

Input Output Examples

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

Input Output Examples

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

Input Output Examples

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

Input Output Examples

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

Input Output Examples

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.

Input Output Examples

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

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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 Output Examples

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.

Input Output Examples

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

Input Output Examples

Name	Type	Req	Description
client_user_id	string	yes	Your own stable id for the user.

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	12
27 Jul	69
28 Jul	70
29 Jul	71
30 Jul	69
31 Jul	72
1 Aug	18
2 Aug	73
3 Aug	18