Sports prediction markets for AI agents — live prices, quotes, orders, and positions.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 19 tools
Each tool targets a distinct resource and action (e.g., create vs get vs list for betslips, orders, heartbeats). Overlaps like create_betslip and get_betslip are clearly differentiated by lifecycle stage (creation vs retrieval). No two tools appear to do the same thing.
All tools use snake_case with a consistent verb_noun structure (e.g., list_events, get_order, place_order). Minor variations like close_all_orders remain predictable. No mixing of conventions.
With 19 tools, the set falls into the 16-25 range that the rubric considers borderline heavy. While most tools serve distinct purposes (heartbeat management alone uses four), some consolidation could reduce the surface without losing functionality.
The set covers the full betting lifecycle: events/offers, betslip creation, order placement and closure, heartbeats, balance, positions, and validation. No obvious gaps for core workflows.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
cancel_heartbeatclose_all_ordersclose_ordercreate_betslipcreate_heartbeatget_balanceget_betslipget_exchange_ratesget_orderget_positionlist_betslipslist_event_offerslist_eventslist_heartbeatslist_ordersplace_orderrefresh_heartbeatsnap_pricevalidate_bet_type
Add one secure layer between your agents and this server.