Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AI Ball — AI football match analysis

REMOTE · AIBALL.SAMAGENT.AI · 2 COMPONENTS

Football match outcome probabilities recorded before kick-off, and an open record of results.

+3 this week 80 Trust /100

Last scanned (16 hours ago)

Scores higher than 84% of remote servers

Reachable. Last reached 24 Oct 2026.

Category Entertainment and Games

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 342 tokens (~85/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
  • Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 20. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Oct 26 74

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 24 Oct 2026 · Probed https://aiball.samagent.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.samagent.ai CN=Encryption Everywhere DV TLS CA - G2,OU=www.digicert.com,O=DigiCert Inc,C=US 9 Sept 2026 26 Mar 2027 RSA 2048 SHA256-RSA 4d2497ed2cc7f4719ce6af5ffbd2524
SANs: *.samagent.ai, samagent.ai
CN=Encryption Everywhere DV TLS CA - G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 27 Nov 2017 27 Nov 2027 RSA 2048 SHA256-RSA de0ffb5ee62cb61109f608c9ced5ed3
CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root CA,OU=www.digicert.com,O=DigiCert Inc,C=US 18 Jan 2024 9 Nov 2031 RSA 2048 SHA256-RSA fe032ab844d033106c50c8e13c8b068

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of aiball.samagent.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
samagent.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://aiball.samagent.ai/mcp Verified 200
http (plaintext) http://aiball.samagent.ai/mcp HTTPS enforced 301 https://aiball.samagent.ai/mcp
MCP tools · 4 exposed · ~342 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_match_analysis ~78

Home / draw / away probabilities from each available model, the most likely outcome, the confidence, the pre-match favourite, when the reading was locked, and the result with a hit flag once the match has finished.

NameTypeReqDescription
langstring–Language of team and league names.
match_idstringyesMatch id from list_matches.

No output schema declared.

No examples provided.

get_match_context ~62

Head-to-head summary, recent form, injuries and suspensions, and schedule density, limited to what is shown publicly on the site.

NameTypeReqDescription
langstring–Language of team and league names.
match_idstringyesMatch id from list_matches.

No output schema declared.

No examples provided.

get_open_record ~109

Hits out of matches for the public record, the pre-match favourite and random baselines on the same matches, results by confidence band, and snapshot coverage. Without week_start it covers the whole record; with it, that week only.

NameTypeReqDescription
langstring–Language of team and league names.
tzstring–IANA time zone used to decide which calendar day a match falls on.
week_startstring–YYYY-MM-DD, the Monday of the week. Optional.

No output schema declared.

No examples provided.

list_matches ~93

Matches on one calendar day with their status: upcoming, pending (reading shown, not yet locked) or finished.

NameTypeReqDescription
datestring–YYYY-MM-DD. Defaults to today in tz.
langstring–Language of team and league names.
leaguestring–League name filter, optional.
tzstring–IANA time zone used to decide which calendar day a match falls on.

No output schema declared.

No examples provided.

Install

How do I install the AI Ball — AI football match analysis MCP server?

AI Ball — AI football match analysis is a hosted endpoint at https://aiball.samagent.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · aiball.samagent.ai

# add to Claude Code
claude mcp add --transport http aiballfooty-aiball-mcp 'https://aiball.samagent.ai/mcp'
Common questions

What is the AI Ball — AI football match analysis MCP server?

AI Ball — AI football match analysis is an MCP server listed in the public MCP registry as io.github.aiballfooty/aiball-mcp. Football match outcome probabilities recorded before kick-off, and an open record of results. This page covers its hosted endpoint (https://aiball.samagent.ai/mcp).

Is the AI Ball — AI football match analysis MCP server safe to use?

AI Ball — AI football match analysis scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the AI Ball — AI football match analysis MCP server expose?

AI Ball — AI football match analysis exposes 4 tools: list_matches, get_match_analysis, get_match_context, get_open_record. Their descriptions and schemas cost roughly 342 tokens of context every time the server is loaded.

Does the AI Ball — AI football match analysis MCP server require authentication?

No. We connected to AI Ball — AI football match analysis without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AI Ball — AI football match analysis MCP server still maintained?

AI Ball — AI football match analysis is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.