MCP server exposing 3 tools for betsapi.
This URL is a JSON-RPC 2.0 endpoint over HTTP. Issue POST requests with a JSON-RPC body. Browsers and search crawlers land here on GET.
POST https://gateway.pipeworx.io/betsapi/mcp
Content-Type: application/json
{"jsonrpc":"2.0","id":1,"method":"tools/list"}betsapi_inplay — Live in-play sport matches happening right now, with running score and match clock. Pass a sport_id (1=Soccer, 18=Basketball, 13=Tennis, 16=Baseball, 17=Ice Hockey, 12=American Football, 91=Volleyball, 78=Handball, 3=Cricket, 14=Snooker, 92=Table Tennis, 15=Darts, 9=Boxing/MMA). Example: betsapi_inplay({ sport_id: "1", _apiKey: "your-key" })betsapi_upcoming — Upcoming (scheduled) sport events for a sport, optionally for a given day. Pass a sport_id (1=Soccer, 18=Basketball, 13=Tennis, 16=Baseball, 17=Ice Hockey, 12=American Football, 91=Volleyball, 78=Handball, 3=Cricket, 14=Snooker, 92=Table Tennis, 15=Darts, 9=Boxing/MMA) and optionally day=YYYYMMDD. Example: betsapi_upcoming({ sport_id: "1", day: "20260704", _apiKey: "your-key" })betsapi_event_odds — Bookmaker odds for a single event across markets (moneyline, spreads, totals). Odds are deeply nested by market, so the full structure is returned under `raw`. Get an event_id from betsapi_inplay or betsapi_upcoming first. Example: betsapi_event_odds({ event_id: "12345678", _apiKey: "your-key" })Code samples (curl / TypeScript / one-click client install), schemas, and the live playground are on the pack page:
https://pipeworx.io/packs/betsapi/
Pipeworx is an open MCP gateway connecting AI agents to live data. pipeworx.io