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
584 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 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).
Recent checks of gol24
CheckedResultHandshake
1 hour agoHandshake completed584 ms
2 days agoHandshake completed599 ms
5 days agoHandshake completed589 ms
7 days agoHandshake completed586 ms
9 days agoHandshake completed562 ms
11 days agoHandshake completed568 ms
13 days agoHandshake completed558 ms
15 days agoHandshake completed607 ms
18 days agoHandshake completed569 ms
19 days agoHandshake completed615 ms
21 days agoHandshake completed575 ms
21 days agoHandshake completed559 ms
23 days agoHandshake completed611 ms
25 days agoHandshake completed555 ms

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

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 gol24 and makes no claim about it beyond what these checks measured.