Home / MCP registry index / io.github.Ninjabeam20/sportiq-mcp

io.github.Ninjabeam20/sportiq-mcp

io.github.Ninjabeam20/sportiq-mcp in the official MCP registry. Endpoint https://sportiq.utkarshgupta.org/mcp. Source: github.com/Ninjabeam20/SportIQ-MCP.

The registry describes it as: MCP tools for FIFA World Cup 2026 football, Formula 1, and IPL cricket — sims, strategy, fantasy.

We read its 46 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http sportiq-mcp https://sportiq.utkarshgupta.org/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "sportiq-mcp": {
      "url": "https://sportiq.utkarshgupta.org/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"sportiq-mcp","type":"http","url":"https://sportiq.utkarshgupta.org/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

sportiq_health football_get_groups football_get_fixtures football_get_standings football_get_squad football_get_match_stats football_get_top_scorers football_get_odds football_xg_model football_match_predictor football_simulate_group football_simulate_bracket football_knockout_path football_what_if football_find_value_bets football_form_trends football_build_accumulator f1_get_sessions f1_get_drivers f1_get_lap_times f1_get_standings f1_get_race_results f1_get_weather f1_tyre_degradation f1_undercut_window f1_head_to_head_pace f1_weather_strategy_impact f1_predict_pit_strategy f1_simulate_championship f1_qualifying_analysis f1_race_pace_compare cricket_get_live_matches cricket_get_scorecard cricket_get_points_table cricket_get_schedule cricket_get_squad cricket_get_live_odds cricket_build_dream11_team cricket_captain_recommendation cricket_differential_picks cricket_player_form_index cricket_get_pitch_report cricket_find_value_bets cricket_head_to_head cricket_player_matchup cross_sport_build_accumulator

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-ninjabeam20-sportiq-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-ninjabeam20-sportiq-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.