Run Coach
NPM · GARMIN-MCP-APP
Garmin data with interactive charts: daily briefing, training trends, workout planning. Unofficial.
Available components
Last scanned (23 hours ago)
Scores higher than 93% of npm servers
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to chenhunghan/garmin-mcp-app). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 4877 tokens (~65/item across 74 items; 73 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete-workout" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 74 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Schema quality: 4367 → 4877 ▼ functional
- Package version: 0.9.1 → 0.11.0 functional
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/garmin-mcp-app@0.11.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | chenhunghan/garmin-mcp-app |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/chenhunghan/garmin-mcp-app/.github/workflows/release-please.yml@refs/heads/main |
| Rekor log index | 3642658206 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:5030dbf55c226b2684cb5ac19960f40651f7bbc67a728df7074ef867dd8d1024d10c05a3afaf527294ad367748f142f46cdf8dbb18d09134580ff6228 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create-structured-workout Create Structured Workout ~405
Create a workout on Garmin Connect from a simple step list, and optionally put it on the calendar (scheduleDate). Use this instead of create-workout. The app shows the new workout's steps. Example: 5x1km intervals on a Tuesday { "name": "5x1km @ 4:00", "sport": "running", "scheduleDate": "2026-10-06", "steps": [ { "type": "warmup", "duration": { "seconds": 900 }, "target": { "hrZone": 2 } }, { "repeat": 5, "steps": [ { "type": "run", "duration": { "meters": 1000 }, "target": { "pace": { "fast": "3:55", "slow": "4:05" } } }, { "type": "recovery", "duration": { "seconds": 90 } } ] }, { "type": "cooldown", "duration": { "seconds": 600 }, "target": { "hrZone": 1 } } ] } An easy run is a single { "type": "run", "duration": { "seconds": 2700 }, "target": { "hrZone": 2 } } step. Base targets on the user's own zones and recent paces (get-training-context).
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional workout description |
| name | string | yes | Workout name, e.g. "Easy 45 min" or "5x1km @ 4:00" |
| scheduleDate | string | – | Optional YYYY-MM-DD: also put the workout on the user's Garmin calendar that day |
| sport | string | yes | Sport |
| steps | array | yes | Steps in order. A step is { type, duration?, target? }; a repeat is { repeat: n, steps: [...] }. |
No output schema declared.
No examples provided.
create-workout Create Workout ~316
Create a workout from raw Garmin workout JSON. Prefer create-structured-workout, which builds this JSON from a simple step list and avoids format mistakes; use this only for something it can't express. Workout structure: - sportType: { sportTypeId: 1, sportTypeKey: 'running' } for running - workoutSegments: array of segments, each with segmentOrder and workoutSteps - Each step uses type "ExecutableStepDTO" for regular steps, "RepeatGroupDTO" for repeat groups - Common step structure: { stepOrder, stepType, endCondition, endConditionValue, targetType, targetValueLow, targetValueHigh } Step types: warmup, cooldown, interval, rest, recovery, repeat End conditions: time (seconds), distance (meters), lap.button (manual lap) Target types: heart.rate.zone (1-5), pace.zone, speed.zone, no.target Example - 5x1000m intervals: - Warmup: 15min easy (endCondition: time, endConditionValue: 900) - Repeat group (numberOfIterations: 5): - Interval: 1000m (endCondition: distance, endConditionValue: 1000) - Recovery: 90s jog (endCondition: time, endConditionValue: 90) - Cooldown: 10min easy (endCondition: time, endConditionValue: 600)
| Name | Type | Req | Description |
|---|---|---|---|
| workout | object | yes | Workout object following Garmin workout JSON structure |
No output schema declared.
No examples provided.
delete-workout Delete Workout ~55
Delete a workout from Garmin Connect, with every calendar entry it has. To take one scheduled workout off the calendar and keep the workout, use unschedule-workout.
| Name | Type | Req | Description |
|---|---|---|---|
| workoutId | string|number | yes | Garmin workout ID |
No output schema declared.
No examples provided.
garmin-check-auth Check Garmin Auth ~20
Check if the user is authenticated with Garmin Connect
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
garmin-get-login-key Get Garmin Login Key ~24
Issue a single-use public key for encrypting the Garmin password
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
garmin-get-replay-asset Get Replay Asset ~68
One file of the 3D replay's asset pack (scanned materials, sky light, models, running motion; CC0), base64-encoded. Served from a local cache, downloaded once from the app's GitHub release.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | – |
No output schema declared.
No examples provided.
garmin-get-run-map Get Run Map ~71
Real elevation and OpenStreetMap features (roads, land cover, water, buildings) around an activity's GPS track, for the 3D replay. Only when the real map setting is on.
| Name | Type | Req | Description |
|---|---|---|---|
| activityId | string|number | – | Garmin activity ID (default: the most recent run) |
No output schema declared.
No examples provided.
garmin-get-run-replay Get Run Replay Data ~76
Time series of an activity for the 3D replay view (GPS, elevation, HR, cadence, speed, power, running dynamics), plus laps, weather and HR zones
| Name | Type | Req | Description |
|---|---|---|---|
| activityId | string|number | – | Garmin activity ID (default: the most recent run) |
| maxPoints | integer | – | – |
No output schema declared.
No examples provided.
garmin-login Garmin Login ~47
Log in to Garmin Connect with email and an encrypted password
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – | |
| encryptedPassword | string | yes | Password encrypted with the key from garmin-get-login-key |
No output schema declared.
No examples provided.
garmin-logout Garmin Logout ~20
Log out of Garmin Connect and clear saved tokens
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
garmin-run-map-settings Run Replay Map Settings ~50
Read or change whether the run replay fetches real elevation (AWS Terrain Tiles) and map data (OpenStreetMap) for the area around a run
| Name | Type | Req | Description |
|---|---|---|---|
| realMap | boolean | – | – |
No output schema declared.
No examples provided.
garmin-submit-mfa Submit Garmin MFA ~27
Submit MFA verification code for Garmin Connect login
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
No output schema declared.
No examples provided.
get-activities Get Activities ~42
Get recent activities from Garmin Connect
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 20) |
| start | number | – | Start index (default 0) |
No output schema declared.
No examples provided.
get-activities-by-date Get Activities by Date ~88
Activities between two dates, optionally filtered by type (e.g. running, cycling)
| Name | Type | Req | Description |
|---|---|---|---|
| activityType | string | – | Activity type key, e.g. running |
| endDate | string | – | End date in YYYY-MM-DD format |
| limit | integer | – | – |
| start | integer | – | – |
| startDate | string | yes | Start date in YYYY-MM-DD format |
No output schema declared.
No examples provided.
get-activity-chart-data Get Activity Chart Data ~57
Time series (HR, pace, cadence, elevation...) of an activity, downsampled
| Name | Type | Req | Description |
|---|---|---|---|
| activityId | string|number | yes | Garmin activity ID |
| maxPoints | integer | – | Max samples (default 200) |
No output schema declared.
No examples provided.
get-activity-details Get Activity Details ~34
Get full details for a specific Garmin activity by ID
| Name | Type | Req | Description |
|---|---|---|---|
| activityId | string|number | yes | Garmin activity ID |
No output schema declared.
No examples provided.
get-activity-exercise-sets Get Activity Exercise Sets ~37
Strength-training sets, reps and weights of an activity
| Name | Type | Req | Description |
|---|---|---|---|
| activityId | string|number | yes | Garmin activity ID |
No output schema declared.
No examples provided.
get-activity-gear Get Activity Gear ~36
Gear (e.g. shoes) used for an activity
| Name | Type | Req | Description |
|---|---|---|---|
| activityId | string|number | yes | Garmin activity ID |
No output schema declared.
No examples provided.
get-activity-hr-zones Get Activity HR Zones ~39
Get heart rate time-in-zones breakdown for a specific activity
| Name | Type | Req | Description |
|---|---|---|---|
| activityId | string|number | yes | Garmin activity ID |
No output schema declared.
No examples provided.
get-activity-splits Get Activity Splits ~80
Get splits (pace, HR, cadence) for a specific activity. Returns the laps recorded by the watch (lapDTOs); when the activity was recorded as a single lap (auto-lap off), also per-km splits computed from the time series (kmSplits).
| Name | Type | Req | Description |
|---|---|---|---|
| activityId | string|number | yes | Garmin activity ID |
No output schema declared.
No examples provided.
get-activity-typed-splits Get Activity Typed Splits ~35
Run/walk/rest splits of an activity
| Name | Type | Req | Description |
|---|---|---|---|
| activityId | string|number | yes | Garmin activity ID |
No output schema declared.
No examples provided.
get-activity-types Get Activity Types ~16
All Garmin activity type keys
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get-activity-weather Get Activity Weather ~28
Weather during an activity
| Name | Type | Req | Description |
|---|---|---|---|
| activityId | string|number | yes | Garmin activity ID |
No output schema declared.
No examples provided.
get-body-battery Get Body Battery ~53
Get daily body battery charged/drained values for a date range
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date in YYYY-MM-DD format |
| startDate | string | yes | Start date in YYYY-MM-DD format |
No output schema declared.
No examples provided.
get-body-battery-events Get Body Battery Events ~42
Events that charged or drained body battery (sleep, activities, stress) for a date
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Date in YYYY-MM-DD format |
No output schema declared.
No examples provided.
get-body-composition Get Body Composition ~36
Weight, BMI, body fat and muscle mass for a date
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Date in YYYY-MM-DD format |
No output schema declared.
No examples provided.
get-calendar Get Calendar ~40
Calendar for a month: scheduled workouts, activities and events
| Name | Type | Req | Description |
|---|---|---|---|
| month | integer | yes | Month, 1-12 |
| year | integer | yes | – |
No output schema declared.
No examples provided.
get-cycling-ftp Get Cycling FTP ~20
Latest cycling functional threshold power (FTP)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get-daily-briefing Daily Briefing ~275
Morning briefing: how the user is today, framed against their own baselines. Use for 'how am I today', 'morning briefing', 'daily check-in', 'should I train today', 'am I recovered'. Returns training readiness (with its limiting factors), last night's sleep (score, duration vs Garmin's optimal, stages), HRV (vs 7-night avg and the balanced range), body battery (vs at wake), resting HR (vs 7-day avg), stress, steps vs goal, training status, the last activity and the past 7 days' volume. Each metric has value, unit, a named baseline, delta and a neutral status (from Garmin's own status fields where it has one); missing metrics carry a reason. After calling it: give a short, warm briefing that leads with the 1–2 numbers that matter most today, then 2–3 concrete, personal suggestions grounded in the numbers (e.g. intensity or duration of today's session, bedtime, recovery), and one thing to watch. Say what you're unsure about (missing metrics, a single bad night vs a trend). Don't restate every number: the app already shows them.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Day to brief on (YYYY-MM-DD), defaults to today in the user's time zone |
No output schema declared.
No examples provided.
get-daily-summary Get Daily Summary ~45
Daily totals: steps, calories, distance, floors, intensity minutes, stress and body battery for a date
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Date in YYYY-MM-DD format |
No output schema declared.
No examples provided.
get-devices Get Devices ~13
Registered Garmin devices
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get-endurance-score Get Endurance Score ~64
Endurance score for a date, or weekly stats when endDate is given (a single date often has no data)
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | – | End date in YYYY-MM-DD format |
| startDate | string | yes | Start date in YYYY-MM-DD format |
No output schema declared.
No examples provided.
get-fitness-age Get Fitness Age ~33
Fitness age vs chronological age and what drives it
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Date in YYYY-MM-DD format |
No output schema declared.
No examples provided.
get-floors Get Floors ~34
Floors climbed and descended through the day for a date
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Date in YYYY-MM-DD format |
No output schema declared.
No examples provided.
get-gear Get Gear ~20
All gear (shoes, bikes) with usage
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get-goals Get Goals ~20
Goals by status
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | – |
No output schema declared.
No examples provided.
get-heart-rate-zones Get Heart Rate Zones ~19
Configured heart rate zones per sport
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get-heart-rates Get Heart Rates ~124
Get heart rate data (resting, min/max, intraday samples) for a day, or for each day from date to endDate in one call. The chart shows the days ending at the last requested date.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Date in YYYY-MM-DD format (the first day when endDate is given) |
| endDate | string | – | Optional last day (YYYY-MM-DD, max 14 days) to get every day in the range in ONE call. Prefer this over calling the tool once per day: each call shows its own chart. |
No output schema declared.
No examples provided.
get-hill-score Get Hill Score ~62
Hill score (strength + endurance on climbs) for a date, or weekly stats when endDate is given
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | – | End date in YYYY-MM-DD format |
| startDate | string | yes | Start date in YYYY-MM-DD format |
No output schema declared.
No examples provided.
get-hrv Get HRV ~62
Get heart rate variability data (nightly avg, weekly avg, baseline, status) for a date range
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date in YYYY-MM-DD format |
| startDate | string | yes | Start date in YYYY-MM-DD format |
No output schema declared.
No examples provided.
get-hydration Get Hydration ~34
Water intake vs goal and sweat loss for a date
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Date in YYYY-MM-DD format |
No output schema declared.
No examples provided.
get-intensity-minutes Get Intensity Minutes ~41
Moderate/vigorous intensity minutes for a date and the running weekly total vs goal
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Date in YYYY-MM-DD format |
No output schema declared.
No examples provided.
get-lactate-threshold Get Lactate Threshold ~50
The user's latest lactate threshold measurement (heart rate and pace), a physiological metric detected by the watch. Not a saved workout: for workouts named like 'LT' use list-workouts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get-last-used-device Get Last Used Device ~15
Most recently synced device
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get-personal-records Get Personal Records ~31
Personal records (fastest 1K/5K/10K, longest run, etc.)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get-primary-training-device Get Primary Training Device ~21
Device used as the source of training status and metrics
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get-progress-summary Get Progress Summary ~59
Totals per activity type over a date range for a metric
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date in YYYY-MM-DD format |
| metric | string | – | – |
| startDate | string | yes | Start date in YYYY-MM-DD format |
No output schema declared.
No examples provided.
get-race-predictions Get Race Predictions ~31
Get predicted race times for 5K, 10K, half marathon, and marathon
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get-respiration Get Respiration ~41
Breathing rate (breaths/min) through the day and during sleep for a date
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Date in YYYY-MM-DD format |
No output schema declared.
No examples provided.
get-resting-heart-rate Get Resting Heart Rate ~50
Daily resting heart rate over a date range
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | – | End date in YYYY-MM-DD format |
| startDate | string | yes | Start date in YYYY-MM-DD format |
No output schema declared.
No examples provided.
How do I install the Run Coach MCP server?
Run Coach runs locally as an npm package, launched with npx -y garmin-mcp-app. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · garmin-mcp-app
claude mcp add chenhunghan-garmin-mcp-app -- npx -y garmin-mcp-app
What is the Run Coach MCP server?
Run Coach is an MCP server listed in the public MCP registry as io.github.chenhunghan/garmin-mcp-app. Garmin data with interactive charts: daily briefing, training trends, workout planning. Unofficial. This page covers its npm package (garmin-mcp-app).
Is the Run Coach MCP server safe to use?
Run Coach scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Run Coach MCP server expose?
Run Coach exposes 73 tools: garmin-check-auth, garmin-get-login-key, garmin-login, garmin-submit-mfa, garmin-logout, and 68 more. Their descriptions and schemas cost roughly 4,867 tokens of context every time the server is loaded.
Is the Run Coach MCP server still maintained?
Run Coach is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Run Coach MCP server under?
Run Coach declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.