Loading the registry…
Local-first Garmin data warehouse with an analysis-grade MCP server. Sync once, analyze forever - even when the API is down.
The publisher performed an authenticated act of publication — proving control of a namespace in the official MCP registry, or appearing in a first-party catalogue an operator curates. That establishes WHO published it. It is not a security finding, and attested artifacts carry Flagged verdicts too.
1 critical finding reported by agent-audit-kit. The composite score alone does not reflect this — read the per-scanner reports below.
This artifact ships from 3 sources and their verdicts differ. The worst is github (Flagged). Installing from a cleaner source does not mean the others are safe — check the source you actually install from.
github: https://github.com/anup-shesh/garmin-local-mcp, 11 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- garmin-local-mcp
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
5 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v2.0.11
3 findings · 7.7s
v0.3.74
8 findings · 2.4s
v0.1.0
0 findings · 3.1s
v0.1.0
0 findings · 3.1s
v0.1.0
0 findings · 11.9s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image.
3 scans on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Sep 1, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source: complete | rejected |
| Aug 8, 2026 | Flagged94 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicabletrivy: completeosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
| Aug 3, 2026 | Flagged90 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completenerlo-multi-source: completetrivy ·n/a: not applicableosv-scanner ·n/a: not applicabletrivy_image ·n/a: not applicable | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 11 findings across every scanner that examined this package. None of the 1 finding rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 4 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
Two keys had to turn. The model had to name a reason from a fixed list of six, and a deterministic check of ours — over which files this artifact actually installs — had to independently agree. Anything it could not corroborate is in “not reviewed” above, at full severity.
2 CI or editor configuration — The match is in build, CI or editor configuration, confirmed by our own check to be outside the installed artifact.
Rules: AAK-GHA-IMMUTABLE-001 · Files: .github/workflows/publish.yml, .github/workflows/ci.yml · reported by agent-audit-kit
The model could have called any of these a false positive and did not.
1 AAK-DNS-REBIND-002
Files: pyproject.toml · reported by agent-audit-kit
1 AAK-MCP-ENV-PLACEHOLDER-EXFIL-001
Files: src/garmin_mcp/config.py · reported by agent-audit-kit
1 AAK-MCP-SDK-CVE-2026-52869-001
Files: pyproject.toml · reported by agent-audit-kit
1 AAK-OAUTH-3P-001
Files: pyproject.toml · reported by agent-audit-kit
1 AAK-SECRET-004
Files: src/garmin_mcp/login.py · reported by agent-audit-kit
4 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-SEC-MD-001, HIDDEN_DATA_FILE, SOCIAL_ENG_VAGUE_DESCRIPTION and 1 more · Files: SECURITY.md, /repo/.mcpbignore, /repo/SKILL.md · reported by agent-audit-kit, cisco-skill-scanner
Critical risk of environment variable exfiltration and credential exposure.
This artifact includes code that could exfiltrate environment variable values from `src/garmin_mcp/config.py`. It also contains a hardcoded secret in `src/garmin_mcp/login.py`, which could lead to credential exposure. Additionally, the artifact uses a vulnerable SDK version in `pyproject.toml` and exhibits potential DNS rebinding behavior in `pyproject.toml`.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.