Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/akutishevsky/withings-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/akutishevsky/withings-mcp/withings)<a href="https://agentmods.dev/mcp/akutishevsky/withings-mcp/withings"><img src="https://agentmods.dev/badge/mcp/akutishevsky/withings-mcp/withings/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/akutishevsky/withings-mcp/withings"><img src="https://agentmods.dev/badge/mcp/akutishevsky/withings-mcp/withings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
withings scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"withings": {
"url": "https://withings-mcp.com/mcp",
"type": "streamable-http"
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 6 lines scan A 12cdf1cf3ca8
withings is an MCP server published in the GitHub repository akutishevsky/withings-mcp (42 stars, last pushed 3d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
whoopmcp
MCP server "whoopmcp" as configured in kurok/whoopmcp. Runs locally from the whoopmcp Python package. Needs 3 environment variables to run.
hevy-mcp
MCP server for managing workouts, routines, and exercise data through the Hevy API. Runs locally from the hevy-mcp npm package. Needs 1 environment variable to run.
hevy
MCP server "hevy", hosted remotely at mcp.hevy-mcp.dev, as configured in chrisdoc/hevy-mcp.
withingsmcp
Privacy-first, unofficial Withings MCP server for AI health, sleep, activity and heart-rate agents. Runs locally from the withings-mcp-unofficial npm package. Needs 8 environment variables to run.
ouramcp
Privacy-first, unofficial Oura MCP server for AI health, sleep, activity and heart-rate agents. Runs locally from the oura-mcp-unofficial npm package. Needs 8 environment variables to run.
fitbitmcp
Privacy-first, unofficial Fitbit MCP server for AI health, sleep, activity and heart-rate agents. Runs locally from the fitbit-mcp-unofficial npm package. Needs 8 environment variables to run.