MetricBridge Apple Health vs HC Sync: Health Connect data
MetricBridge Apple Health is an MCP server published by PhilipAD. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). HC Sync: Health Connect data is an MCP server published by shaharfrish6. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  MetricBridge Apple Health | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.10.2 Downloads/month (npm): 2 493 Downloads/week (npm): 1 266 Forks (GitHub): 0 Stars (GitHub): 11 Not marked · First seen |
Listed Version: 0.3.0 No figure published Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 1.10.2 Downloads/month (npm): 2 493 Downloads/week (npm): 1 266 Forks (GitHub): 0 Stars (GitHub): 11 Not marked · First seen |
Not listed |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | MetricBridge Apple Health | HC Sync: Health Connect data |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 11 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | 2026-11-03 | Not published |
| Where it runs (differs) | On your machine (health-export-mcp) | Remote server (hcsync.dev/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 2 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/philipad/health-export-mcp | Not stated |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-11-08 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
MetricBridge Apple Health
Ask your agent about your own Apple Health data: 194 metrics, 22 tools, local, 0 deps.
HC Sync: Health Connect data
Read Android Health Connect users, daily summaries and records synced to your backend.
How to run each
MetricBridge Apple Health As a local MCP server: npm package
claude mcp add --env "HEALTH_EXPORT_PASSPHRASE=<YOUR_HEALTH_EXPORT_PASSPHRASE>" --env "PAIRING_SECRET=<YOUR_PAIRING_SECRET>" --transport stdio health-export-mcp -- npx -y health-export-mcpRequires: HEALTH_EXPORT_PASSPHRASE (secret), PAIRING_SECRET (secret)
HC Sync: Health Connect data As a remote MCP server
claude mcp add --transport http hc-sync https://hcsync.dev/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only HC Sync: Health Connect data has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of HC Sync: Health Connect data publish no settings it asks for, so we do not compare settings.
What it can do: MetricBridge Apple Health · What it can do: HC Sync: Health Connect data · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.