Withings Health Data vs Prometheus MCP Server
Withings Health Data is an MCP server published by akutishevsky. Marketplaces we read that list it: 1 (Official MCP Registry). Prometheus MCP Server is an MCP server published by pab1it0. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-11-07. 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: 1.3.0 Forks (GitHub): 12 Stars (GitHub): 45 Not marked · First seen |
Listed Version: 1.6.2 Forks (GitHub): 106 Stars (GitHub): 522 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:3c3921301229 Forks (GitHub): 106 Stars (GitHub): 522 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 | Withings Health Data | Prometheus MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 45 (worse) | 522 (better) |
| Forks (GitHub) (differs) | 12 (worse) | 106 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (withings-mcp.com/mcp) | On your machine (ghcr.io/pab1it0/prometheus-mcp-server:1.6.2) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares (differs) | Not published | 6 |
| Environment variables it asks for (differs) | Not published | 14, secrets among them: 2 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/akutishevsky/withings-mcp | github.com/pab1it0/prometheus-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 40 h ago returned HTTP 401 | 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
Withings Health Data
MCP server for Withings health data — sleep, activity, heart, and body metrics.
Prometheus MCP Server
MCP server providing Prometheus metrics access and PromQL query execution for AI assistants
How to run each
Withings Health Data As a remote MCP server
claude mcp add --transport http withings https://withings-mcp.com/mcp
Prometheus MCP Server As a local MCP server: Docker image
claude mcp add --env "PROMETHEUS_PASSWORD=<YOUR_PROMETHEUS_PASSWORD>" --env "PROMETHEUS_TOKEN=<YOUR_PROMETHEUS_TOKEN>" --env "PROMETHEUS_URL=<YOUR_PROMETHEUS_URL>" --transport stdio prometheus-mcp-server -- docker run -i --rm -e PROMETHEUS_PASSWORD -e PROMETHEUS_TOKEN -e PROMETHEUS_URL ghcr.io/pab1it0/prometheus-mcp-server:1.6.2
Requires: PROMETHEUS_PASSWORD (secret), PROMETHEUS_TOKEN (secret), PROMETHEUS_URL
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Withings Health Data has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Withings Health Data publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Withings Health Data publish no settings it asks for, so we do not compare settings.
What it can do: Withings Health Data · What it can do: Prometheus MCP Server · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.