A
licenseNot graded
qualityD
maintenanceEnables fetching health and fitness metrics from the Ultrahuman API, including heart rate, sleep, steps, temperature, and HRV data.
15
22
MIT
vital
by io.usefulapi
Server Details
Read wearables and lab health data — sleep, activity, workouts, timeseries, lab tests and orders.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A3.7/5.0
Tool DescriptionsA
Average 3.8/5 across 21 of 21 tools scored. Lowest: 3/5.
Server CoherenceA
Disambiguation5/5
Each tool targets a distinct resource and action: user creation/lookup, connection tokens, summaries for different health domains, lab test/order queries, and timeseries. No two tools appear to serve the same purpose, and the parameters (e.g. data ranges vs. IDs) further differentiate them.
Naming Consistency4/5
All tools use the 'vital_' prefix and snake_case with a verb_noun pattern. Verbs are limited to create/get/list/resolve, and the use of 'get' for both single resources and summary endpoints is consistent enough. Slight deviation: some collection-returning operations use 'get' (e.g., get_workouts) while others use 'list' (e.g., list_orders), but the distinction between catalog listing and data retrieval is logical.
Tool Count4/5
21 tools is above the ideal 3-15 range but fits the breadth of Vital's health data API. The count is justified by the many distinct summary types, lab test management, and user/provider operations. While it feels a bit heavy, the tools are well-scoped and each serves a clear need.
Completeness4/5
The set covers user creation/lookup, connection linking, health data summaries for common domains (activity, body, sleep, meals, menstrual cycle, workouts), timeseries, and lab test/order fetching. Gaps include no tool to create or cancel lab test orders, update/delete users, or disconnect providers, but these may be out of scope for a read-oriented health data server.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseAqualityAmaintenanceProvides read-only access to Withings health metrics including body composition, sleep, workouts, and ECG data with local SQLite caching and trend analysis. Features incremental synchronization, automatic OAuth token refresh, and supports all 200+ Withings measurement types for comprehensive health tracking.8GPL 3.0
- AlicenseNot gradedqualityBmaintenanceRead-only MCP access to Fitbit-synced health data through Google Health API v4. Provides tools for metrics, summaries, trends, and data quality without write or arbitrary HTTP operations.MIT
- FlicenseNot gradedqualityCmaintenanceEnables users to query Polar health data (activity, sleep, recovery, training sessions, heart rate) through MCP with secure authentication, redacted personal info, and bounded responses.