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.

io.github.Ninjabeam20/sportiq-mcp

REMOTE · SPORTIQ.UTKARSHGUPTA.ORG · 2 COMPONENTS · SCANNED SEP 24

MCP tools for FIFA World Cup 2026 football, Formula 1, and IPL cricket — sims, strategy, fantasy.

+60 this week 78 Trust /100
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 Security63
Transport & Reachability100
Schema Quality & AI Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 6973 tokens (~154/item across 45 items; 44 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
  • Stability observed for 22 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 44 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 45 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
Install

How do I install the io.github.Ninjabeam20/sportiq-mcp server?

io.github.Ninjabeam20/sportiq-mcp is a hosted endpoint at https://sportiq.utkarshgupta.org/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 · sportiq.utkarshgupta.org

# add to Claude Code
claude mcp add --transport http ninjabeam20-sportiq-mcp 'https://sportiq.utkarshgupta.org/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "ninjabeam20-sportiq-mcp": {
      "url": "https://sportiq.utkarshgupta.org/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ninjabeam20-sportiq-mcp": {
      "type": "http",
      "url": "https://sportiq.utkarshgupta.org/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.ninjabeam20-sportiq-mcp]
url = "https://sportiq.utkarshgupta.org/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ninjabeam20-sportiq-mcp": {
      "type": "remote",
      "url": "https://sportiq.utkarshgupta.org/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ninjabeam20-sportiq-mcp --url 'https://sportiq.utkarshgupta.org/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ninjabeam20-sportiq-mcp:
    url: "https://sportiq.utkarshgupta.org/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ninjabeam20-sportiq-mcp": {
      "Transport": "http",
      "Url": "https://sportiq.utkarshgupta.org/mcp"
    }
  }
}
# add to Vellum
assistant mcp add ninjabeam20-sportiq-mcp -t streamable-http -u 'https://sportiq.utkarshgupta.org/mcp'
// mcp.json
{
  "mcpServers": {
    "ninjabeam20-sportiq-mcp": {
      "type": "http",
      "url": "https://sportiq.utkarshgupta.org/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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 Sept 26 +1

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

  • 21 Sept 26 +1

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

  • 20 Sept 26 +58
    • Injection markers: unverified → pass ▲ security
    • Authorization: unverified → partial ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Stability: unverified → 0.60 ▲ functional
  • 13 Sept 26 −55
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: 0.33 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 12 Sept 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.

  • 11 Sept 26 +54
    • Injection markers: unverified → pass ▲ security
    • Authorization: unverified → partial ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Stability: unverified → 0.30 ▲ functional
  • 10 Sept 26 −53
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Authorization: partial → unverified ▼ security
    • Stability: 0.23 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 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.

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 Sept 2026 · Probed https://sportiq.utkarshgupta.org/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=utkarshgupta.org CN=WE1,O=Google Trust Services,C=US 5 Sept 2026 4 Dec 2026 ECDSA 256 ECDSA-SHA256 3ffdcfe1fe814c2d13f5d81ac468b5a4
SANs: utkarshgupta.org, *.utkarshgupta.org
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of sportiq.utkarshgupta.org. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
org. present 26974 8 Verified
utkarshgupta.org. 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://sportiq.utkarshgupta.org/mcp Verified 200
http (plaintext) http://sportiq.utkarshgupta.org/mcp Inconclusive 406
MCP tools · 44 exposed · ~6,936 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
cricket_build_dream11_team ~388

Recommend an optimal fantasy XI + captain + vice-captain for one fixture. Args: match_id: CricAPI match identifier; resolves team_a/team_b/venue automatically. team_a: First team code/name (e.g. ``MI``). Required if match_id is absent. team_b: Second team code/name (e.g. ``CSK``). Required if match_id is absent. venue: Venue key/name (e.g. ``wankhede``). Required if match_id is absent. strategy: ``"balanced"`` only in Phase 2; future variants reserved. Returns: data.players: 11 picked players with name/role/credits/team/projected_points. data.captain: name of the chosen captain. data.vice_captain: name of the chosen VC. data.total_credits: sum of credits used (<= 100). data.total_projected_points: fantasy points including C x2 and VC x1.5 boosts. meta.estimated: true — projections are model output, not a fantasy oracle. Example: cricket_build_dream11_team(team_a="MI", team_b="CSK", venue="wankhede") cricket_build_dream11_team(match_id="abc123")

NameTypeReqDescription
match_id––CricAPI match identifier; resolves team_a/team_b/venue automatically.
strategystring–``"balanced"`` only in Phase 2; future variants reserved.
team_a––First team code/name (e.g. ``MI``). Required if match_id is absent.
team_b––Second team code/name (e.g. ``CSK``). Required if match_id is absent.
venue––Venue key/name (e.g. ``wankhede``). Required if match_id is absent.
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

cricket_captain_recommendation ~198

Return the top-3 captain candidates ranked by projected points. Args: match_id: CricAPI match identifier; resolves team_a/team_b/venue automatically. team_a: First team code/name. Required if match_id is absent. team_b: Second team code/name. Required if match_id is absent. venue: Venue key/name. Required if match_id is absent. Returns: data.candidates: list of 3 dicts with name/role/team/projected_points. meta.source: model:captain_score. meta.estimated: true.

NameTypeReqDescription
match_id––CricAPI match identifier; resolves team_a/team_b/venue automatically.
team_a––First team code/name. Required if match_id is absent.
team_b––Second team code/name. Required if match_id is absent.
venue––Venue key/name. Required if match_id is absent.
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

cricket_differential_picks ~269

Suggest low-ownership picks with positive projected upside. Ownership is *estimated* — proxied by credit weight (lower-credit players tend to have lower ownership), not real ownership data. Flagged ``estimated: true`` in the response. Args: match_id: CricAPI match identifier; resolves team_a/team_b/venue automatically. team_a: First team code/name. Required if match_id is absent. team_b: Second team code/name. Required if match_id is absent. venue: Venue key/name. Required if match_id is absent. ownership_threshold: percent ownership cap; affects estimated label. Returns: data.picks: list of {name, role, team, credits, projected_points, estimated_ownership_pct}. meta.source: model:captain_score (filtered). meta.estimated: true.

NameTypeReqDescription
match_id––CricAPI match identifier; resolves team_a/team_b/venue automatically.
ownership_thresholdinteger–percent ownership cap; affects estimated label.
team_a––First team code/name. Required if match_id is absent.
team_b––Second team code/name. Required if match_id is absent.
venue––Venue key/name. Required if match_id is absent.
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

cricket_find_value_bets ~333

Compare model probabilities against market-implied IPL odds. Requires THEODDS_KEY. NOTE: cricket has no calibrated team-strength model wired yet (unlike the football Elo/Poisson path), so this tool currently returns an EMPTY ``value_bets`` list — scoring an edge against a neutral 50/50 prior would flag every market underdog, which would be misleading. It still reports how many events were screened so callers know odds were available. For raw de-vigged prices use ``cricket_get_live_odds``. Real edge detection lands when a cricket win model is wired (see cricket_head_to_head). Args: team: Optional team name to filter events (case-insensitive substring). Omit to scan every IPL odds event. min_edge: Minimum edge (model_prob - devigged_market_prob), 0..1. Default 0.05. Currently informational only (no bets emitted). Returns: data.value_bets: always ``[]`` until a cricket model is wired. data.events_analysed: count of events screened (both teams present). data.model: ``"neutral_baseline"``. data.note: why no bets are emitted. meta.estimated: true.

NameTypeReqDescription
min_edgenumber–Minimum edge (model_prob - devigged_market_prob), 0..1. Default 0.05. Currently informational only (no bets emitted).
team––Optional team name to filter events (case-insensitive substring). Omit to scan every IPL odds event.
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

cricket_get_live_matches ~63

Return all currently live cricket matches across all series. Returns: data.matches: list of live match objects (team names, score, status). meta.source: which adapter served the response. meta.is_stale: true if data is from stale cache.

Input schema present but exposes no named parameters.

NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

cricket_get_live_odds ~237

Return live market head-to-head odds for upcoming/live IPL matches. Sourced from The Odds API (requires THEODDS_KEY). Without a key the call returns a clean ALL_SOURCES_FAILED envelope rather than crashing. Args: team: Optional team name to filter events (case-insensitive substring, matched against both sides). Omit to return every IPL event. The Odds API uses its own opaque event ids, so a CricAPI match_id cannot be resolved to an event yet — filtering is by team name. Returns: data.events: list of {event_id, home, away, commence_time, bookmakers: [{name, home, away}]} with decimal h2h prices per bookmaker. meta.source: adapter that served the data (theodds / cache:stale).

NameTypeReqDescription
team––Optional team name to filter events (case-insensitive substring, matched against both sides). Omit to return every IPL event. The Odds API uses its own opaque event ids, so a CricAPI match_id cannot…
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

cricket_get_pitch_report ~105

Summarise pitch characteristics for a venue. Args: venue: Venue key (e.g. ``wankhede``), official name, or city. Returns: data: {batting_friendly 0..1, expected_first_inn, recommendation, venue, pitch_type}. meta.source: which adapter served the venue record.

NameTypeReqDescription
venuestringyesVenue key (e.g. ``wankhede``), official name, or city.
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

cricket_get_points_table ~100

Return the points table / standings for a cricket series. Args: series_id: The series identifier (e.g. IPL 2026 series ID from CricAPI). Returns: data: points table rows with team, P, W, L, NRR, Points. meta.source: adapter that served the data.

NameTypeReqDescription
series_idstringyesThe series identifier (e.g. IPL 2026 series ID from CricAPI).
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

cricket_get_schedule ~189

Return the upcoming match schedule, optionally filtered by series. Args: series_id: Optional. Filter to a specific series. If omitted, returns all upcoming fixtures across all active series. limit: Max matches to return, 1..200 (default 50). offset: Number of matches to skip for paging (default 0). Returns: data.matches: page of upcoming matches with teams, date, venue. data.pagination: {total, count, offset, limit, has_more, next_offset}. meta.source: adapter that served the data.

NameTypeReqDescription
limitinteger–Max matches to return, 1..200 (default 50).
offsetinteger–Number of matches to skip for paging (default 0).
series_id––Optional. Filter to a specific series. If omitted, returns all upcoming fixtures across all active series.
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

cricket_get_scorecard ~85

Return the full scorecard for a specific match. Args: match_id: The match identifier (e.g. from cricket_get_live_matches). Returns: data: full scorecard with innings, partnerships, bowling figures. meta.source: adapter that served the data.

NameTypeReqDescription
match_idstringyesThe match identifier (e.g. from cricket_get_live_matches).
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

cricket_get_squad ~166

Return the squad roster for a cricket team, optionally for a specific series. Args: team: Team code or name (e.g. "MI", "CSK", "IND", "AUS"). series_id: Optional. Series ID to pull the tournament-specific squad. If omitted, falls back to static seed data. Returns: data.players: list of players with name, role, and credits. meta.source: adapter that served the data (cricapi / static_seed).

NameTypeReqDescription
series_id––Optional. Series ID to pull the tournament-specific squad. If omitted, falls back to static seed data.
teamstringyesTeam code or name (e.g. "MI", "CSK", "IND", "AUS").
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

cricket_head_to_head ~171

Compare two cricket teams head-to-head using squad form and player stats. Args: team_a: First team code or name (e.g. "MI", "India"). team_b: Second team code or name (e.g. "CSK", "Australia"). Returns: data: {team_a, team_b, team_a_edge_count, team_b_edge_count, key_players_a, key_players_b, h2h_win_rate_a, h2h_win_rate_b, win_prob_a, win_prob_b}. meta.estimated: true.

NameTypeReqDescription
team_astringyesFirst team code or name (e.g. "MI", "India").
team_bstringyesSecond team code or name (e.g. "CSK", "Australia").
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

cricket_player_form_index ~126

Report a 0-100 form score for a player using the player_stats chain. Args: player_id: Upstream player identifier (CricAPI/Cricbuzz id). Returns: data.form_score: 0..100 indicator. data.trend: "rising" / "stable" / "falling". data.samples: how many recent innings were available. meta.source: which adapter served the underlying stats. meta.estimated: true.

NameTypeReqDescription
player_idstringyesUpstream player identifier (CricAPI/Cricbuzz id).
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

cricket_player_matchup ~130

Analyse the head-to-head matchup between two cricket players based on role and career stats. Args: player_a: Player ID or name for the first player. player_b: Player ID or name for the second player. Returns: data: {matchup_type, edge_holder, edge_reason, signals, role_a, role_b}. meta.estimated: true — heuristic model, not ball-by-ball H2H data.

NameTypeReqDescription
player_astringyesPlayer ID or name for the first player.
player_bstringyesPlayer ID or name for the second player.
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

cross_sport_build_accumulator ~122

Model the joint probability of multiple outcomes across football and cricket. Args: legs: Total legs across both sports (2-8). Default 3. min_edge: Minimum edge per leg. Default 0.05. Returns: data: same shape as football_build_accumulator, with sport field per leg. meta.estimated: true.

NameTypeReqDescription
legsinteger–Total legs across both sports (2-8). Default 3.
min_edgenumber–Minimum edge per leg. Default 0.05.
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

f1_get_drivers ~76

Return driver list for a specific F1 session. Args: session_key: OpenF1 session identifier. Returns: data.drivers: list of driver objects with driver_number, full_name, team. meta.source: adapter that served the data.

NameTypeReqDescription
session_keyintegeryesOpenF1 session identifier.
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

f1_get_lap_times ~240

Return lap times for a driver in a specific F1 session. Args: session_key: OpenF1 session identifier. driver_number: Driver's race number (e.g. 1 for Verstappen). limit: Max laps to return, 1..200 (default 100 — covers most full races). offset: Number of laps to skip for paging (default 0). Returns: data.laps: page of lap objects with lap_number and lap_duration. OpenF1 does not put compound/tyre_life here — those live on the stints endpoint. data.pagination: {total, count, offset, limit, has_more, next_offset}. meta.source: adapter that served the data.

NameTypeReqDescription
driver_numberintegeryesDriver's race number (e.g. 1 for Verstappen).
limitinteger–Max laps to return, 1..200 (default 100 — covers most full races).
offsetinteger–Number of laps to skip for paging (default 0).
session_keyintegeryesOpenF1 session identifier.
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

f1_get_race_results ~148

Return the final classification for one F1 race, keyed by year and round. Args: year: Championship year (e.g. 2025). round: Round number within the season (1-based; e.g. 1 for the opener). Returns: data.results: Ergast/Jolpica RaceTable payload — finishing order, times, grid positions, points, and fastest laps for the race. meta.source: adapter that served the data.

NameTypeReqDescription
roundintegeryesRound number within the season (1-based; e.g. 1 for the opener).
yearintegeryesChampionship year (e.g. 2025).
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

f1_get_sessions ~117

Return F1 sessions for a given year, optionally filtered by country. Args: year: Championship year (e.g. 2025). country: Optional country name to filter (e.g. "Monaco"). Returns: data.sessions: list of session objects with session_key, session_type, date. meta.source: adapter that served the data.

NameTypeReqDescription
country––Optional country name to filter (e.g. "Monaco").
yearintegeryesChampionship year (e.g. 2025).
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

f1_get_standings ~93

Return F1 driver and constructor championship standings for a year. Args: year: Championship year (e.g. 2025). Returns: data.driver_standings: driver championship positions and points. data.constructor_standings: constructor championship positions and points. meta.source: adapter that served the data.

NameTypeReqDescription
yearintegeryesChampionship year (e.g. 2025).
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

f1_get_weather ~72

Return weather data for a specific F1 session. Args: session_key: OpenF1 session identifier. Returns: data.weather: list of weather snapshots with temperature, rainfall, wind. meta.source: adapter that served the data.

NameTypeReqDescription
session_keyintegeryesOpenF1 session identifier.
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

f1_head_to_head_pace ~121

Compare lap-time pace distribution between two drivers in a session. Args: session_key: OpenF1 session identifier. driver_a: First driver's race number. driver_b: Second driver's race number. Returns: data: {driver_a_avg_s, driver_b_avg_s, delta_s, faster_driver}. meta.estimated: true.

NameTypeReqDescription
driver_aintegeryesFirst driver's race number.
driver_bintegeryesSecond driver's race number.
session_keyintegeryesOpenF1 session identifier.
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

f1_predict_pit_strategy ~378

Predict the optimal pit-stop strategy for a driver in an F1 race session. Args: session_key: OpenF1 session identifier for a recorded race. driver_number: Driver's race number (e.g. 1 for Verstappen). current_lap: Current lap to project from (default 1 = full race ahead). total_laps: Total race laps. If omitted, inferred from the highest observed lap_number in the fetched laps (correct for Monaco 78 / Spa 44), falling back to 57 when no laps are available. An explicit value always wins. Returns: data.stop_laps: recommended pit laps. data.compound_sequence: tyre compounds for each stint. data.expected_finish_position: currently always None (not modelled). data.confidence: 0.0-1.0 model confidence. meta.total_laps: race length used (explicit arg, else inferred from laps). meta.estimated: true. Example: f1_predict_pit_strategy(session_key=9158, driver_number=1) f1_predict_pit_strategy(session_key=9158, driver_number=16, current_lap=20, total_laps=78)

NameTypeReqDescription
current_lapinteger–Current lap to project from (default 1 = full race ahead).
driver_numberintegeryesDriver's race number (e.g. 1 for Verstappen).
session_keyintegeryesOpenF1 session identifier for a recorded race.
total_laps––Total race laps. If omitted, inferred from the highest observed lap_number in the fetched laps (correct for Monaco 78 / Spa 44), falling back to 57 when no laps are available. An explicit value alway…
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

f1_qualifying_analysis ~135

Analyse a qualifying session: best lap per driver, gap to pole, projected grid. Args: session_key: OpenF1 session identifier for a Qualifying session. Returns: data.grid: [{position, driver_number, full_name, team_name, best_lap_gap_s}]. data.pole_time_s: pole lap duration in seconds. data.drivers_analysed: count of drivers with valid laps. meta.estimated: true — grid derived from session laps, not official timing.

NameTypeReqDescription
session_keyintegeryesOpenF1 session identifier for a Qualifying session.
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

f1_race_pace_compare ~129

Compare race-pace and tyre degradation between two F1 drivers in a session. Args: session_key: OpenF1 session identifier. driver_a: First driver's race number. driver_b: Second driver's race number. Returns: data: {by_compound, overall_faster, compounds_compared}. meta.estimated: true — degradation model fit, not official timing.

NameTypeReqDescription
driver_aintegeryesFirst driver's race number.
driver_bintegeryesSecond driver's race number.
session_keyintegeryesOpenF1 session identifier.
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

f1_tyre_degradation ~146

Fit a tyre degradation model for a driver + compound in a session. Args: session_key: OpenF1 session identifier. driver_number: Driver's race number. compound: Tyre compound (SOFT, MEDIUM, HARD, INTER, WET). Returns: data: {intercept, slope, residual_std, sample_count}. meta.estimated: true — model output, not telemetry oracle.

NameTypeReqDescription
compoundstringyesTyre compound (SOFT, MEDIUM, HARD, INTER, WET).
driver_numberintegeryesDriver's race number.
session_keyintegeryesOpenF1 session identifier.
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

f1_undercut_window ~144

Estimate whether an undercut is viable for the attacker against the target. Args: session_key: OpenF1 session identifier. attacker_number: Attacking driver's race number. target_number: Target driver's race number. current_lap: Current lap number in the race. Returns: data: {laps_to_clear, viable, marginal}. meta.estimated: true.

NameTypeReqDescription
attacker_numberintegeryesAttacking driver's race number.
current_lapintegeryesCurrent lap number in the race.
session_keyintegeryesOpenF1 session identifier.
target_numberintegeryesTarget driver's race number.
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

f1_weather_strategy_impact ~77

Analyse weather data and recommend compound or pit-window adjustments. Args: session_key: OpenF1 session identifier. Returns: data: {has_rain, avg_track_temp_c, compound_recommendation, recommendation}. meta.estimated: true.

NameTypeReqDescription
session_keyintegeryesOpenF1 session identifier.
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

football_build_accumulator ~164

Model the joint probability of several match outcomes from the top model-vs-market gaps. Calls ``football_find_value_bets`` internally to fetch live odds, then selects the strongest legs and combines them under the joint-probability model. Args: legs: Number of legs (2-8). Default 3. min_edge: Minimum edge threshold per leg. Default 0.05. Returns: data: {legs, legs_used, combined_odds, combined_model_prob, combined_edge, risk_flag, independence_warning}. meta.estimated: true.

NameTypeReqDescription
legsinteger–Number of legs (2-8). Default 3.
min_edgenumber–Minimum edge threshold per leg. Default 0.05.
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

football_find_value_bets ~327

Surface the largest gaps between the model's win probability and the market. De-vigs each market's 1X2 decimal odds (removes the margin so implied probabilities sum to 1) and compares them to this server's own match-outcome probabilities — the same Elo/Poisson path ``football_match_predictor`` uses. Where the model probability exceeds the de-vigged market probability by at least ``min_edge``, the outcome is flagged with its edge and the model's fair odds. Args: team: Optional team name to filter events (case-insensitive substring, matched against both sides). Omit to scan every WC 2026 odds event. min_edge: Minimum edge (model_prob - devigged_market_prob), 0..1. Default 0.05 (5 percentage points). Returns: data.value_bets: list of {event_id, home, away, outcome, model_prob, fair_odds, market_odds, edge, bookmaker}, sorted by edge descending. data.events_analysed: events with both teams rated (model-comparable). meta.estimated: true. meta.is_stale reflects the odds freshness.

NameTypeReqDescription
min_edgenumber–Minimum edge (model_prob - devigged_market_prob), 0..1. Default 0.05 (5 percentage points).
team––Optional team name to filter events (case-insensitive substring, matched against both sides). Omit to scan every WC 2026 odds event.
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

football_form_trends ~118

Return rolling form, goal record, and xG trend for a football team. Args: team: Team name (e.g. "Brazil", "Argentina"). Returns: data: {form_string, wins, draws, losses, goals_scored, goals_conceded, xg_for, xg_against, recent_trend, matches_analysed}. meta.estimated: true — derived from available fixture data.

NameTypeReqDescription
teamstringyesTeam name (e.g. "Brazil", "Argentina").
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

football_get_fixtures ~162

Return World Cup 2026 fixtures (live providers, else the group schedule). Args: limit: Max fixtures to return, 1..200 (default 50). offset: Number of fixtures to skip for paging (default 0). Returns: data.fixtures: page of {home, away, date/group, status, home_goals, away_goals}. data.pagination: {total, count, offset, limit, has_more, next_offset}. meta.source: adapter that served the data (static_seed = group schedule only).

NameTypeReqDescription
limitinteger–Max fixtures to return, 1..200 (default 50).
offsetinteger–Number of fixtures to skip for paging (default 0).
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

football_get_groups ~92

Return the FIFA World Cup 2026 group draw and advancement format. Returns: data.groups: {group_letter: [4 team codes]} for all 12 groups. data.format: 48-team / 12-group / top-2 + 8-best-thirds rule. data.teams: team-code -> {name, fifa_code} metadata. meta.source: adapter that served the data.

Input schema present but exposes no named parameters.

NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

football_get_match_stats ~130

Return a team's aggregate World Cup tournament statistics. Network-only enrichment: requires a configured API-Football (or football-data.org) key. There is no offline static fallback, so without a key the call returns a clean ALL_SOURCES_FAILED envelope. Args: team: API-Football numeric team id (not a country code). Returns: data.team_stats: {team, played, wins, goals_for, goals_against}. meta.source: adapter that served the data.

NameTypeReqDescription
teamintegeryesAPI-Football numeric team id (not a country code).
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

football_get_odds ~178

Return live market head-to-head odds for upcoming World Cup 2026 matches. Sourced from The Odds API (requires THEODDS_KEY). Without a key the call returns a clean ALL_SOURCES_FAILED envelope rather than crashing. Args: team: Optional team name to filter events (case-insensitive substring, matched against both sides). Omit to return every WC event. Returns: data.events: list of {event_id, home, away, commence_time, bookmakers: [{name, home, draw, away}]} with decimal 1X2 prices per bookmaker. meta.source: adapter that served the data (theodds / cache:stale).

NameTypeReqDescription
team––Optional team name to filter events (case-insensitive substring, matched against both sides). Omit to return every WC event.
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

football_get_squad ~131

Return a national team's World Cup squad. Args: team: Team code or name (e.g. "ARG"). Without an API-Football key, the static seed serves an empty-but-valid squad (rosters are a follow-up). Returns: data.squad: list of {name, number, position, age}. meta.source: adapter that served the data.

NameTypeReqDescription
teamstringyesTeam code or name (e.g. "ARG"). Without an API-Football key, the static seed serves an empty-but-valid squad (rosters are a follow-up).
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

football_get_standings ~148

Return current World Cup 2026 group standings. Args: limit: Max standing rows to return, 1..200 (default 50). offset: Number of rows to skip for paging (default 0). Returns: data.standings: page of {rank, team, group, points, played, goals_diff}. data.pagination: {total, count, offset, limit, has_more, next_offset}. meta.source: adapter that served the data.

NameTypeReqDescription
limitinteger–Max standing rows to return, 1..200 (default 50).
offsetinteger–Number of rows to skip for paging (default 0).
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

football_get_top_scorers ~52

Return the World Cup 2026 top scorers. Returns: data.scorers: list of {name, team, goals, assists}. meta.source: adapter that served the data.

Input schema present but exposes no named parameters.

NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

football_knockout_path ~142

Round-by-round survival probabilities for one team in the full sim. Args: team: Team code (e.g. "FRA"). iterations: Number of tournament simulations (clamped to 100..20000). seed: Optional RNG seed. Returns: data: {team, reach_r32, reach_r16, reach_qf, reach_sf, reach_final, win}. meta.estimated: true.

NameTypeReqDescription
iterationsinteger–Number of tournament simulations (clamped to 100..20000).
seed––Optional RNG seed.
teamstringyesTeam code (e.g. "FRA").
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

football_match_predictor ~123

Predict a single match: most likely scoreline + outcome probabilities. Args: home_team: First team code. away_team: Second team code. neutral: True for a neutral venue (World Cup default). Returns: data: {most_likely_score, home_win, draw, away_win, predicted_winner}. meta.estimated: true.

NameTypeReqDescription
away_teamstringyesSecond team code.
home_teamstringyesFirst team code.
neutralboolean–True for a neutral venue (World Cup default).
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

football_simulate_bracket ~259

Monte Carlo the full World Cup 2026 — per-team round + title probabilities. Simulates all 12 groups, advances the top 2 + 8 best third-placed teams to a 32-team knockout, and plays it to a champion, ``iterations`` times. Args: iterations: Number of tournament simulations (clamped to 100..20000; ~10000 gives stable ±2% probabilities). seed: Optional RNG seed for reproducible output. Returns: data.teams: {code: {reach_r32, reach_r16, reach_qf, reach_sf, reach_final, win}} sorted by win probability descending. data.champion: most likely winner. data.iterations: iterations run. meta.estimated: true. meta.conditioned_matches: completed matches locked in (played group results fixed, decided knockout ties locked). Example: football_simulate_bracket() football_simulate_bracket(iterations=20000, seed=42)

NameTypeReqDescription
iterationsinteger–Number of tournament simulations (clamped to 100..20000; ~10000 gives stable ±2% probabilities).
seed––Optional RNG seed for reproducible output.
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

football_simulate_group ~140

Monte Carlo one group within the full 12-group qualification context. Args: group: Group letter A-L. iterations: Number of simulations (clamped to 100..20000). Returns: data.teams: Per-team position probabilities, p_auto_advance, p_best_third_advance, truthful combined p_advance, and avg_points. data.iterations: iterations actually run. meta.estimated: true. meta.conditioned_matches: completed matches locked in.

NameTypeReqDescription
groupstringyesGroup letter A-L.
iterationsinteger–Number of simulations (clamped to 100..20000).
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

football_xg_model ~157

Estimate a match's expected goals and win/draw/loss probabilities. Args: home_team: First team code (e.g. "ARG"). away_team: Second team code (e.g. "BRA"). neutral: True for a neutral venue (no home advantage). World Cup default. Returns: data: {expected_home_goals, expected_away_goals, home_win, draw, away_win}. meta.estimated: true.

NameTypeReqDescription
away_teamstringyesSecond team code (e.g. "BRA").
home_teamstringyesFirst team code (e.g. "ARG").
neutralboolean–True for a neutral venue (no home advantage). World Cup default.
NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

sportiq_health ~55

Report cache backend, per-adapter healthcheck, and quota status. Returns: HealthReport-shaped dict with `cache_backend`, `cache_ok`, `adapters` (per-source ok/detail), and `quotas`.

Input schema present but exposes no named parameters.

NameTypeReqDescription
data–––
error–––
meta–––

No examples provided.

Common questions

What is the io.github.Ninjabeam20/sportiq-mcp server?

io.github.Ninjabeam20/sportiq-mcp is listed in the public MCP registry as io.github.Ninjabeam20/sportiq-mcp. MCP tools for FIFA World Cup 2026 football, Formula 1, and IPL cricket, sims, strategy, fantasy. This page covers its hosted endpoint (https://sportiq.utkarshgupta.org/mcp).

Is the io.github.Ninjabeam20/sportiq-mcp server safe to use?

io.github.Ninjabeam20/sportiq-mcp scores 78 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 io.github.Ninjabeam20/sportiq-mcp server expose?

io.github.Ninjabeam20/sportiq-mcp exposes 44 tools: sportiq_health, football_get_groups, football_get_fixtures, football_get_standings, football_get_squad, and 39 more. Their descriptions and schemas cost roughly 6,936 tokens of context every time the server is loaded.

Does the io.github.Ninjabeam20/sportiq-mcp server require authentication?

No. We connected to io.github.Ninjabeam20/sportiq-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.Ninjabeam20/sportiq-mcp server still maintained?

io.github.Ninjabeam20/sportiq-mcp is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.