Skip to main content
Glama
Mavline

Odds De-vig MCP Server

by Mavline

Related Servers

Alternatives to Odds De-vig MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Wraps the Sports Game Odds API to provide sports game odds data through natural language queries.
      166 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables fetching sportsbook odds, live scores, and event information across 70+ books and 30+ leagues, with tools to list sports, get scores, and discover events.
      191 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Sorqen is a sports fair-value API + MCP server: it turns sportsbook odds into a versioned, no-vig consensus probability for NFL/NBA/MLB/NHL moneyline, spread, and total markets, with confidence, provenance, and freshness attached to every number instead of a black-box pick.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Provides AI assistants with sports model win probabilities and fair odds across nine sports without requiring an API key.
      3
      60 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Props-first sports odds API with a hosted MCP server. Live odds and player props (moneyline, spreads, totals) across US sportsbooks, normalized to JSON. Tools: get_odds, get_props, get_events, get_books. API-key auth, free tier.
      MIT No Attribution
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to query live sports betting odds, best prices, arbitrage, +EV bets, and middles directly through Model Context Protocol tools.
      8
      MIT

    TDQS

    A3.6/5.0

    Scored across 6 tools

    Disambiguation4/5

    The tools have mostly distinct purposes: sports list, today's games, upcoming odds, processed odds, event consensus, and API usage. However, 'get_processed_odds' and 'get_event_consensus' could overlap for agents looking for the best line on an event, though descriptions clarify that processed odds gives probabilities and consensus gives a single line.

    Naming Consistency4/5

    All tools follow the 'get_' prefix with a resource, which is consistent. The naming is clear and predictable, but some names like 'get_upcoming_odds' and 'get_processed_odds' are similar in structure, which is minor. No mixing of conventions.

    Tool Count5/5

    With 6 tools, the server is well-scoped for a specialized odds processing service. Each tool serves a distinct function, and the count is within the ideal 3-15 range, providing enough coverage without being bloated.

    Completeness4/5

    The tool surface covers listing sports, fetching today's games, upcoming events, processed odds, consensus lines, and API usage. There are minor gaps such as no ability to fetch specific historical games or detailed event details beyond consensus, but the core workflow of getting and processing odds is complete.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues