Remote MCP · Endpoint
gol24 MCP server
No. gol24 answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://gol24.uz/mcp
The last check completed an MCP handshake.
- Registry name
- uz.gol24/gol24
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 580 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 100% from 13 checks
- Described by its publisher as
- Uzbek football news from gol24.uz: transfers, quotes, results, club and player news.
- Website
- https://gol24.uz/mcp-docs
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 580 ms |
| 4 days ago | Handshake completed | 579 ms |
| 7 days ago | Handshake completed | 953 ms |
| 16 days ago | Handshake completed | 661 ms |
| 16 days ago | Handshake completed | 660 ms |
| 18 days ago | Handshake completed | 610 ms |
| 19 days ago | Handshake completed | 651 ms |
| 20 days ago | Handshake completed | 601 ms |
| 21 days ago | Handshake completed | 585 ms |
| 22 days ago | Handshake completed | 586 ms |
| 23 days ago | Handshake completed | 584 ms |
| 26 days ago | Handshake completed | 599 ms |
| 29 days ago | Handshake completed | 589 ms |
The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 24 responding of 24.
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 gol24 and makes no claim about it beyond what these checks measured.