health vs HealthAPI
health is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑30.
health is a plugin bundle for AI coding tools published by AI-Ready U.. No marketplace we read lists it any more. HealthAPI is an MCP server published by healthapi.app. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  HealthAPI | |
|---|---|---|
| Community marketplace fru-dev3/ai-ready-life | Removed on 2026-10-30 Version: 1.0.11 Forks (GitHub): 5 Stars (GitHub): 17 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.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 | healthno longer listed · | HealthAPI |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 17 | No figure on GitHub |
| Forks (GitHub) (differs) | 5 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (healthapi.app/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 31 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/fru-dev3/ai-ready-life | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-19 | 2026-10-21 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 22 h ago |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of health
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
SmartHealthConnect turns Claude into a patient-facing health copilot. Six auto-discoverable skills invoke themselves based on natural prompts: • care-completion — tracks…
-
google-health-mcp io.github.davidmosiah/google-health-mcp
Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents
-
Consent-gated tools that turn user health notes into non-diagnostic appointment-prep materials.
-
B.O.N.S.A.I. Health Intelligence API
Lifestyle medicine health intelligence via x402 micropayments. 637+ peer-reviewed references.
-
health-partner io.github.shrynshjn/health-partner
Manage your Health Partner account, log food, water, workouts, body using agent
-
Connect your health, fitness, nutrition, sleep, and wearable data to your AI assistant.
What each says it does
health
2 AI agents that manage your personal health — wellness tracking, lab review, medication monitoring, appointment management, and insurance/HSA oversight.
HealthAPI
Read-only Apple Health data synced from your iPhone: sleep, heart rate, HRV, workouts and trends.
How to run each
health
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
HealthAPI As a remote MCP server
claude mcp add --transport http healthapi https://healthapi.app/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only HealthAPI 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
Neither one's marketplaces publish the settings it asks for.
What it can do: health · What it can do: HealthAPI · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.