Vital MCP by usefulapi
io.usefulapi/vitalusefulapi.iostreamable-httpv1.40.4Scanned
Read wearables and lab health data — sleep, activity, workouts, timeseries, lab tests and orders.
21 tools: 2 can delete or cancel things and 19 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
2 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Vital MCP by usefulapi can do
The Vital MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 21 tools. It can delete or cancel things (2 tools: vital_create_user and vital_create_link_token). 19 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.40.4.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
21 tools
Deletes or cancels 2Claude Code: deny
vital_create_link_tokenCreates a short-lived Link token to connect a user's wearable/provider (no health data is modified).No findings
Why it is in this group
- The name "vital_create_link_token" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Creates a short-lived Link token to connect a user's wearable/provider (no health data is modified). Vital API: POST /v2/link/token.
Annotations the server declares
- title: Create link token
- destructiveHint: true
vital_create_userCreates a Vital user record (additive).No findings
Why it is in this group
- The name "vital_create_user" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Creates a Vital user record (additive). Returns the Vital user_id. Vital API: POST /v2/user.
Annotations the server declares
- title: Create user
- destructiveHint: true
Only reads 19Show 19 read-only tools
vital_get_activityGet activity summaries for a user over a date range.No findings
Why it is in this group
- The name "vital_get_activity" says "get": a word for reading.
Description, as the server wrote it Get activity summaries for a user over a date range. Vital API: GET /v2/summary/activity/{user_id}.
Annotations the server declares
- title: Activity
- readOnlyHint: true
vital_get_bodyGet body summaries for a user over a date range.No findings
Why it is in this group
- The name "vital_get_body" says "get": a word for reading.
Description, as the server wrote it Get body summaries for a user over a date range. Vital API: GET /v2/summary/body/{user_id}.
Annotations the server declares
- title: Body
- readOnlyHint: true
vital_get_lab_testGet a single lab test by id.No findings
Why it is in this group
- The name "vital_get_lab_test" says "get": a word for reading.
Description, as the server wrote it Get a single lab test by id. Vital API: GET /v3/lab_tests/{lab_test_id}.
Annotations the server declares
- title: Get lab test
- readOnlyHint: true
vital_get_mealGet meal summaries for a user over a date range.No findings
Why it is in this group
- The name "vital_get_meal" says "get": a word for reading.
Description, as the server wrote it Get meal summaries for a user over a date range. Vital API: GET /v2/summary/meal/{user_id}.
Annotations the server declares
- title: Meal
- readOnlyHint: true
vital_get_menstrual_cycleGet menstrual cycle summaries for a user over a date range.No findings
Why it is in this group
- The name "vital_get_menstrual_cycle" says "get": a word for reading.
Description, as the server wrote it Get menstrual cycle summaries for a user over a date range. Vital API: GET /v2/summary/menstrual_cycle/{user_id}.
Annotations the server declares
- title: Menstrual cycle
- readOnlyHint: true
vital_get_orderGet a single lab-test order by id.No findings
Why it is in this group
- The name "vital_get_order" says "get": a word for reading.
Description, as the server wrote it Get a single lab-test order by id. Vital API: GET /v3/order/{order_id}.
Annotations the server declares
- title: Get order
- readOnlyHint: true
vital_get_order_resultsGet the lab-test results for an order.No findings
Why it is in this group
- The name "vital_get_order_results" says "get": a word for reading.
Description, as the server wrote it Get the lab-test results for an order. Vital API: GET /v3/order/{order_id}/result.
Annotations the server declares
- title: Get order results
- readOnlyHint: true
vital_get_profileGet a user's profile summary (height, and other static attributes).No findings
Why it is in this group
- The name "vital_get_profile" says "get": a word for reading.
Description, as the server wrote it Get a user's profile summary (height, and other static attributes). Vital API: GET /v2/summary/profile/{user_id}.
Annotations the server declares
- title: Profile
- readOnlyHint: true
vital_get_sleepGet sleep summaries for a user over a date range.No findings
Why it is in this group
- The name "vital_get_sleep" says "get": a word for reading.
Description, as the server wrote it Get sleep summaries for a user over a date range. Vital API: GET /v2/summary/sleep/{user_id}.
Annotations the server declares
- title: Sleep
- readOnlyHint: true
vital_get_timeseriesGet timeseries data points for a user and resource over a date range.No findings
Why it is in this group
- The name "vital_get_timeseries" says "get": a word for reading.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Get timeseries data
- readOnlyHint: true
vital_get_userGet a single Vital user by their Vital user_id.No findings
Why it is in this group
- The name "vital_get_user" says "get": a word for reading.
Description, as the server wrote it Get a single Vital user by their Vital user_id. Vital API: GET /v2/user/{user_id}.
Annotations the server declares
- title: Get user
- readOnlyHint: true
vital_get_user_connected_providersList the wearables/data sources (providers) a user has connected.No findings
Why it is in this group
- The name "vital_get_user_connected_providers" says "get": a word for reading.
Description, as the server wrote it List the wearables/data sources (providers) a user has connected. Vital API: GET /v2/user/providers/{user_id}.
Annotations the server declares
- title: Get user's connected providers
- readOnlyHint: true
vital_get_user_latest_infoGet the latest device/app info reported for a user.No findings
Why it is in this group
- The name "vital_get_user_latest_info" says "get": a word for reading.
Description, as the server wrote it Get the latest device/app info reported for a user. Vital API: GET /v2/user/{user_id}/info/latest.
Annotations the server declares
- title: Get user's latest info
- readOnlyHint: true
vital_get_workoutsGet workouts summaries for a user over a date range.No findings
Why it is in this group
- The name "vital_get_workouts" says "get": a word for reading.
Description, as the server wrote it Get workouts summaries for a user over a date range. Vital API: GET /v2/summary/workouts/{user_id}.
Annotations the server declares
- title: Workouts
- readOnlyHint: true
vital_list_lab_testsList the lab tests available/configured for your team.No findings
Why it is in this group
- The name "vital_list_lab_tests" says "list": a word for reading.
Description, as the server wrote it List the lab tests available/configured for your team. Vital API: GET /v3/lab_tests.
Annotations the server declares
- title: List lab tests
- readOnlyHint: true
vital_list_ordersList lab-test orders with filters, paginated.No findings
Why it is in this group
- The name "vital_list_orders" says "list": a word for reading.
Description, as the server wrote it List lab-test orders with filters, paginated. Vital API: GET /v3/orders.
Annotations the server declares
- title: List orders
- readOnlyHint: true
vital_list_providersList all providers (wearables/data sources) Vital supports.No findings
Why it is in this group
- The name "vital_list_providers" says "list": a word for reading.
Description, as the server wrote it List all providers (wearables/data sources) Vital supports. Vital API: GET /v2/providers.
Annotations the server declares
- title: List supported providers
- readOnlyHint: true
vital_list_usersList all Vital users in your team, paginated.No findings
Why it is in this group
- The name "vital_list_users" says "list": a word for reading.
Description, as the server wrote it List all Vital users in your team, paginated. Vital API: GET /v2/user.
Annotations the server declares
- title: List users
- readOnlyHint: true
vital_resolve_userLook up a Vital user by your own client_user_id (the stable id you assigned).No findings
Why it is in this group
- The name "vital_resolve_user" says "resolve": a word for reading.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Resolve user by client_user_id
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://vital.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://vital.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://vital.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://vital.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.40.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http vital https://vital.usefulapi.io/mcpclaude mcp add --transport http vital https://vital.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__vital__vital_list_users",
"mcp__vital__vital_get_user",
"mcp__vital__vital_resolve_user",
"mcp__vital__vital_get_user_connected_providers",
"mcp__vital__vital_get_user_latest_info",
"mcp__vital__vital_list_providers",
"mcp__vital__vital_get_sleep",
"mcp__vital__vital_get_activity",
"mcp__vital__vital_get_workouts",
"mcp__vital__vital_get_body",
"mcp__vital__vital_get_meal",
"mcp__vital__vital_get_menstrual_cycle",
"mcp__vital__vital_get_profile",
"mcp__vital__vital_get_timeseries",
"mcp__vital__vital_list_lab_tests",
"mcp__vital__vital_get_lab_test",
"mcp__vital__vital_list_orders",
"mcp__vital__vital_get_order",
"mcp__vital__vital_get_order_results"
],
"ask": [],
"deny": [
"mcp__vital__vital_create_user",
"mcp__vital__vital_create_link_token"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as vital. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/vital/verify?hash=1194a90138a48c10de3254291219fa4ea929f49d7ddee418efb27a1f01b017d0" | jq -e '.changed == false'Pinned hash 1194a90138a4, from Oct 25, 2026, 23:20 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/vital/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/vital)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:19 UTC.
Vital MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Vital MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 21 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Vital MCP by usefulapi delete data?
- Yes. 2 tools can delete, cancel or revoke something: vital_create_user and vital_create_link_token.
Can the Vital MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Vital MCP by usefulapi have?
- 21 tools: 2 destructive, 19 read. vital_create_user, vital_create_link_token, vital_list_users, vital_get_user, vital_resolve_user, vital_get_user_connected_providers, vital_get_user_latest_info, vital_list_providers and 13 more.
Does the Vital MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Vital MCP by usefulapi send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Vital MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.