Garmin Givemydata MCP Server
garmin-givemydata
PyPI
v0.1.13
Published by nrvim — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
high Shell/command execution in server code (garmin_client/client.py)MTC-SRC-002
In the server's implementation (`garmin_client/client.py:152`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: self._xvfb_proc = subprocess.Popen( [ xvfb, display,
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server garmin_client/client.py
Tools 48
Each tool and what it can reach — statically extracted from the published source.
garmin_activitiesno sensitive capabilitygarmin_activity_detailno sensitive capabilitygarmin_activity_trackpointsno sensitive capabilitygarmin_activity_typesno sensitive capabilitygarmin_badgesno sensitive capabilitygarmin_blood_pressureno sensitive capabilitygarmin_body_batteryno sensitive capabilitygarmin_body_compositionno sensitive capabilitygarmin_caloriesno sensitive capabilitygarmin_challengesno sensitive capability
Show 38 more tools ↓
garmin_compareno sensitive capabilitygarmin_daily_eventsno sensitive capabilitygarmin_devicesno sensitive capabilitygarmin_endurance_scoreno sensitive capabilitygarmin_fitness_ageno sensitive capabilitygarmin_floorsno sensitive capabilitygarmin_gearno sensitive capabilitygarmin_goalsno sensitive capabilitygarmin_health_snapshotno sensitive capabilitygarmin_health_summaryno sensitive capabilitygarmin_heart_rateno sensitive capabilitygarmin_hill_scoreno sensitive capabilitygarmin_hr_zonesno sensitive capabilitygarmin_hrvno sensitive capabilitygarmin_hydrationno sensitive capabilitygarmin_intensity_minutesno sensitive capabilitygarmin_lactate_thresholdno sensitive capabilitygarmin_load_focusno sensitive capabilitygarmin_queryno sensitive capabilitygarmin_race_predictionsno sensitive capabilitygarmin_recordsno sensitive capabilitygarmin_recoveryno sensitive capabilitygarmin_respirationno sensitive capabilitygarmin_schemano sensitive capabilitygarmin_sleepno sensitive capabilitygarmin_spo2no sensitive capabilitygarmin_stepsno sensitive capabilitygarmin_stressno sensitive capabilitygarmin_syncno sensitive capabilitygarmin_todayno sensitive capabilitygarmin_training_loadno sensitive capabilitygarmin_training_statusno sensitive capabilitygarmin_trendsno sensitive capabilitygarmin_user_profileno sensitive capabilitygarmin_vo2maxno sensitive capabilitygarmin_week_summaryno sensitive capabilitygarmin_wellness_activityno sensitive capabilitygarmin_workoutsno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (48 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.1.13 latest |
A 93/100 | 1 | 1.9.0 | 2026-07-23 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan garmin-givemydata --online --registry pypiMore in Lifestyle & Local
Admissions data & match scores for law, medical, dental, MBA, pharmacy, vet, optometry schools
Live AI data for agents: model releases, regulations (EU AI Act), GenAI glossary, daily news.
Physician-reviewed medical opinions and prescriptions for AI agents.
Security scan results for the Atrium MCP server.
Security scan results for the Autotel Mcp Instrumentation MCP server.
Security scan results for the Avalanche Org MCP server.