Remote MCP · Endpoint

AI Ball — AI football match analysis MCP server

No. AI Ball — AI football match analysis answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://aiball.samagent.ai/mcp

The last check completed an MCP handshake.

Registry name
io.github.aiballfooty/aiball-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
818 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Football match outcome probabilities recorded before kick-off, and an open record of results.
Listing
From the official MCP registry (active).
Recent checks of AI Ball — AI football match analysis
CheckedResultHandshake
1 hour agoHandshake completed818 ms
2 days agoHandshake completed790 ms
5 days agoHandshake completed735 ms
7 days agoHandshake completed781 ms
9 days agoHandshake completed748 ms
11 days agoHandshake completed817 ms
13 days agoHandshake completed710 ms
16 days agoHandshake completed746 ms
18 days agoHandshake completed715 ms
19 days agoHandshake completed709 ms
21 days agoHandshake completed716 ms
22 days agoHandshake completed757 ms
23 days agoHandshake completed753 ms

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

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 AI Ball — AI football match analysis and makes no claim about it beyond what these checks measured.