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

Garmin Connect (treinos)

REMOTE · API.MCP.AI · SCANNED AUG 3

List, fetch, create, edit (replace), delete and schedule structured workouts on Garmin Connect (runn

Available components

+7 this week 63 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 1448 tokens (~90/item across 16 items; 16 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · api.mcp.ai

# add to Claude Code
claude mcp add --transport http mcp-dir-garmin-mcp https://api.mcp.ai/p_garmin
# ~/.codex/config.toml
[mcp_servers.mcp-dir-garmin-mcp]
url = "https://api.mcp.ai/p_garmin"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mcp-dir-garmin-mcp": {
      "type": "remote",
      "url": "https://api.mcp.ai/p_garmin",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add mcp-dir-garmin-mcp --url https://api.mcp.ai/p_garmin --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  mcp-dir-garmin-mcp:
    url: "https://api.mcp.ai/p_garmin"
// mcp.json
{
  "mcpServers": {
    "mcp-dir-garmin-mcp": {
      "type": "http",
      "url": "https://api.mcp.ai/p_garmin"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 3 Aug 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.200 → 0.9.201 functional
  • 2 Aug 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.197 → 0.9.200 functional
  • 1 Aug 26 +1

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

  • 31 Jul 26 +3
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Jul 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.184 → 0.9.194 functional
  • 28 Jul 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.180 → 0.9.184 functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 3 Aug 2026 · Probed https://api.mcp.ai/p_garmin

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.ai CN=WE1,O=Google Trust Services,C=US 31 Jul 2026 29 Oct 2026 ECDSA 256 ECDSA-SHA256 796a3b1f576e3f2e133c5d19d8f7be3b
SANs: mcp.ai, *.mcp.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b
DNSSEC insecure

Validation of api.mcp.ai. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
mcp.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.mcp.ai/p_garmin Verified 200
http (plaintext) http://api.mcp.ai/p_garmin Inconclusive 406
MCP tools — 16 exposed · ~1,319 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.

Tool Tokens
authenticate ~99

MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.

NameTypeReqDescription
tokenstring

No output schema declared.

No examples provided.

connect ~42

Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

garmin_delete_workout ~56

Delete a workout template from Garmin Connect by workout_id. Bulk support: accepts workout_ids for batched execution.

NameTypeReqDescription
accountstring
workout_idstringyes
workout_idsarray

No output schema declared.

No examples provided.

garmin_edit_workout ~82

Replace a workout: uploads a new workout from payload, then deletes workout_id (no native PUT). Returns new workout_id and previous_workout_id. Bulk support: accepts workout_ids for batched execution.

NameTypeReqDescription
accountstring
workoutobjectyes
workout_idstringyes
workout_idsarray

No output schema declared.

No examples provided.

garmin_get_scheduled_workout ~64

Get one scheduled workout entry by scheduled_workout_id. Bulk support: accepts scheduled_workout_ids for batched execution.

NameTypeReqDescription
accountstring
scheduled_workout_idstringyes
scheduled_workout_idsarray

No output schema declared.

No examples provided.

garmin_get_workout ~68

Get one workout template by workout_id (full structure: segments, steps, targets). Includes raw_data JSON string. Bulk support: accepts workout_ids for batched execution.

NameTypeReqDescription
accountstring
workout_idstringyes
workout_idsarray

No output schema declared.

No examples provided.

garmin_list_accounts ~36

List all Garmin logins linked to this install (id, email, label, created_at).

NameTypeReqDescription
accountstring

No output schema declared.

No examples provided.

garmin_list_scheduled_workouts ~48

List calendar scheduled workouts for a given month/year from Garmin calendar-service.

NameTypeReqDescription
accountstring
monthnumberyes
yearnumberyes

No output schema declared.

No examples provided.

garmin_list_workouts ~55

List saved workouts from Garmin Connect (workout-service). Returns summaries plus raw_data (full JSON string from Garmin).

NameTypeReqDescription
accountstring
limitnumber
startnumber

No output schema declared.

No examples provided.

garmin_schedule_workout ~83

Schedule an existing workout onto the calendar. date must be YYYY-MM-DD (or ISO-8601 date prefix). Returns Garmin schedule response as raw_data. Bulk support: accepts workout_ids for batched execution.

NameTypeReqDescription
accountstring
datestringyes
workout_idstringyes
workout_idsarray

No output schema declared.

No examples provided.

garmin_submit_workout ~118

Create a new structured workout on Garmin Connect. Body must match Garmin API (workoutName, sportType, workoutSegments with ExecutableStepDTO / RepeatGroupDTO). You may omit displayOrder/displayable everywhere and the endCondition on RepeatGroupDTO — the server normalizes them automatically (see workout.description). Multi-sport: sportTypeKey multi_sport (typically sportTypeId 5) with one segment per discipline. Returns workout_id and raw_data.

NameTypeReqDescription
accountstring
workoutobjectyes

No output schema declared.

No examples provided.

garmin_unschedule_workout ~69

Remove workout from calendar by scheduled_workout_id (does not delete the workout template). Bulk support: accepts scheduled_workout_ids for batched execution.

NameTypeReqDescription
accountstring
scheduled_workout_idstringyes
scheduled_workout_idsarray

No output schema declared.

No examples provided.

marketplace ~402

The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin.

NameTypeReqDescription
actionstring
argumentsstring
cancel_commentstring
cancel_reasonstring
conversationstring
immediateboolean
limitnumber
mcp_idstring
messagestring
querystring
report_contextstring
request_detailsstring
request_namestring
tier_slugstring
tool_idstring

No output schema declared.

No examples provided.

report_bug ~50

Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.

NameTypeReqDescription
contextstring
conversationstring
messagestringyes

No output schema declared.

No examples provided.

show_version ~17

Show the current MCP platform and adapter versions.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

toolkit_info ~30

Returns the current toolkit state: installed MCPs, their connection status, and how many catalog tools each exposes.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.