MCP Safety Board · server report · November 2026
Taxuspt/garmin_mcp
A
90 / 100
Grade A · ★ 1,502 · Python checked by hand
How the score was worked out
| Check | What was found | Points |
|---|---|---|
| Risky tools labelled | All 19 tools that look like they delete, write or run things declare destructiveHint or readOnlyHint. | 0 |
| Tools with any label | 157 of 157 tools (100%) carry any annotation; half or more. | 0 |
| README install command | The README tells users to launch the server with npx / bunx / uvx / pnpm dlx without a pinned version (or with @latest). | −10 |
| Committed config | No committed MCP config with an unpinned package, a moving tag, a broad filesystem root, a privileged docker server or plain http. | 0 |
| Score | 100 minus the penalties above (never below 0). | 90 |
Changes that would raise this grade
- +10Pin the version in the README install command (pkg@1.2.3 or pkg==1.2.3, not @latest). Alone, this gives 100 (A).
What was checked
- Commit checked
a2ca5fcac345- Repository
- github.com/Taxuspt/garmin_mcp
- Tools found
- 157, of which 157 carry any label (100%)
- Risky tools
- 19, of which 19 labelled
- README install
- not pinned
- Last push
- 2026-10-24
Static reading of this one commit. No code was installed or run. This is a hygiene grade, not a security audit.
Maintainer?
Fixed something, or think a count is wrong? Request a re-check (opens a GitHub issue). Re-checks run on the latest commit.
README badge
[](https://mcp-safety-board.pages.dev/s/taxuspt--garmin_mcp.html)Want a written review of your agent's tools and permissions?
48-hour written review. Which tools your agent can call, what each one can change, which need a confirmation step, and what to lock down first. Send a message to start.