Skip to main content
Glama
zafronix

World Cup History MCP

by zafronix

Related Servers

Alternatives to World Cup History MCP

  • A
    license
    A
    quality
    C
    maintenance
    MCP server for FIFA World Cup 2026 data: matches, teams, venues, city guides, fan zones, visa info, injuries, odds, standings, bracket, and historical matchups. 18 tools, zero external API dependencies.
    18
    216 npm
    34
    MIT

Related Servers

  • F
    license
    B
    quality
    C
    maintenance
    Provides structured access to a World Cup SQLite database via MCP tools, enabling queries for tournaments, team histories, head-to-head matches, and player records.
    4
    -
  • A
    license
    A
    quality
    A
    maintenance
    MCP server for FIFA World Cup 2026 data including fixtures, live scores, odds, and knockout bracket, plus a tool (wc_edge) that autonomously pays for premium data via Injective's x402 protocol.
    8
    14 npm
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    MCP server for retrieving World Cup match briefs, fixtures, and event explanations with sourced, plain-language context.
    MIT
  • F
    license
    Not graded
    quality
    D
    maintenance
    Enables querying FIFA World Cup player and team statistics for 2010, 2014, 2018, and 2022 through natural language, providing tools for top scorers, player comparisons, team summaries, and more via a Claude-powered CLI.
    -
  • A
    license
    A
    quality
    A
    maintenance
    Claudinho gives any MCP client live 2026 World Cup scores, fixtures, group standings, read-only prediction-market signals (Polymarket, informational only), and ready-to-paste match cards. Key-free; the schedule is bundled offline — only live state hits ESPN. Independent fan project — not affiliated with FIFA or Anthropic.
    9
    30
    MIT

TDQS

A4.4/5.0

Scored across 15 tools

Disambiguation5/5

Each tool has a clear, non-overlapping purpose. For example, compare_tournaments is for multi-year comparisons while get_tournament handles single years; get_team vs get_team_roster separate summary from roster; search_players vs get_player_career distinguish lookup from career view.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern (e.g., list_tournaments, get_match, compare_tournaments) using snake_case. There are no mixed conventions or ambiguous names.

Tool Count5/5

With 15 tools, the server is well-scoped for its domain—covering tournaments, teams, players, matches, stadiums, standings, brackets, and trivia without being bloated. The number feels natural for a comprehensive World Cup history API.

Completeness5/5

The tool set covers the major CRUD-like operations for the domain: listing and getting tournaments, teams, players, matches, stadiums, comparisons, trivia, brackets, and standings. There are no obvious gaps for typical World Cup queries.

Maintenance

ActivityInactive
ResponsivenessUnresponsive