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.
npx agentmods add mcp/davidmosiah/fitbit-mcp/fitbitmcpgit clone --depth 1 https://github.com/davidmosiah/fitbit-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/davidmosiah/fitbit-mcp/fitbitmcp)<a href="https://agentmods.dev/mcp/davidmosiah/fitbit-mcp/fitbitmcp"><img src="https://agentmods.dev/badge/mcp/davidmosiah/fitbit-mcp/fitbitmcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
fitbitmcp 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 6d 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
{
"fitbitmcp": {
"command": "npx",
"args": [
"-y",
"fitbit-mcp-unofficial"
],
"env": {
"FITBIT_CLIENT_ID": "",
"FITBIT_CLIENT_SECRET": "",
"FITBIT_REDIRECT_URI": "",
"FITBIT_TOKEN_PATH": "",
"FITBIT_PRIVACY_MODE": "",
"FITBIT_CACHE": "",
"FITBIT_CACHE_PATH": "",
"FITBIT_NO_CACHE": ""
}
}
}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.
- 6d ago First seen · 19 lines scan A 219091b09f28
fitbitmcp is an MCP server published in the GitHub repository davidmosiah/fitbit-mcp (4 stars, last pushed 8d 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-31.
Other mcp servers, from other repositories
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.
apple-health-mcp
Unofficial local-first MCP server for Apple Health export data. Runs locally from the apple-health-mcp-unofficial npm package. Needs 4 environment variables to run.
withings
MCP server for Withings health data — sleep, activity, heart, and body metrics. Remote server at withings-mcp.com.
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.
mcp-server-whoop
Local-first, read-only WHOOP MCP server for recovery, sleep, strain, workouts, and body signals. Runs locally from the mcp-server-whoop npm package.
whoopmcp
MCP server "whoopmcp" as configured in kurok/whoopmcp. Runs locally from the whoopmcp Python package. Needs 3 environment variables to run.