Run Coach
NPM · GARMIN-MCP-APP
Garmin data with interactive charts: daily briefing, training trends, workout planning. Unofficial.
Available components
Last scanned (42 minutes 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 2 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 Management73
- Stability observed for 22 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 5 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 →
get-running-tolerance Get Running Tolerance ~55
Running load tolerance over a date range
| Name | Type | Req | Description |
|---|---|---|---|
| aggregation | string | – | – |
| 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-sleep Get Sleep ~122
Get sleep data (stages, score, HRV, breathing) 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-spo2 Get Pulse Ox ~36
Blood oxygen saturation (SpO2) readings for a date
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Date in YYYY-MM-DD format |
No output schema declared.
No examples provided.
get-steps Get Steps ~59
Get step count data from Garmin Connect. Supports a single date or a date range.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Start date in YYYY-MM-DD format |
| endDate | string | – | End date in YYYY-MM-DD format (defaults to date) |
No output schema declared.
No examples provided.
get-stress Get Stress ~120
Get stress data (average, max, intraday levels) 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-training-context Get Training Context ~64
Collects comprehensive training context for workout planning: recent running activities, sleep, HRV, training readiness, body battery, VO2 max, and training status. Use this before planning a workout.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Reference date (YYYY-MM-DD), typically today |
No output schema declared.
No examples provided.
get-training-plans Get Training Plans ~16
Available and active training plans
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get-training-readiness Get Training Readiness ~49
Get training readiness score (0-100) and breakdown (sleep, HRV, recovery, stress) for a given date
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Date in YYYY-MM-DD format |
No output schema declared.
No examples provided.
get-training-status Get Training Status ~42
Get training status including acute/chronic load, ACWR, and load status for a given date
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Date in YYYY-MM-DD format |
No output schema declared.
No examples provided.
get-user-settings Get User Settings ~33
User settings: units, sleep schedule, physiological data (age, weight, height, HR zones, lactate threshold)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get-vo2-max Get VO2 Max ~52
Get VO2 Max trend data 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-weekly-intensity-minutes Get Weekly Intensity Minutes ~53
Weekly intensity minutes vs goal over 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-weekly-steps Get Weekly Steps ~51
Weekly step totals for the weeks ending at a date
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date in YYYY-MM-DD format |
| weeks | integer | – | Number of weeks (default 12) |
No output schema declared.
No examples provided.
get-weekly-stress Get Weekly Stress ~51
Weekly average stress for the weeks ending at a date
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date in YYYY-MM-DD format |
| weeks | integer | – | Number of weeks (default 12) |
No output schema declared.
No examples provided.
get-weigh-ins Get Weigh-ins ~48
All weigh-ins over 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-workout Get Workout ~52
Get a saved workout's steps (warm-up, intervals, targets) by ID. To find a workout by name, call list-workouts first.
| Name | Type | Req | Description |
|---|---|---|---|
| workoutId | string|number | yes | Garmin workout ID |
No output schema declared.
No examples provided.
list-workouts List Workouts ~103
List the user's saved/custom workouts (structured workouts they created, e.g. 'LT', 'Tempo 5K', '4x1km'). Use this whenever the user refers to a workout by name, then get-workout for its steps.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 20) |
| name | string | – | Only workouts whose name contains this text (case-insensitive) |
| start | number | – | Start index (default 0) |
No output schema declared.
No examples provided.
schedule-workout Schedule Workout ~50
Schedule a workout on a specific calendar date in Garmin Connect
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Date to schedule the workout (YYYY-MM-DD) |
| workoutId | string|number | yes | Garmin workout ID |
No output schema declared.
No examples provided.
show-performance-dashboard Performance Dashboard ~436
Show how key health and fitness metrics trend over 4 weeks to 1 year, one small chart per metric on a shared time range. Use it for trends, progress and comparing metrics over time: "is my fitness improving?", "how has my HRV changed?", "why did my resting HR go up in March?" (pick a range/endDate that covers the period). Metrics (max 4): restingHR, hrv (nightly avg, with Garmin's baseline band), vo2max, sleepScore, sleepDuration (h), steps (per day), stress (avg), bodyBattery (daily high), intensityMinutes (weekly, vigorous counted double), trainingLoad (acute load with Garmin's optimal range), weight (kg, only if the user weighs in). Points are daily for 4w/12w and weekly means for 26w/52w. Each metric has a summary: end = current level (mean of the last 7 days, or the latest week), mean = the period's average, vsMean/vsMeanPct = current level vs that average (the headline comparison; % omitted when the average is near zero), min/max with dates, start = the first 7 days/week (often unrepresentative, e.g. a new watch still calibrating or load ramping up from zero, so don't quote start→end percentages), and trend (direction of a least-squares fit; "flat" = fitted change under 3% of the mean). The chart only shows the data: interpret it for the user — what changed, how the metrics relate (e.g. HRV vs resting HR vs training load vs sleep), and gaps in the data. Don't over-read small changes.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | – | Last day shown, YYYY-MM-DD (default today) |
| metrics | array | – | Metrics to show (max 4), default restingHR, hrv, vo2max, sleepScore |
| range | string | – | Time range ending at endDate: 4, 12, 26 or 52 weeks (default 12w) |
No output schema declared.
No examples provided.
show-run-replay Show Run Replay ~119
Open an interactive 3D replay of a run: a runner follows the GPS track over the terrain while pace, heart rate (zones), cadence, elevation/grade, power, running dynamics and weather play back over time, with pause, fast-forward and scrubbing. Use when the user wants to replay, relive, watch or review a run as a whole. Returns a short summary of the run; the view renders the time series.
| Name | Type | Req | Description |
|---|---|---|---|
| activityId | string|number | – | Garmin activity ID (default: the most recent run) |
No output schema declared.
No examples provided.
show-training-week Training Week ~106
Show a Monday-Sunday training week: workouts scheduled on the Garmin calendar (with their steps and estimated duration/distance), activities completed, and a weekly summary (planned vs done, planned and completed volume). Call it after creating/scheduling a week of workouts to show the user the plan, or to review how a week went.
| Name | Type | Req | Description |
|---|---|---|---|
| startDate | string | – | Any day of the week to show (YYYY-MM-DD); the week starts on its Monday. Default: this week. |
No output schema declared.
No examples provided.
unschedule-workout Unschedule Workout ~100
Remove one scheduled workout from the Garmin calendar; the workout itself and its other dates are kept. scheduleId is the calendar entry's ID, not the workout's: workoutScheduleId from schedule-workout or create-structured-workout, or scheduleId from show-training-week. To move a workout to another day, unschedule it, then schedule-workout on the new date.
| Name | Type | Req | Description |
|---|---|---|---|
| scheduleId | string|number | yes | Calendar schedule entry ID |
No output schema declared.
No examples provided.
update-workout Update Workout ~44
Update an existing workout on Garmin Connect
| Name | Type | Req | Description |
|---|---|---|---|
| workout | object | yes | Workout object following Garmin workout JSON structure |
| workoutId | string|number | yes | Garmin workout ID |
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 5 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 5 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.