io.github.Philongevity/phi-longevity-prism vs io.github.davidmosiah/garminmcp
io.github.Philongevity/phi-longevity-prism is an MCP server published by Philongevity. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). io.github.davidmosiah/garminmcp is an MCP server published by davidmosiah. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-14. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 0.7.3 Downloads/month (npm): 1 541 Downloads/week (npm): 853 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.5.3 Downloads/month (npm): 839 Downloads/week (npm): 230 Forks (GitHub): 8 Stars (GitHub): 13 Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 0.7.3 Downloads/month (npm): 1 541 Downloads/week (npm): 853 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.8.0 Downloads/month (npm): 839 Downloads/week (npm): 230 Forks (GitHub): 8 Stars (GitHub): 13 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 | io.github.Philongevity/phi-longevity-prism | io.github.davidmosiah/garminmcp |
|---|---|---|
| Marketplaces that list it | 2 | 2 |
| Stars (GitHub) (differs) | 0 (worse) | 13 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 8 (better) |
| Last release (differs) | 2026-11-11 (better) | 2026-11-06 (worse) |
| Where it runs (differs) | Remote server or your machine | On your machine (garmin-mcp-unofficial) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 6, secrets among them: 0 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/philongevity/phi-mcp-server | github.com/davidmosiah/garmin-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 4 h ago | no remote endpoint we check |
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
io.github.Philongevity/phi-longevity-prism
Every doctor, your complete record: connect your patient portals or upload records from any doctor.
io.github.davidmosiah/garminmcp
Privacy-first unofficial Garmin Connect MCP for AI health, sleep, activity & recovery agents.
How to run each
io.github.Philongevity/phi-longevity-prism As a remote MCP server
claude mcp add --transport http phi-longevity-prism https://philongevity.com/mcp
io.github.davidmosiah/garminmcp As a local MCP server: npm package
claude mcp add --transport stdio garminmcp -- npx -y garmin-mcp-unofficial
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.Philongevity/phi-longevity-prism has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of io.github.davidmosiah/garminmcp nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
The marketplaces of io.github.Philongevity/phi-longevity-prism publish no settings it asks for, so we do not compare settings.
What it can do: io.github.Philongevity/phi-longevity-prism · What it can do: io.github.davidmosiah/garminmcp · 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.