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 Workouts MCP

OCI · GHCR.IO/PRANCISKUS/GARMIN-WORKOUTS-MCP:0.1.2 · SCANNED SEP 20

Manage Garmin Connect workouts, including strength workouts with mapped exercises.

0 this week 37 Trust /100
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 Security0
  • Malware scan not yet available for this package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency45
Schema Quality & AI Usability34
  • AI-judged instruction clarity (poor).Fail
  • Tool/resource definitions use about 238 tokens (~15/item across 15 items; 15 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage14
  • 0% of tools have a non-trivial description (not blank, and not just the tool's name).Fail
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 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 15 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

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 Workouts MCP server?

Garmin Workouts MCP runs locally as a container image, launched with docker run --rm -i ghcr.io/pranciskus/garmin-workouts-mcp:0.1.2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/pranciskus/garmin-workouts-mcp:0.1.2

# add to Claude Code
claude mcp add pranciskus-garmin-workouts-mcp -- docker run --rm -i ghcr.io/pranciskus/garmin-workouts-mcp:0.1.2
// .cursor/mcp.json
{
  "mcpServers": {
    "pranciskus-garmin-workouts-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/pranciskus/garmin-workouts-mcp:0.1.2"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "pranciskus-garmin-workouts-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/pranciskus/garmin-workouts-mcp:0.1.2"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add pranciskus-garmin-workouts-mcp -- docker run --rm -i ghcr.io/pranciskus/garmin-workouts-mcp:0.1.2
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pranciskus-garmin-workouts-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/pranciskus/garmin-workouts-mcp:0.1.2"
      ],
      "enabled": true
    }
  }
}
# ~/.hermes/config.yaml
mcp_servers:
  pranciskus-garmin-workouts-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/pranciskus/garmin-workouts-mcp:0.1.2"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "pranciskus-garmin-workouts-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/pranciskus/garmin-workouts-mcp:0.1.2"
      ]
    }
  }
}
// mcp.json
{
  "mcpServers": {
    "pranciskus-garmin-workouts-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/pranciskus/garmin-workouts-mcp:0.1.2"
      ]
    }
  }
}
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 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 17 Sept 26 +1
    • Stability: 0.97 → pass security
  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1
    • Security disclosure: unverified → fail functional
  • 10 Sept 26 −3
    • Security disclosure: fail → unverified functional
    • Stability: pass → 0.77 functional
  • 9 Sept 26 +1
    • Stability: 0.97 → pass security
  • 8 Sept 26 0
    • Security disclosure: unverified → fail functional
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 20 Sept 2026 · Analysed oci/ghcr.io/pranciskus/garmin-workouts-mcp:0.1.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 15 exposed · ~238 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
delete_workout ~14

No description provided.

NameTypeReqDescription
workout_idstringyes
NameTypeReqDescription
resultbooleanyes

No examples provided.

generate_workout_data_prompt ~15

No description provided.

NameTypeReqDescription
descriptionstringyes

Structured output declared, but exposes no named fields.

No examples provided.

get_activity ~13

No description provided.

NameTypeReqDescription
activity_idstringyes

Structured output declared, but exposes no named fields.

No examples provided.

get_activity_weather ~14

No description provided.

NameTypeReqDescription
activity_idstringyes

Structured output declared, but exposes no named fields.

No examples provided.

get_calendar ~31

No description provided.

NameTypeReqDescription
day
monthintegeryes
startinteger
yearintegeryes

Structured output declared, but exposes no named fields.

No examples provided.

get_workout ~14

No description provided.

NameTypeReqDescription
workout_idstringyes

Structured output declared, but exposes no named fields.

No examples provided.

get_workout_input_schema ~8

No description provided.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

list_activities ~31

No description provided.

NameTypeReqDescription
activityType
limitinteger
search
startinteger

Structured output declared, but exposes no named fields.

No examples provided.

list_supported_strength_exercises ~13

No description provided.

NameTypeReqDescription
query

Structured output declared, but exposes no named fields.

No examples provided.

list_workouts ~6

No description provided.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

preview_workout_payload ~15

No description provided.

NameTypeReqDescription
workout_dataobjectyes

Structured output declared, but exposes no named fields.

No examples provided.

resolve_supported_strength_exercise ~15

No description provided.

NameTypeReqDescription
querystringyes

Structured output declared, but exposes no named fields.

No examples provided.

schedule_workout ~21

No description provided.

NameTypeReqDescription
datestringyes
workout_idstringyes

Structured output declared, but exposes no named fields.

No examples provided.

upload_workout ~14

No description provided.

NameTypeReqDescription
workout_dataobjectyes

Structured output declared, but exposes no named fields.

No examples provided.

validate_workout ~14

No description provided.

NameTypeReqDescription
workout_dataobjectyes

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the Garmin Workouts MCP server?

Garmin Workouts MCP is listed in the public MCP registry as io.github.pranciskus/garmin-workouts-mcp. Manage Garmin Connect workouts, including strength workouts with mapped exercises. This page covers its container image (ghcr.io/pranciskus/garmin-workouts-mcp:0.1.2).

Is the Garmin Workouts MCP server safe to use?

Garmin Workouts MCP scores 37 out of 100 on VerifyMCP. 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 Workouts MCP server expose?

Garmin Workouts MCP exposes 15 tools: list_workouts, get_workout, delete_workout, upload_workout, preview_workout_payload, and 10 more. Their descriptions and schemas cost roughly 238 tokens of context every time the server is loaded.

Is the Garmin Workouts MCP server still maintained?

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

Garmin Workouts 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.