Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Garmin Dynamic MCP

PYPI · GARMIN-DYNAMIC-MCP

Read-only access to your Garmin Connect data. Key in the OS keychain, self-updating catalog.

Available components

0 this week 77 Trust /100

Last scanned (13 hours ago)

Scores higher than 71% of PyPI servers

Category Health and Science

Trust breakdown (7 categories)

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
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 5 of 46 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to fabriziodebortoli/garmin-dynamic-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 10 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability61
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 532 tokens (~266/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +26
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.96 ▲ functional
  • 19 Nov 26 −11
    • Known CVEs: pass → unverified ▼ security
    • Dependency health: 0.96 → unverified ▼ functional
  • 16 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 14 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 13 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 12 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 11 Nov 26 62

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed pypi/garmin-dynamic-mcp@0.2.2

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 pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo fabriziodebortoli/garmin-dynamic-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/fabriziodebortoli/garmin-dynamic-mcp/.github/workflows/release.yml@refs/heads/main
Rekor log index 3806152357
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:5b8d8ca07bac5d32b1f85e1ed5a56105f2c53db22bf2698f0561bfeac4f8598a

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 46 packages
Packages resolved 46
Stale 3
No linked repository 2
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~432 tokens

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 →

Tool Tokens
get ~286

Call one Garmin Personal API endpoint (GET only) and return compact JSON. path: an endpoint path exactly as listed by list_endpoints (with the {placeholders}). params: values for that endpoint's path and query parameters, e.g. {"startDate": "2026-11-01", "endDate": "2026-11-09"}. For the activity search endpoint, `limit` is the total number of activities wanted (pages are fetched automatically, up to 1000) and startDate/endDate filter by date. fields: optional dotted paths to keep, e.g. ["startTimeLocal", "distance", "averageRunningCadenceInStepsPerMinute"]. Activities come with a useful default set when fields is omitted. Returns {"data": ..., "partial": bool, "notes": [...], "key_warning": str|null}. If partial is true, read notes: the result was cut and says how to narrow the request. Responses are capped at about 40,000 characters (roughly 150 activities in the default view): for long periods pass a short `fields` list. If key_warning is not null, tell the user. If update_available is present, tell the user once (version and how to update).

NameTypeReqDescription
fields–––
params–––
pathstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

list_endpoints ~146

List the Garmin Personal API endpoints this server can call, with their parameters. query: optional case-insensitive text matched against path and summary (e.g. "sleep"). Each entry has: path, summary, params (name, location 'path' or 'query', required, type), verified (whether the endpoint was tested against a real account), disabled (sensitive endpoints are off unless GARMIN_MCP_ENABLE_SENSITIVE=1) and, when known, max_range_days (longer date ranges are split automatically). Date parameters use YYYY-MM-DD. If the answer contains update_available, tell the user once (version and how to update).

NameTypeReqDescription
query–––
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the Garmin Dynamic MCP server?

Garmin Dynamic MCP runs locally as a PyPI package, launched with uvx garmin-dynamic-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · garmin-dynamic-mcp

# add to Claude Code
claude mcp add fabriziodebortoli-garmin-dynamic-mcp -- uvx garmin-dynamic-mcp
Common questions

What is the Garmin Dynamic MCP server?

Garmin Dynamic MCP is listed in the public MCP registry as io.github.fabriziodebortoli/garmin-dynamic-mcp. Read-only access to your Garmin Connect data. Key in the OS keychain, self-updating catalog. This page covers its PyPI package (garmin-dynamic-mcp).

Is the Garmin Dynamic MCP server safe to use?

Garmin Dynamic MCP scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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 Garmin Dynamic MCP server expose?

Garmin Dynamic MCP exposes 2 tools: list_endpoints, get. Their descriptions and schemas cost roughly 432 tokens of context every time the server is loaded.

Is the Garmin Dynamic MCP server still maintained?

Garmin Dynamic MCP is still listed as active in the MCP registry. We last reached this channel on 21 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 Garmin Dynamic MCP server under?

Garmin Dynamic MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Garmin Dynamic MCP server?

VerifyMCP ran 15 checks on Garmin Dynamic MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Garmin Dynamic MCP: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.