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/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/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/davidmosiah/fitbit-mcp/fitbitmcp"><img src="https://agentmods.dev/badge/mcp/davidmosiah/fitbit-mcp/fitbitmcp.svg" alt="Reviewed on agentmods" width="80" 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 1mo 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.
- 1mo 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 today), 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
google-health-mcp
Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents. Runs locally from the google-health-mcp-unofficial npm package. Needs 8 environment variables to run.
whoop-mcp
Privacy-first, unofficial WHOOP MCP server for AI health, sleep, recovery, and performance agents. Runs locally from the whoop-mcp-unofficial npm package. Needs 8 environment variables to run.
cdc-health-mcp-server
Search and query CDC public health data — mortality, vaccinations, surveillance, behavioral risk. Runs locally from the @cyanheads/cdc-health-mcp-server npm package. Needs 2 environment variables to run.
polarmcp
Privacy-first unofficial Polar AccessLink v4 MCP server for AI health, sleep and training agents. Runs locally from the polar-mcp-unofficial npm package. Needs 8 environment variables to run.
google-health-fitbit-mcp
Privacy-first Google Health API MCP server for health, sleep, activity and HR agents. Runs locally from the google-health-fitbit-mcp npm package. Needs 8 environment variables to run.
google-health-mcp
MCP server for the Google Health API, with a local cache and trend analysis. Runs locally from the google-health-mcp Python package.