MCP servers › io.github.chenhunghan › garmin-mcp-app

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.chenhunghan/garmin-mcp-app

Garmin data with interactive charts: daily briefing, training trends, workout planning. Unofficial. — the publisher's description

8 of 9 record checks metRead-only · tools listed 2026-10-23Topic: science-health-and-education · AI-classifiedversion 0.9.1TypeScriptMITstandard input/output67 tools

Summary

io.github.chenhunghan/garmin-mcp-app is a local MCP server listed in the official MCP registry at version 0.9.1. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 67 tools, 1 resource and 3 prompts.

Record checks

8 of 9 record checks met

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
not met: Repository publishes a security policy (SECURITY.md)
met: Package names its licence with a standard (SPDX) identifier
met: The version the registry lists can be installed and is not withdrawn
met: npm package carries build provenance (attestation)
met: No known critical or high advisory in the package or its dependencies

#4,792 of 15,112 packages by monthly downloads, tied with 5 others
#2,075 of 22,952 repositories by GitHub stars, tied with 58 others

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: local package
Transport: standard input/output
Package: npm · listed version behind the latest release
License: MIT
Dependencies: no known high or critical advisories
Repository: public
Tools: 67
Described as changing data: 8 of 67 toolsAI-classified
Mainly works on: accounts and data in outside web servicesAI-classified
Topic: science-health-and-educationAI-classified
Last tested: 2026-10-23

Add to your client

Worth knowing before you connect it

8 tools are described as changing something (garmin-login, garmin-submit-mfa, garmin-logout, …): our AI model's reading of the descriptions, not something we tested. We did not call them.
The registry lists 0.9.1; 0.10.0 is newer (1 release).
Its package is signed and carries a build record naming its source.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-23

Mode

read-only (no tool calls)

Latest version

0.9.1, published 2026-10-15 (registry, as of the 2026-10-23 snapshot)

First listed version

2026-10-08 (earliest version still in the registry; older removed versions would be earlier)

Version history

2 versions listed, 2026-10-08 to 2026-10-15; 2 in the 90 days before the 2026-10-23 snapshot.

Most recent 2 versions

0.9.1 · 2026-10-15
0.9.0 · 2026-10-08

(versions still listed in the registry only)

Registry data

snapshot 2026-10-23

Package and repository

checked 2026-10-23

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.9.1 (published 2026-10-15).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

67tools

1resources

3prompts

What it mainly works on, as our AI model read its tool descriptions: accounts and data in outside web services.

8 of 67 tools are described as changing something (creating, editing, deleting, sending or running). For 1 the reading was uncertain, so no mark is shown.

garmin-check-authreads or searches
“Check if the user is authenticated with Garmin Connect”
Takes no inputs.
garmin-get-login-key
“Issue a single-use public key for encrypting the Garmin password”
Takes no inputs.
garmin-logindescribed as changing data
“Log in to Garmin Connect with email and an encrypted password”
2 inputs, 2 required
- emailstringrequired
- encryptedPasswordstringrequired“Password encrypted with the key from garmin-get-login-key”
garmin-submit-mfadescribed as changing data
“Submit MFA verification code for Garmin Connect login”
1 input, 1 required
- codestringrequired
garmin-logoutdescribed as changing data
“Log out of Garmin Connect and clear saved tokens”
Takes no inputs.
get-stepsreads or searches
“Get step count data from Garmin Connect.”
2 inputs, 1 required
- datestringrequired“Start date in YYYY-MM-DD format”
- endDatestring“End date in YYYY-MM-DD format (defaults to date)”
get-heart-ratesreads or searches
“Get heart rate data (resting, min/max, intraday samples) for a day, or for each day from date to endDate in one call.”
2 inputs, 1 required
- datestringrequired“Date in YYYY-MM-DD format (the first day when endDate is given)”
- endDatestring“Optional last day (YYYY-MM-DD, max 14 days) to get every day in the range in ONE call.”
get-sleepreads or searches
“Get sleep data (stages, score, HRV, breathing) for a day, or for each day from date to endDate in one call.”
2 inputs, 1 required
- datestringrequired“Date in YYYY-MM-DD format (the first day when endDate is given)”
- endDatestring“Optional last day (YYYY-MM-DD, max 14 days) to get every day in the range in ONE call.”
get-stressreads or searches
“Get stress data (average, max, intraday levels) for a day, or for each day from date to endDate in one call.”
2 inputs, 1 required
- datestringrequired“Date in YYYY-MM-DD format (the first day when endDate is given)”
- endDatestring“Optional last day (YYYY-MM-DD, max 14 days) to get every day in the range in ONE call.”
get-activitieson 1 other serverreads or searches
“Get recent activities from Garmin Connect”
2 inputs
- startnumber“Start index (default 0)”
- limitnumber“Max results (default 20)”
get-training-readinessreads or searches
“Get training readiness score (0-100) and breakdown (sleep, HRV, recovery, stress) for a given date”
1 input, 1 required
- datestringrequired“Date in YYYY-MM-DD format”
get-training-statusreads or searches
“Get training status including acute/chronic load, ACWR, and load status for a given date”
1 input, 1 required
- datestringrequired“Date in YYYY-MM-DD format”

Show 55 more tools

get-hrvreads or searches
“Get heart rate variability data (nightly avg, weekly avg, baseline, status) for a date range”
2 inputs, 2 required
- startDatestringrequired“Start date in YYYY-MM-DD format”
- endDatestringrequired“End date in YYYY-MM-DD format”
get-body-batteryreads or searches
“Get daily body battery charged/drained values for a date range”
2 inputs, 2 required
- startDatestringrequired“Start date in YYYY-MM-DD format”
- endDatestringrequired“End date in YYYY-MM-DD format”
get-activity-detailsreads or searches
“Get full details for a specific Garmin activity by ID”
1 input, 1 required
- activityIdstring or numberrequired“Garmin activity ID”
get-activity-splitsreads or searches
“Get splits (pace, HR, cadence) for a specific activity.”
1 input, 1 required
- activityIdstring or numberrequired“Garmin activity ID”
get-activity-hr-zonesreads or searches
“Get heart rate time-in-zones breakdown for a specific activity”
1 input, 1 required
- activityIdstring or numberrequired“Garmin activity ID”
get-vo2-maxreads or searches
“Get VO2 Max trend data for a date range”
2 inputs, 2 required
- startDatestringrequired“Start date in YYYY-MM-DD format”
- endDatestringrequired“End date in YYYY-MM-DD format”
get-race-predictionsreads or searches
“Get predicted race times for 5K, 10K, half marathon, and marathon”
Takes no inputs.
get-training-contextreads or searches
“Collects comprehensive training context for workout planning: recent running activities, sleep, HRV, training readiness, body battery, VO2 max, and training status.”
1 input, 1 required
- datestringrequired“Reference date (YYYY-MM-DD), typically today”
list-workoutsreads or searches
“List the user's saved/custom workouts (structured workouts they created, e.g.”
3 inputs
- namestring“Only workouts whose name contains this text (case-insensitive)”
- startnumber“Start index (default 0)”
- limitnumber“Max results (default 20)”
get-workoutreads or searches
“Get a saved workout's steps (warm-up, intervals, targets) by ID.”
1 input, 1 required
- workoutIdstring or numberrequired“Garmin workout ID”
create-workoutcreates or changes datadescribed as changing data
“Create a workout from raw Garmin workout JSON.”
1 input, 1 required
- workoutobjectrequired“Workout object following Garmin workout JSON structure”
create-structured-workoutcreates or changes datadescribed as changing data
“Create a workout on Garmin Connect from a simple step list, and optionally put it on the calendar (scheduleDate).”
5 inputs, 3 required
- namestringrequired“Workout name, e.g.”
- sportstringrequired“Sport”
- descriptionstring“Optional workout description”
- stepsarrayrequired“Steps in order.”
- scheduleDatestring“Optional YYYY-MM-DD: also put the workout on the user's Garmin calendar that day”
update-workoutcreates or changes datadescribed as changing data
“Update an existing workout on Garmin Connect”
2 inputs, 2 required
- workoutIdstring or numberrequired“Garmin workout ID”
- workoutobjectrequired“Workout object following Garmin workout JSON structure”
delete-workoutdeletesdescribed as changing data
“Delete a workout from Garmin Connect”
1 input, 1 required
- workoutIdstring or numberrequired“Garmin workout ID”
schedule-workoutcreates or changes datadescribed as changing data
“Schedule a workout on a specific calendar date in Garmin Connect”
2 inputs, 2 required
- workoutIdstring or numberrequired“Garmin workout ID”
- datestringrequired“Date to schedule the workout (YYYY-MM-DD)”
get-daily-summaryreads or searches
“Daily totals: steps, calories, distance, floors, intensity minutes, stress and body battery for a date”
1 input, 1 required
- datestringrequired“Date in YYYY-MM-DD format”
get-respirationreads or searches
“Breathing rate (breaths/min) through the day and during sleep for a date”
1 input, 1 required
- datestringrequired“Date in YYYY-MM-DD format”
get-spo2reads or searches
“Blood oxygen saturation (SpO2) readings for a date”
1 input, 1 required
- datestringrequired“Date in YYYY-MM-DD format”
get-intensity-minutesreads or searches
“Moderate/vigorous intensity minutes for a date and the running weekly total vs goal”
1 input, 1 required
- datestringrequired“Date in YYYY-MM-DD format”
get-floorsreads or searches
“Floors climbed and descended through the day for a date”
1 input, 1 required
- datestringrequired“Date in YYYY-MM-DD format”
get-resting-heart-ratereads or searches
“Daily resting heart rate over a date range”
2 inputs, 1 required
- startDatestringrequired“Start date in YYYY-MM-DD format”
- endDatestring“End date in YYYY-MM-DD format”
get-body-battery-eventsreads or searches
“Events that charged or drained body battery (sleep, activities, stress) for a date”
1 input, 1 required
- datestringrequired“Date in YYYY-MM-DD format”
get-hydrationreads or searches
“Water intake vs goal and sweat loss for a date”
1 input, 1 required
- datestringrequired“Date in YYYY-MM-DD format”
get-body-compositionreads or searches
“Weight, BMI, body fat and muscle mass for a date”
1 input, 1 required
- datestringrequired“Date in YYYY-MM-DD format”
get-weigh-insreads or searches
“All weigh-ins over a date range”
2 inputs, 2 required
- startDatestringrequired“Start date in YYYY-MM-DD format”
- endDatestringrequired“End date in YYYY-MM-DD format”
get-weekly-stepsreads or searches
“Weekly step totals for the weeks ending at a date”
2 inputs, 1 required
- endDatestringrequired“End date in YYYY-MM-DD format”
- weeksinteger“Number of weeks (default 12)”
get-weekly-stressreads or searches
“Weekly average stress for the weeks ending at a date”
2 inputs, 1 required
- endDatestringrequired“End date in YYYY-MM-DD format”
- weeksinteger“Number of weeks (default 12)”
get-weekly-intensity-minutesreads or searches
“Weekly intensity minutes vs goal over a date range”
2 inputs, 2 required
- startDatestringrequired“Start date in YYYY-MM-DD format”
- endDatestringrequired“End date in YYYY-MM-DD format”
get-endurance-scorereads or searches
“Endurance score for a date, or weekly stats when endDate is given (a single date often has no data)”
2 inputs, 1 required
- startDatestringrequired“Start date in YYYY-MM-DD format”
- endDatestring“End date in YYYY-MM-DD format”
get-hill-scorereads or searches
“Hill score (strength + endurance on climbs) for a date, or weekly stats when endDate is given”
2 inputs, 1 required
- startDatestringrequired“Start date in YYYY-MM-DD format”
- endDatestring“End date in YYYY-MM-DD format”
get-running-tolerancereads or searches
“Running load tolerance over a date range”
3 inputs, 2 required
- startDatestringrequired“Start date in YYYY-MM-DD format”
- endDatestringrequired“End date in YYYY-MM-DD format”
- aggregationstring
get-lactate-thresholdreads or searches
“The user's latest lactate threshold measurement (heart rate and pace), a physiological metric detected by the watch.”
Takes no inputs.
get-cycling-ftpreads or searches
“Latest cycling functional threshold power (FTP)”
Takes no inputs.
get-heart-rate-zonesreads or searches
“Configured heart rate zones per sport”
Takes no inputs.
get-fitness-agereads or searches
“Fitness age vs chronological age and what drives it”
1 input, 1 required
- datestringrequired“Date in YYYY-MM-DD format”
get-personal-recordsreads or searches
“Personal records (fastest 1K/5K/10K, longest run, etc.)”
Takes no inputs.
get-progress-summaryreads or searches
“Totals per activity type over a date range for a metric”
3 inputs, 2 required
- startDatestringrequired“Start date in YYYY-MM-DD format”
- endDatestringrequired“End date in YYYY-MM-DD format”
- metricstring
get-activities-by-datereads or searches
“Activities between two dates, optionally filtered by type (e.g.”
5 inputs, 1 required
- startDatestringrequired“Start date in YYYY-MM-DD format”
- endDatestring“End date in YYYY-MM-DD format”
- activityTypestring“Activity type key, e.g.”
- startinteger
- limitinteger
get-activity-typed-splitsreads or searches
“Run/walk/rest splits of an activity”
1 input, 1 required
- activityIdstring or numberrequired“Garmin activity ID”
get-activity-weatherreads or searches
“Weather during an activity”
1 input, 1 required
- activityIdstring or numberrequired“Garmin activity ID”
get-activity-exercise-setsreads or searches
“Strength-training sets, reps and weights of an activity”
1 input, 1 required
- activityIdstring or numberrequired“Garmin activity ID”
get-activity-chart-datareads or searches
“Time series (HR, pace, cadence, elevation...) of an activity, downsampled”
2 inputs, 1 required
- activityIdstring or numberrequired“Garmin activity ID”
- maxPointsinteger“Max samples (default 200)”
get-activity-gearreads or searches
“Gear (e.g.”
1 input, 1 required
- activityIdstring or numberrequired“Garmin activity ID”
get-activity-typesreads or searches
“All Garmin activity type keys”
Takes no inputs.
get-user-settingsreads or searches
“User settings: units, sleep schedule, physiological data (age, weight, height, HR zones, lactate threshold)”
Takes no inputs.
get-devicesreads or searches
“Registered Garmin devices”
Takes no inputs.
get-primary-training-devicereads or searches
“Device used as the source of training status and metrics”
Takes no inputs.
get-last-used-devicereads or searches
“Most recently synced device”
Takes no inputs.
get-gearreads or searches
“All gear (shoes, bikes) with usage”
Takes no inputs.
get-goalsreads or searches
“Goals by status”
1 input
- statusstring
get-training-plansreads or searches
“Available and active training plans”
Takes no inputs.
get-calendarreads or searches
“Calendar for a month: scheduled workouts, activities and events”
2 inputs, 2 required
- yearintegerrequired
- monthintegerrequired“Month, 1-12”
get-daily-briefingreads or searches
“Morning briefing: how the user is today, framed against their own baselines.”
1 input
- datestring“Day to brief on (YYYY-MM-DD), defaults to today in the user's time zone”
show-training-weekreads or searches
“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 …”
1 input
- startDatestring“Any day of the week to show (YYYY-MM-DD); the week starts on its Monday.”
show-performance-dashboardreads or searches
“Show how key health and fitness metrics trend over 4 weeks to 1 year, one small chart per metric on a shared time range.”
3 inputs
- metricsarray“Metrics to show (max 4), default restingHR, hrv, vo2max, sleepScore”
- rangestring“Time range ending at endDate: 4, 12, 26 or 52 weeks (default 12w)”
- endDatestring“Last day shown, YYYY-MM-DD (default today)”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 67 tools
Says what it returns: 93% of 67 tools
States limits, defaults or errors: 10% of 63 tools
Says when to use it: 9% of 64 tools
Items covered per tool: 2.2 of 4 on average

Counted from the listing

Parameters with a description: 91% of 88
Tools with a description: 100% of 67
Typical description length: 138 characters

The tool set

Counted from the listing

Tools: 67
Size of the list: about 10,457 tokens for an agent to load (characters ÷ 4)
Naming: 67 of 67 names use kebab-case

AI reading: easy to mix up

No pair found.

The AI items cover 67 of 67 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the npm package garmin-mcp-app

Our sandbox started this package on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)

{
  "mcpServers": {
    "garmin-mcp-app": {
      "command": "npx",
      "args": [
        "-y",
        "garmin-mcp-app@0.9.1"
      ]
    }
  }
}

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "garmin-mcp-app": {
      "command": "npx",
      "args": [
        "-y",
        "garmin-mcp-app@0.9.1"
      ]
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "garmin-mcp-app": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "garmin-mcp-app@0.9.1"
      ]
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"garmin-mcp-app","type":"stdio","command":"npx","args":["-y","garmin-mcp-app@0.9.1"]}'

Claude Code

claude mcp add --transport stdio garmin-mcp-app -- npx -y garmin-mcp-app@0.9.1

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 -- npx -y garmin-mcp-app@0.9.1

This runs the publisher's code on your machine (npx). Read its README first.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists: 0.9.1
Latest stable: 0.10.0
Status: behind the latest release (1 releases, 5 days)
Withdrawn: no

Source: registry.npmjs.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

Counted in the full dependency tree as resolved on 2026-10-23 (npm audit). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity: sha512-3drgcfp2he27KSyD7…
Signature: signed and attested
License: MIT

Source: the package registry · 2026-10-23.

Usage

Downloads: 575 in the last month

Source: api.npmjs.org · 2026-10-23.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Published package can be started	Started and answered	matches	our test · 2026-10-23
Version 0.9.1 on npm	Exists and can be installed	matches	npm · 2026-10-23
Repository github.com/chenhunghan/garmin-mcp-app	Opens publicly	matches	api.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.github.chenhunghan
GitHub owner: a personal account (chenhunghan)
Build record: signed and attested

Repository: github.com/chenhunghan/garmin-mcp-app
Stars: 16
Repository age: 181–365 days
Last push: 0–30 days ago
Archived: no
Security policy: none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

8 of 9 record checks met

#4,792 of 15,112 packages by monthly downloads, tied with 5 others
#2,075 of 22,952 repositories by GitHub stars, tied with 58 others

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
MetPackage names its licence with a standard (SPDX) identifierMIT
MetThe version the registry lists can be installed and is not withdrawnThe listed version exists; a newer one is out.
Metnpm package carries build provenance (attestation)Signed, with a build attestation naming the source and workflow.
MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.chenhunghan/garmin-mcp-app

Answered from the data above

Is io.github.chenhunghan/garmin-mcp-app safe to install?

We do not rate servers as safe or unsafe. 8 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its npm package carries a build-provenance attestation that names its source repository and build workflow. Its source repository opens publicly. Its repository had a push in the last 90 days. A newer stable release exists than the one listed. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. 8 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.chenhunghan/garmin-mcp-app been security tested?

Partly. 4 of the 13 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

What can io.github.chenhunghan/garmin-mcp-app do?

It lists 67 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data and delete. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.chenhunghan/garmin-mcp-app change or delete data?

8 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.github.chenhunghan/garmin-mcp-app publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Is the listed version current?

No. The registry lists 0.9.1; the latest stable release on npm is 0.10.0.

Where is the source code of io.github.chenhunghan/garmin-mcp-app?

In github.com/chenhunghan/garmin-mcp-app, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

io.github.nietus/anki-mcpAnkialso has tools that creates or changes data, deletes, reads or searchescompare with this one
com.mcparmory/canvasalso has tools that creates or changes data, deletes, reads or searchescompare with this one
io.github.u9401066/pubmed-search-mcpPubMed Searchalso has tools that creates or changes data, deletes, reads or searchescompare with this one
io.github.Mason-Levyy/mfp-mcpMyFitnessPalalso has tools that creates or changes data, deletes, reads or searchescompare with this one
io.github.Jezue/fitatu-apiFitatualso has tools that creates or changes data, deletes, reads or searchescompare with this one
io.github.marcorusc/BioMASSBioMASS ODE Model Builderalso has tools that creates or changes data, deletes, reads or searchescompare with this one

Active servers whose topic is also “science-health-and-education” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: exercised
Fake assistant turns: exercised
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not applicable
Consent handling: not applicable
Sign-in metadata: not applicable

4 exercised9 not run (reason given)5 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 13 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 4

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
12Hidden content
audience-hidingChecks resources that hide content from the user.exercised
13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.exercised

Not run, with the reason · 9

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against

Does not apply to this server · 5

14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
17Consent handling
confused-deputyChecks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted the published package in an isolated sandbox (read-only mode)
116,519 msConnected after 0 redirects.
Read the inventory: 67 tools, 1 resource, 3 prompts.
120,997 msFinished: 4 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

science-health-and-education

AI-classified · 2026-10-23

Pricing modelAI-classified

no value

The website listed in the registry is a code-hosting, package or marketplace page, not the product's own site.

Programming language

TypeScript

api.github.com · 2026-10-23

Hosting type

local package

registry · 2026-10-23

MCP capability

prompts, resources, tools

our test · 2026-10-23

Transport

standard input/output

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

npm

registry · 2026-10-23

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

permissive

package registry · 2026-10-23

Integrity hash

declared (sri)

package registry · 2026-10-23

Signature / provenance

signed and attested

package registry · 2026-10-23

Dependency advisories

none known

npm audit · 2026-10-23

Popularity

575 downloads a month

package registry · 2026-10-23

Publisher signals

owner: a personal account · repository age: 181–365 days · stars: 10–99 · build record: signed and attested

api.github.com · 2026-10-23

Maintenance

active

api.github.com · 2026-10-23

Environment

your machine

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.chenhunghan/garmin-mcp-app: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.chenhunghan/garmin-mcp-app

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.chenhunghan/garmin-mcp-app)](https://protocolprobe.com/mcp/servers/io.github.chenhunghan/garmin-mcp-app)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology