io.github.rwestergren/inbody-api-mcp vs io.github.souravpn/whoop-mcp
io.github.rwestergren/inbody-api-mcp is an MCP server published by rwestergren. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.souravpn/whoop-mcp is an MCP server published by souravpn. Marketplaces we read that list it: 1 (Official MCP Registry). 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.1.0 Downloads/month (PyPI): 608 Downloads/week (PyPI): 146 Forks (GitHub): 2 Stars (GitHub): 15 Not marked · First seen |
Listed Version: 1.0.2 Downloads/month (npm): 144 Downloads/week (npm): 43 Forks (GitHub): 0 Stars (GitHub): 0 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.rwestergren/inbody-api-mcp | io.github.souravpn/whoop-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 15 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 2 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (inbody-api-mcp) | On your machine (@souravpn/whoop-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 1 | 2, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/rwestergren/inbody-api-mcp | github.com/souravpn/whoop-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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.rwestergren/inbody-api-mcp
MCP server for InBody body-composition data — scans, body fat, muscle mass, body water
io.github.souravpn/whoop-mcp
MCP server for WHOOP — gives Claude access to your recovery, sleep, strain, and workout data
How to run each
io.github.rwestergren/inbody-api-mcp As a local MCP server: PyPI package
claude mcp add --env "INBODY_LOGIN_ID=<YOUR_INBODY_LOGIN_ID>" --env "INBODY_LOGIN_PW=<YOUR_INBODY_LOGIN_PW>" --transport stdio inbody-api-mcp -- uvx inbody-api-mcp
Requires: INBODY_LOGIN_ID, INBODY_LOGIN_PW (secret)
io.github.souravpn/whoop-mcp As a local MCP server: npm package
claude mcp add --env "WHOOP_CLIENT_ID=<YOUR_WHOOP_CLIENT_ID>" --env "WHOOP_CLIENT_SECRET=<YOUR_WHOOP_CLIENT_SECRET>" --transport stdio whoop-mcp -- npx -y @souravpn/whoop-mcp
Requires: WHOOP_CLIENT_ID, WHOOP_CLIENT_SECRET (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only io.github.rwestergren/inbody-api-mcp asks for
INBODY_COUNTRY_CODEINBODY_LOGIN_IDINBODY_LOGIN_PW (secret)
Only io.github.souravpn/whoop-mcp asks for
WHOOP_CLIENT_IDWHOOP_CLIENT_SECRET (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.rwestergren/inbody-api-mcp · What it can do: io.github.souravpn/whoop-mcp · 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.