Remote MCP · Endpoint

Garmin Connect (treinos) MCP server

No. Garmin Connect (treinos) answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://api.mcp.ai/p_garmin

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/garmin-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
52 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
List, fetch, create, edit (replace), delete and schedule structured workouts on Garmin Connect (runn
Repository
https://github.com/mcp-dir/garmin-mcp
Listing
From the official MCP registry (active).
Recent checks of Garmin Connect (treinos)
CheckedResultHandshake
1 day agoHandshake completed52 ms
4 days agoHandshake completed53 ms
5 days agoHandshake completed698 ms
7 days agoHandshake completed89 ms
8 days agoHandshake completed997 ms
9 days agoHandshake completed148 ms
12 days agoHandshake completed31 ms
13 days agoHandshake completed185 ms
15 days agoHandshake completed76 ms
17 days agoHandshake completed209 ms
18 days agoHandshake completed128 ms
19 days agoHandshake completed123 ms
20 days agoHandshake completed110 ms
20 days agoHandshake completed36 ms
21 days agoHandshake completed74 ms
23 days agoHandshake completed85 ms

The last 16 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Garmin Connect (treinos) and makes no claim about it beyond what these checks measured.