Remote MCP · Endpoint

CoachSync MCP server

No. CoachSync answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.coachsync.io/mcp

The last check completed an MCP handshake.

Registry name
io.coachsync/coachsync-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
112 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Barbell strength training tools for AI assistants. Warmup, plate loading, and LP.
Listing
From the official MCP registry (active).
Recent checks of CoachSync
CheckedResultHandshake
1 hour agoHandshake completed112 ms
2 days agoHandshake completed91 ms
4 days agoHandshake completed32 ms
5 days agoHandshake completed65 ms
7 days agoHandshake completed69 ms
8 days agoHandshake completed317 ms
9 days agoHandshake completed57 ms
12 days agoHandshake completed80 ms
13 days agoHandshake completed68 ms
15 days agoHandshake completed31 ms
16 days agoHandshake completed59 ms
18 days agoHandshake completed53 ms
19 days agoHandshake completed55 ms
20 days agoHandshake completed42 ms
20 days agoHandshake completed52 ms
21 days agoHandshake completed31 ms
22 days agoHandshake completed208 ms

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

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.

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