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/LePomas/garminconnect-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/lepomas/garminconnect-mcp/garmin)<a href="https://agentmods.dev/mcp/lepomas/garminconnect-mcp/garmin"><img src="https://agentmods.dev/badge/mcp/lepomas/garminconnect-mcp/garmin.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
garmin 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 7d 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
{
"garmin": {
"type": "stdio",
"command": "/path/to/garminconnect-mcp/.venv/bin/garminconnect-mcp",
"args": []
}
}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.
- 7d ago First seen · 7 lines scan A cde396a5ec42
garmin is an MCP server published in the GitHub repository LePomas/garminconnect-mcp (0 stars, last pushed 2mo 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
garmin-local-mcp
Local-first Garmin data warehouse with an analysis-grade MCP server. Sync once, analyze forever - even when the API is down. Runs locally from the garmin-local-mcp Python package. Needs 1 environment variable to run.
hybridlog
MCP server "hybridlog" as configured in Imgrund/hybridlog. Runs in Docker (ghcr.io/imgrund/hybridlog:0.1.9). Needs 2 environment variables to run.
paceforge
MCP server "paceforge" as configured in yashhooda1/paceforge. Runs locally from the paceforge Python package.
garmin-mcp
MCP server exposing Garmin Connect data to Claude. Runs locally from the garmin-mcp Python package.
garmin-readonly-mcp
MCP server "garmin-readonly-mcp" as configured in alexpomsft/garmin-readonly-mcp. Runs locally from the garmin-readonly-mcp Python package.
intervals-icu
MCP server "intervals-icu" as configured in staffanbergvall/intervals-mcp. Runs locally from the python Python package.