ghurt Made the Official MCP Registry With Garmin, Oura and Whoop
The Official MCP Registry now has a health server in it. It covers Garmin, Oura and Whoop. Apple Health, the dataset sitting on roughly a billion iPhones, is not on the surface. That gap is the whole story of this post.
Quick answer
ghurt is listed on the Official MCP Registry (v1.0.0, first seen 2026-10-11) and its health surface covers Garmin, Oura and Whoop only. Apple Health is absent (evidence E6 and E7 in our weekly market pack, read 2026-10-18). For a buyer, that means the registry listing is not a shortcut to your phone's health data. If you have an iPhone and no wearable, a registry-listed health server still does not read your data.
What the Official MCP Registry is
The registry is the canonical index of published MCP servers. It gives a server a discoverable identity, a listing with metadata, and a first-seen date that directories can track. For an agent ecosystem that is genuinely useful, because it turns a scattered pile of GitHub repos into something a client can look up.
What the registry is not is a coverage promise. It records what a server says it supports, not what you need it to support. The registry answers "does this server exist and resolve". It does not answer "does it read my health data". Those are different questions and the gap between them is where buyers get lost.
Why the Apple Health gap is structural
Wearables are easy to serve from the cloud. Garmin, Oura and Whoop all ship first-party cloud APIs, so a hosted server can authenticate once and pull your data over the network with a documented token. Apple Health is the opposite shape. It lives on the device, behind HealthKit permissions, with no public cloud endpoint that reads it for you. Serving it means either an on-device app that exports, or a file the app produced.
That is why the registry's health entries cluster around wearable clouds and stay empty at Apple Health. It is not a slight to Apple. It is a transport difference, and the transport is the thing that decides which servers can exist.
The three transports, and who they serve
| Transport | Reads Apple Health? | Notes |
|---|---|---|
| Wearable cloud API | No | Great for Garmin, Oura, Whoop; your iPhone's data is not on this path |
| Hosted health connector | Sometimes | Serves your data from a vendor copy; plan-gated and metered |
| Local file MCP server | Yes | Reads the export your own app produced, on your own machine |
If your goal is "my agent can answer questions about my Apple Health data", only the bottom two rows reach it at all, and only the bottom row keeps the data on your machine with no account and no quota.
How we sourced this. ghurt's registry listing, platform coverage and first-seen date are from the registry and the Ext Ops Panel listing (E6, E7), read on 2026-10-18. Listings change, so check the registry for the current surface before you rely on a name.
How to read a registry listing properly
A registry listing is a starting point, not a verdict. Four things to check before you install anything from it:
- Which platforms does it actually name? A health server that lists three wearable brands is a wearable server. If Apple Health is not named, it is not read.
- Where does the data come from? A cloud API, a vendor-held copy, or your own file. This decides your privacy and quota story.
- When was it first seen? A first-seen date tells you how new the listing is, which matters for a server you are about to run with your health data.
- Does the install line resolve? A listing with an unset placeholder can still score zero on a trust scanner. See our pre-install check.
The gap is an opportunity, not a scandal
The empty Apple Health slot is the most interesting fact in this week's sweep. It means the fastest-growing registry in the agent ecosystem has room at exactly the dataset most iPhone owners care about, and the servers that could fill it are the ones that solve the local export problem rather than the wearable-cloud problem.
That is the path MetricBridge ships. An app that exports 190 Apple Health metrics as local JSON, and a zero-dependency stdio MCP server that reads that export and exposes 16 read-only tools. No cloud API, no vendor copy, no quota.
{
"mcpServers": {
"health-export": {
"command": "node",
"args": ["/Users/you/.health-export-mcp/server.mjs"],
"env": {
"HEALTH_DATA_DIR": "/Users/you/Library/Mobile Documents/iCloud~ai~healthexport~app/Documents"
}
}
}
}Ask the agent to call get_mcp_status and it confirms the server is up and the data was found. That is the Apple Health slot filled, on your own machine.
FAQ
Is there an Apple Health server on the Official MCP Registry?
As of the 2026-10-18 sweep, the registry's health listing we examined, ghurt, covers Garmin, Oura and Whoop only and does not include Apple Health. The registry records what a server says it supports, so check each listing's named platforms.
Why do health MCP servers cover wearables but not Apple Health?
Wearables ship first-party cloud APIs that a hosted server can pull over the network. Apple Health lives on the device behind HealthKit permissions with no equivalent cloud endpoint, so serving it needs an on-device export and a local server instead.
Does a registry listing mean a server is trustworthy?
No. The registry confirms a server exists and resolves. It does not vouch for behaviour or coverage. Trust scanners such as VerifyMCP grade the install line separately, and you should still check the platform list, the data path and the source.
How do I read my Apple Health data with an agent if no registry server covers it?
Use a local file MCP server. Export your Apple Health data to JSON with an on-device app, then point a zero-dependency stdio server at that export. MetricBridge ships both, and the server is open source.
Doing this yourself? MetricBridge handles the export step: all 190 metrics as local JSON, with the open-source MCP server (GitHub).
Filling the Apple Health slot, locally
MetricBridge is a $24.99 one-time unlock: 190 metrics exported as local JSON, the open-source MCP server that reads it, and the on-device Ask and Weekly Brief. Nothing on our servers.