health4ai vs HC Sync: Health Connect data
health4ai is an MCP server published by jefflitt1. Marketplaces we read that list it: 1 (Official MCP Registry). 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-09. 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 |  health4ai | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Downloads/month (PyPI): 187 Downloads/week (PyPI): 19 Forks (GitHub): 5 Stars (GitHub): 7 Not marked · First seen |
Listed Version: 0.3.0 No figure published Not marked · First seen |
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 | health4ai | HC Sync: Health Connect data |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 7 | No figure on GitHub |
| Forks (GitHub) (differs) | 5 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (health4ai) | Remote server (hcsync.dev/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/jefflitt1/health4ai | 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 2 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
health4ai
Query your Apple Health data from your own Supabase/Postgres via local MCP.
HC Sync: Health Connect data
Read Android Health Connect users, daily summaries and records synced to your backend.
How to run each
health4ai As a local MCP server: PyPI package
claude mcp add --env "DATABASE_URL=<YOUR_DATABASE_URL>" --env "HEALTHKIT_USER_ID=<YOUR_HEALTHKIT_USER_ID>" --transport stdio health4ai -- uvx health4aiRequires: DATABASE_URL (secret), HEALTHKIT_USER_ID
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: health4ai · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.