Remote MCP · Endpoint

QuinielaHoy MCP server

No. QuinielaHoy answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://quinielahoy.net/mcp

The last check completed an MCP handshake.

Registry name
net.quinielahoy/quinielahoy
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
115 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Argentine quiniela and Telekino results: cabezas, full draws, number check. Read only.
Listing
From the official MCP registry (active).
Recent checks of QuinielaHoy
CheckedResultHandshake
2 days agoHandshake completed115 ms
3 days agoHandshake completed990 ms
4 days agoHandshake completed131 ms
5 days agoHandshake completed93 ms
7 days agoHandshake completed947 ms
7 days agoHandshake completed194 ms
8 days agoHandshake completed227 ms
9 days agoHandshake completed69 ms
11 days agoHandshake completed847 ms
14 days agoHandshake completed279 ms
16 days agoHandshake completed90 ms
19 days agoHandshake completed802 ms
21 days agoHandshake completed106 ms
23 days agoHandshake completed71 ms
25 days agoHandshake completed100 ms
27 days agoHandshake completed97 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.

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