Skip to main content
Glama
rapidoddsapi

rapidoddsapi-mcp

Official
by rapidoddsapi

Related Servers

Alternatives to rapidoddsapi-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      MCP-compatible server that gives AI agents access to alternative sports data across 30+ leagues — odds, events, probabilities, settlement, and futures for prediction markets, DFS platforms, and sportsbooks.
      29
      7
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server that brings live Australian racing and sports odds from 12 bookmaker/exchange sources into AI assistants, with per-price age data and tools for next races, best odds, results, and movers.
      9
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      MCP server that provides structured access to real-time sportsbook data from iddaa, including live events, competitions, and league fixtures with strategy analysis. Designed for AI agents and automation workflows.
      5
      54
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that connects Claude Desktop to The Odds API, giving Claude real-time access to sports odds, scores, and schedules across 80+ sports and leagues worldwide.
      -
    • A
      license
      A
      quality
      C
      maintenance
      MCP server that connects AI assistants to the Statos football analytics platform, enabling natural language queries for match predictions, betting picks, league information, and admin market-suppression controls.
      7
      9
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for the FootballStack football data API. Gives LLM clients and AI agents (Claude, Cursor) access to real football data — fixtures, standings, lineups, live events, shot-level xG with pitch coordinates, and model-derived fair odds.
      12
      MIT

    TDQS

    A4.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a distinct purpose: one lists coverage, one fetches live scores, one fetches odds, and two analyze odds for arbitrage/value. There is no overlap that could cause an agent to select the wrong tool.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: get_results, list_sports, get_odds, find_arbitrage, find_value_bets. The verbs 'get' and 'find' are both action-oriented and the style is uniform.

    Tool Count5/5

    Five tools is an appropriate scope for a betting odds API: it covers the core data access (sports, results, odds) and the two main analytical use cases (arbitrage and value betting) without unnecessary bloat.

    Completeness5/5

    The tool set covers the full lifecycle of the domain: discovering coverage, retrieving live results, pulling current odds, and calculating betting opportunities. There are no obvious missing operations for a read-only odds service.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues