MCP servers › io.github.Mason-Levyy › garmin-personal-mcp

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

io.github.Mason-Levyy/garmin-personal-mcp

Garmin Connect on Garmin's official Personal API: sleep, HRV, body battery, activities. — the publisher's description

8 of 8 record checks metRead-only · tools listed 2026-10-23Topic: science-health-and-education · AI-classifiedversion 0.1.0PythonMITstandard input/output26 tools

Summary

io.github.Mason-Levyy/garmin-personal-mcp is a local MCP server listed in the official MCP registry at version 0.1.0. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 26 tools, 0 resources and 0 prompts.

Record checks

8 of 8 record checks met · 1 does not apply

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
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
not applicable: npm package carries build provenance (attestation)
met: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: no download figure available
#2,021 of 22,952 repositories by GitHub stars, tied with 53 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: PyPI · listed version behind the latest release
License: MIT
Dependencies: no known high or critical advisories
Repository: public
Tools: 26
Described as changing data: 1 of 26 toolsAI-classified
Topic: science-health-and-educationAI-classified
Last tested: 2026-10-23

Add to your client

Worth knowing before you connect it

1 tool is described as changing something (garmin_download_activity): our AI model's reading of the descriptions, not something we tested. We did not call it.
The registry lists 0.1.0; 0.1.1 is newer (1 release).

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.1.0, published 2026-10-22 (registry, as of the 2026-10-23 snapshot)
First listed version: 2026-10-22 (earliest version still in the registry; older removed versions would be earlier)
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.1.0 (published 2026-10-22).

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

26tools

0resources

0prompts

1 of 26 tools are described as changing something (creating, editing, deleting, sending or running).

garmin_get_dayreads or searches
“One day at a glance: daily summary (steps, calories, intensity minutes, resting HR, stress, body battery), last night's sleep, HRV, body battery, stress, and the day's activities.”
Publisher declares: read-only yes · open-world yes
1 input
- datestring or null
garmin_get_daily_summaryreads or searches
“Every all-day wellness total for one date: steps, distance, floors, total/active/BMR calories, intensity minutes, heart rate, stress, body battery, SpO2, respiration, and time active/sedentary/asleep.”
Publisher declares: read-only yes · open-world yes
1 input
- datestring or null
garmin_get_daily_summariesreads or searches
“Daily wellness summaries across a date range, grouped per day (movement, calories, heart rate, intensity minutes, stress, body battery, hydration, respiration, pulse ox, jet lag).”
Publisher declares: read-only yes · open-world yes
2 inputs
- startstring or null
- endstring or null
garmin_get_stepsreads or searches
“Daily total steps, distance (meters), and step goal.”
Publisher declares: read-only yes · open-world yes
2 inputs
- startstring or null
- endstring or null
garmin_get_stressreads or searches
“Daily overall stress level (0-100) and seconds spent in high, medium, low, and rest stress.”
Publisher declares: read-only yes · open-world yes
2 inputs
- startstring or null
- endstring or null
garmin_get_hydrationreads or searches
“Daily water intake, goal, estimated sweat loss, and intake logged during activities, all in mL.”
Publisher declares: read-only yes · open-world yes
2 inputs
- startstring or null
- endstring or null
garmin_get_body_batteryreads or searches
“Daily Body Battery: amount charged and drained, plus the events that moved it (sleep, activities, stress) with Garmin's feedback.”
Publisher declares: read-only yes · open-world yes
3 inputs
- startstring or null
- endstring or null
- chunksinteger or null
garmin_get_heart_ratereads or searches
“Resting, minimum, and maximum heart rate for a day, the 7-day resting average, and any abnormal high/low heart rate alerts.”
Publisher declares: read-only yes · open-world yes
2 inputs
- datestring or null
- include_samplesboolean
garmin_get_spo2reads or searches
“Blood oxygen (pulse ox) for a day: average, lowest, latest, sleep average, 7-day average, hourly averages, and altitude acclimation.”
Publisher declares: read-only yes · open-world yes
2 inputs
- datestring or null
- include_samplesboolean
garmin_get_wellness_activitiesreads or searches
“Wellness activities recorded by the device, each with its type, start and end time, per-metric summary values, and time in zones.”
Publisher declares: read-only yes · open-world yes
2 inputs
- startstring or null
- endstring or null
garmin_get_sleepreads or searches
“The full sleep record for the night ending on date: sleep score and its components, deep/light/REM/awake seconds, start and end times, overnight heart rate, SpO2, respiration, sleep stress, naps, and…”
Publisher declares: read-only yes · open-world yes
1 input
- datestring or null
garmin_get_sleep_summariesreads or searches
“Nightly sleep records across a date range, same fields as garmin_get_sleep.”
Publisher declares: read-only yes · open-world yes
2 inputs
- startstring or null
- endstring or null

Show 14 more tools

garmin_get_hrvreads or searches
“One night of heart-rate variability: the summary (last-night average, 5-minute high, weekly average, baseline band, status) plus every reading taken during sleep.”
Publisher declares: read-only yes · open-world yes
1 input
- datestring or null
garmin_get_hrv_summariesreads or searches
“Nightly HRV summaries across a date range: last-night average, weekly average, baseline band, status, and Garmin's feedback.”
Publisher declares: read-only yes · open-world yes
2 inputs
- startstring or null
- endstring or null
garmin_get_weightreads or searches
“Daily weight summaries over a range, the range average, and the nearest weigh-ins before and after it (handy when the range itself has none).”
Publisher declares: read-only yes · open-world yes
3 inputs
- startstring or null
- endstring or null
- include_allboolean
garmin_get_weight_goalsreads or searches
“Weight goals in effect during a date range and their target ranges.”
Publisher declares: read-only yes · open-world yes
2 inputs
- startstring or null
- endstring or null
garmin_get_food_logreads or searches
“Foods logged in Garmin Connect's nutrition tracker for a day, with serving sizes, calories and nutrients consumed, nutrition goals, and a per-meal breakdown.”
Publisher declares: read-only yes · open-world yes
5 inputs
- datestring or null
- meal_idinteger or null
- include_goalsboolean
- include_nutritionboolean
- include_mediaboolean
garmin_search_activitiesreads or searches
“Recorded activities (runs, rides, swims, strength, dives, ...), newest first, with name, type, start time, distance, duration, pace/speed, HR, power, cadence, calories, elevation, and training effect.”
Publisher declares: read-only yes · open-world yes
32 inputs
- startstring or null
- endstring or null
- searchstring or null
- activity_typestring or null
- activity_subtypestring or null
- excluded_activity_subtypesarray or null
- event_typestring or null
- favoriteboolean or null
- exclude_childrenboolean
- sort_bystring or null
- sort_orderstring or null
- min_distanceinteger or null
- max_distanceinteger or null
- min_durationinteger or null
- max_durationinteger or null
- min_elapsed_durationinteger or null
- max_elapsed_durationinteger or null
- min_elevationinteger or null
- max_elevationinteger or null
- min_avg_powerinteger or null
- northnumber or null
- southnumber or null
- eastnumber or null
- westnumber or null
- min_max_depthinteger or null
and 7 more not listed here.
garmin_get_activityreads or searches
“Full detail for one activity: summary metrics (distance, time, pace, HR, power, cadence, elevation, training effect, calories), device and location metadata, and split/lap summaries.”
Publisher declares: read-only yes · open-world yes
1 input, 1 required
- activity_idintegerrequired
garmin_get_activity_workoutsreads or searches
“The structured workout(s) followed during an activity, step by step with targets.”
Publisher declares: read-only yes · open-world yes
1 input, 1 required
- activity_idintegerrequired
garmin_download_activitydescribed as changing data
“Download an activity's original file (a ZIP, usually holding a .fit) and save it on the machine running this server as activity-<activity_id>.zip, replacing any earlier download.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
- activity_idintegerrequired
- directorystring or null
garmin_get_profilereads or searches
“Profile settings: display name, measurement system and display formats, time zone, hydration units and containers, and preferred training days.”
Publisher declares: read-only yes · open-world yes
Takes no inputs.
garmin_get_heart_rate_zonesreads or searches
“Heart rate zone floors per sport, with the training method and the resting, max, and lactate threshold heart rates the zones were built on.”
Publisher declares: read-only yes · open-world yes
1 input
- generate_defaultsboolean
garmin_get_fitness_agereads or searches
“Fitness age versus chronological age as of a date, the achievable fitness age, and the components behind it (vigorous days and minutes, resting heart rate, BMI or body fat %), or the reason none is a…”
Publisher declares: read-only yes · open-world yes
2 inputs
- datestring or null
- full_history_scanboolean
garmin_get_menstrual_cyclereads or searches
“Menstrual cycle summary as of a date: current phase, day in cycle, days until the next phase, period length, fertile window, predicted ovulation and cycle length, and pregnancy details when tracking …”
Publisher declares: read-only yes · open-world yes
1 input
- datestring or null
garmin_get_menstrual_dayreads or searches
“One day in detail: logged symptoms, flow, mood, and other entries, that day's cycle summary, and weekly weight goal ranges during pregnancy.”
Publisher declares: read-only yes · open-world yes
5 inputs
- datestring or null
- todaystring or null
- reducedboolean
- skip_baby_movementboolean
- include_analysisboolean

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. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. 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 26 tools
Says what it returns: 100% of 26 tools
States limits, defaults or errors: 0% of 17 tools
Says when to use it: 8% of 26 tools
Items covered per tool: 2.4 of 4 on average

Counted from the listing

Parameters with a description: 0% of 80
Tools with a description: 100% of 26
Typical description length: 318 characters

The tool set

Counted from the listing

Tools: 26
Size of the list: about 5,478 tokens for an agent to load (characters ÷ 4)
Naming: 26 of 26 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 26 of 26 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. 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 PyPI package garmin-personal-mcp

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-personal-mcp": {
      "command": "uvx",
      "args": [
        "garmin-personal-mcp==0.1.0"
      ]
    }
  }
}

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

{
  "mcpServers": {
    "garmin-personal-mcp": {
      "command": "uvx",
      "args": [
        "garmin-personal-mcp==0.1.0"
      ]
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "garmin-personal-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "garmin-personal-mcp==0.1.0"
      ]
    }
  }
}

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

code --add-mcp '{"name":"garmin-personal-mcp","type":"stdio","command":"uvx","args":["garmin-personal-mcp==0.1.0"]}'

Claude Code

claude mcp add --transport stdio garmin-personal-mcp -- uvx garmin-personal-mcp==0.1.0

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

npx @modelcontextprotocol/inspector@2.11.0 -- uvx garmin-personal-mcp==0.1.0

Optional settings the entry also lists (left out above): GARMIN_PERSONAL_API_KEY, GARMIN_MCP_DOWNLOAD_DIR.
This runs the publisher's code on your machine (uvx). 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.1.0
Latest stable: 0.1.1
Status: behind the latest release (1 releases, 1 days)
Withdrawn: no

Source: pypi.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 (OSV.dev). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity: sha256-f5413f2c002b0cdee…
License: MIT

Source: the package registry · 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.1.0 on PyPI	Exists and can be installed	matches	PyPI · 2026-10-23
Repository github.com/Mason-Levyy/garmin-personal-mcp	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.Mason-Levyy · 2 servers
GitHub owner: a personal account (Mason-Levyy)

Repository: github.com/Mason-Levyy/garmin-personal-mcp
Stars: 17
Repository age: 0–30 days
Last push: 0–30 days ago
Archived: no
Security policy: SECURITY.md

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 8 record checks met · 1 does not apply

Not ranked by downloads: no download figure available
#2,021 of 22,952 repositories by GitHub stars, tied with 53 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.
MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
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.
Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
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.Mason-Levyy/garmin-personal-mcp

Answered from the data above

Is io.github.Mason-Levyy/garmin-personal-mcp safe to install?

We do not rate servers as safe or unsafe. 8 of its 8 applicable record checks are met (facts from public records, each listed on this page). What the records show: 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. 1 of its tools describes 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.Mason-Levyy/garmin-personal-mcp been security tested?

Partly. 2 of the 12 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.Mason-Levyy/garmin-personal-mcp do?

It lists 26 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. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.Mason-Levyy/garmin-personal-mcp change or delete data?

1 of its tools says in its description that it creates, edits, deletes, sends or runs something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.github.Mason-Levyy/garmin-personal-mcp publish a security policy?

Yes: its repository has a public security policy (github.com/mason-levyy/garmin-personal-mcp/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Is the listed version current?

No. The registry lists 0.1.0; the latest stable release on PyPI is 0.1.1.

Where is the source code of io.github.Mason-Levyy/garmin-personal-mcp?

In github.com/Mason-Levyy/garmin-personal-mcp, 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.cyanheads/pubmed-mcp-serveralso has tools that reads or searchescompare with this one
io.github.cyanheads/clinicaltrialsgov-mcp-serveralso has tools that reads or searchescompare with this one
io.github.amos689/paper-preflightpaper-preflightalso has tools that reads or searchescompare with this one
io.github.nietus/anki-mcpAnkialso has tools that reads or searchescompare with this one
com.mcparmory/canvasalso has tools that reads or searchescompare with this one
io.github.iowarp/adios-mcpCLIO Adiosalso has tools that 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: not run · nothing to check it against
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not applicable
Consent handling: not applicable
Sign-in metadata: not applicable

2 exercised10 not run (reason given)6 not applicable

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

Exercised · 2

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised

Not run, with the reason · 10

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
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against

Does not apply to this server · 6

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
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)
8,027 msConnected after 0 redirects.
Read the inventory: 26 tools, 0 resources, 0 prompts.
8,536 msFinished: 2 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

not checked

no website in the registry entry

Programming language

Python

api.github.com · 2026-10-23

Hosting type

local package

registry · 2026-10-23

MCP capability

experimental, 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

pypi

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 (sha256)

package registry · 2026-10-23

Signature / provenance

does not apply

PyPI publishes no registry signature or attestation equivalent to npm dist.signatures

Dependency advisories

none known

OSV.dev · 2026-10-23

Popularity

not known (our limit)

Our lookup failed (network error, timeout or rate limit). This is our limit, not the server's.

Publisher signals

owner: a personal account · repository age: 0–30 days · stars: 10–99

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.Mason-Levyy/garmin-personal-mcp: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.Mason-Levyy/garmin-personal-mcp

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.Mason-Levyy/garmin-personal-mcp)](https://protocolprobe.com/mcp/servers/io.github.Mason-Levyy/garmin-personal-mcp)

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