Remote MCP · Endpoint
MONS Athletics MCP server
No. MONS Athletics answered an MCP handshake 7 hours ago.
UpLast checked 7 hours ago
Server URL
https://monsathletics.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.monsathletics/mons
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 430 ms
- Tools exposed
- 14 tools
- Uptime, last 30 days
- 100% from 13 checks
- Described by its publisher as
- Find your next endurance challenge and train for it with your MONS coach.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 7 hours ago | Handshake completed | 430 ms |
| 4 days ago | Handshake completed | 453 ms |
| 14 days ago | Handshake completed | 431 ms |
| 15 days ago | Handshake completed | 475 ms |
| 15 days ago | Handshake completed | 452 ms |
| 17 days ago | Handshake completed | 448 ms |
| 18 days ago | Handshake completed | 428 ms |
| 19 days ago | Handshake completed | 432 ms |
| 20 days ago | Handshake completed | 575 ms |
| 21 days ago | Handshake completed | 427 ms |
| 23 days ago | Handshake completed | 503 ms |
| 26 days ago | Handshake completed | 440 ms |
| 28 days ago | Handshake completed | 425 ms |
The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 23 responding of 23.
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 MONS Athletics and makes no claim about it beyond what these checks measured.