# Garmin Dynamic MCP (pypi · garmin-dynamic-mcp)

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

- Trust score: 77/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- pypi · `garmin-dynamic-mcp`: 77/100 (this document), [markdown](https://verifymcp.io/servers/fabriziodebortoli-garmin-dynamic-mcp/garmin-dynamic-mcp.md), [page](https://verifymcp.io/servers/fabriziodebortoli-garmin-dynamic-mcp/garmin-dynamic-mcp)

## Channel facts

- Registry: `pypi`
- Package: `garmin-dynamic-mcp`
- Version: `0.2.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 5 of 46 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to fabriziodebortoli/garmin-dynamic-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 10 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**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.

## 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.

### Claude

```bash
claude mcp add fabriziodebortoli-garmin-dynamic-mcp -- uvx garmin-dynamic-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "fabriziodebortoli-garmin-dynamic-mcp": {
      "command": "uvx",
      "args": [
        "garmin-dynamic-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "fabriziodebortoli-garmin-dynamic-mcp": {
      "command": "uvx",
      "args": [
        "garmin-dynamic-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add fabriziodebortoli-garmin-dynamic-mcp -- uvx garmin-dynamic-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fabriziodebortoli-garmin-dynamic-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "garmin-dynamic-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add fabriziodebortoli-garmin-dynamic-mcp --command uvx --arg garmin-dynamic-mcp
```

### Hermes

```yaml
mcp_servers:
  fabriziodebortoli-garmin-dynamic-mcp:
    command: "uvx"
    args: ["garmin-dynamic-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "fabriziodebortoli-garmin-dynamic-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "garmin-dynamic-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add fabriziodebortoli-garmin-dynamic-mcp -t stdio -c uvx -a garmin-dynamic-mcp
```

### Other

```json
{
  "mcpServers": {
    "fabriziodebortoli-garmin-dynamic-mcp": {
      "command": "uvx",
      "args": [
        "garmin-dynamic-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 77, +26)

- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.96

### 2026-11-19 (score 51, −11)

- [security regression] Known CVEs: pass → unverified
- [functional regression] Dependency health: 0.96 → unverified

### 2026-11-16 (score 62, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-14 (score 77, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-13 (score 62, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-12 (score 77, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-11 (score 62)

First indexed and scored.

## MCP tools (2)

### `list_endpoints` (~146 tokens)

List Garmin endpoints

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).

Input parameters:

- `query`

Output parameters:

- `result` (string)

### `get` (~286 tokens)

Read Garmin data

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).

Input parameters:

- `fields`
- `params`
- `path` (string, required)

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/fabriziodebortoli-garmin-dynamic-mcp/garmin-dynamic-mcp#diagnostics

## Score history

- 2026-11-21: 77
- 2026-11-20: 77
- 2026-11-19: 51
- 2026-11-18: 62
- 2026-11-17: 62
- 2026-11-16: 62
- 2026-11-15: 77
- 2026-11-14: 77
- 2026-11-13: 62
- 2026-11-12: 77
- 2026-11-11: 62

## 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.

## Links

- PyPI project: https://pypi.org/project/garmin-dynamic-mcp/
- Socket report: https://socket.dev/pypi/package/garmin-dynamic-mcp
- Repository: https://github.com/fabriziodebortoli/garmin-dynamic-mcp
- Changelog RSS feed: https://verifymcp.io/servers/fabriziodebortoli-garmin-dynamic-mcp/garmin-dynamic-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/fabriziodebortoli-garmin-dynamic-mcp/garmin-dynamic-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/fabriziodebortoli-garmin-dynamic-mcp/garmin-dynamic-mcp.json
- HTML version of this page: https://verifymcp.io/servers/fabriziodebortoli-garmin-dynamic-mcp/garmin-dynamic-mcp
