Odds-API MCP Server

22 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated:

2 can modify or destroy data
20 read-only
22 tools total

Community server · catalogue entry verified 03/07/2026

How to control Odds-API MCP Server ↓

What Odds-API MCP Server exposes to your agents

Read (20) Write / Execute (2) Destructive / Financial (0)
High Risk

The most dangerous Odds-API MCP Server tools

2 of Odds-API MCP Server's 22 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Odds-API MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Odds-API MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations
{
  "clear_selected_bookmakers": {
    "limits": [
      {
        "counter": "clear_selected_bookmakers_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "get_arbitrage_bets": {
    "limits": [
      {
        "counter": "get_arbitrage_bets_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Odds-API MCP Server — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON ODDS-API →

Instant setup, no code required.

All 22 Odds-API MCP Server tools

READ 20 tools
Read get_arbitrage_bets Get arbitrage opportunities across bookmakers. Returns profit margin, optimal stake distribution, and direct b Read get_bookmakers List all supported bookmakers with their name and active status. Read get_documentation Fetch the complete Odds-API.io API documentation. Read get_dropping_odds Get odds that have dropped the most from opening, based on sharp bookmaker data. Useful for tracking where sha Read get_event Get a single event by its unique ID. Read get_events Get events for a sport with filtering by league, participant, status, date range, bookmaker availability, and Read get_historical_events Get finished events for a sport and league within a date range (max 31-day span). Read get_historical_odds Get closing odds and final scores for a finished event from selected bookmakers. Read get_leagues Get leagues for a sport. Returns league name, slug, and active event count. Read get_live_events Get all currently live events across all sports, optionally filtered by sport. Read get_multi_odds Get odds for multiple events in a single request (up to 10 events). Counts as only 1 API call. Read get_odds Get betting odds for a specific event from selected bookmakers. Read get_odds_movements Get historical odds line movements for an event from a bookmaker. Returns opening, latest, and all intermediat Read get_participant Get a single participant/team by their unique ID. Read get_participants Get teams/participants for a sport, optionally filtered by name search. Read get_selected_bookmakers Get the authenticated user Read get_sports List all available sports with their name and slug identifier. Read get_updated_odds Get odds updated since a Unix timestamp for a bookmaker and sport. The timestamp must be at most 1 minute old. Read get_value_bets Get positive expected value betting opportunities for a bookmaker. Updated every 5 seconds. EV formula: (Proba Read search_events Search events by team name or text query. Returns up to 10 matching results.

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about Odds-API MCP Server

How do I prevent bulk modifications through Odds-API MCP Server? +

The Odds-API MCP Server server has 2 write tools including clear_selected_bookmakers, select_bookmakers. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Odds-API MCP Server.

How many tools does the Odds-API MCP Server MCP server expose? +

22 tools across 3 categories: Destructive, Read, Write. 20 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on Odds-API MCP Server? +

Register the Odds-API MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Odds-API MCP Server tool call.

Deterministic rules across all 22 Odds-API MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

22 Odds-API MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.