Remote MCP · Endpoint
Vital MCP by usefulapi MCP server
No. Vital MCP by usefulapi answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://vital.usefulapi.io/mcp
The last check completed an MCP handshake.
- Registry name
- io.usefulapi/vital
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 405 ms
- Tools exposed
- 21 tools
- Uptime, last 30 days
- 70.6% from 17 checks
- Described by its publisher as
- Read wearables and lab health data — sleep, activity, workouts, timeseries, lab tests and orders.
- Website
- https://usefulapi.io/vital/
- Repository
- https://github.com/m190/usefulapi-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 405 ms |
| 2 days ago | Handshake completed | 251 ms |
| 4 days ago | Handshake completed | 428 ms |
| 5 days ago | Handshake completed | 197 ms |
| 7 days ago | Handshake completed | 304 ms |
| 8 days ago | Failed - the check failed for an unclassified reason | — |
| 9 days ago | Handshake completed | 334 ms |
| 12 days ago | Failed - the check failed for an unclassified reason | — |
| 13 days ago | Failed - the check failed for an unclassified reason | — |
| 15 days ago | Failed - the check failed for an unclassified reason | — |
| 17 days ago | Failed - the check failed for an unclassified reason | — |
| 18 days ago | Handshake completed | 189 ms |
| 19 days ago | Handshake completed | 263 ms |
| 20 days ago | Handshake completed | 185 ms |
| 21 days ago | Handshake completed | 218 ms |
| 21 days ago | Handshake completed | 209 ms |
| 23 days ago | Handshake completed | 163 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 12 responding of 17.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with Vital MCP by usefulapi and makes no claim about it beyond what these checks measured.