Statos MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STATOS_API_KEY | Yes | Required. Your Statos API key. | |
| STATOS_API_BASE | No | Base URL for the Statos API. Defaults to https://api.statos.pro. Use https://api.sandbox.statos.pro for sandbox. | https://api.statos.pro |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_picksA | List Statos's current betting suggestions, optionally filtered by league, market type, minimum edge, or quality tier. Each pick carries the model's claimed probability, best available odds (where attached), implied edge, and a confidence label (low/medium/high). Picks are computed live from upcoming fixtures; volumes vary by day. Use this for 'what does Statos suggest today?' type queries. |
| get_match_picksA | Fetch every suggestion the Statos engine has emitted for a single match. Useful for per-match analysis: 'what does Statos think about match X across every market?'. Returns the same BetSuggestion shape as list_picks but scoped to one match. |
| list_leaguesA | List the soccer leagues the Statos engine tracks (filtered to what the API-key holder's plan permits). Each league carries an |
| get_accountA | Return the API-key holder's account info: email, role (silver/gold/diamond/admin), subscription status, and the effective role (trial-elevated while a trial is active). Useful for an AI assistant to explain what plan the user is on and which leagues they have access to. Read-only. |
| suppress_marketA | ADMIN kill switch: stop Statos emitting a (league × market) for a time window WITHOUT a deploy — e.g. during the World Cup if 'cards' starts firing 30% below claimed hit rate. Requires an admin key with the admin:market_suppressions scope. league_id 0 = all leagues. Reversible via unsuppress_market or expiry. Use sparingly. |
| list_suppressionsA | List the currently active market suppressions (the kill switches in effect). Read-only; same admin scope as suppress_market. |
| unsuppress_marketA | Cancel an active market suppression by id, immediately restoring emission (within ~60s). Requires the admin:market_suppressions scope. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct resource and action: account retrieval, suppression listing, pick listing, per-match pick retrieval, league listing, and suppression creation/cancellation. The only potential overlap (list_picks vs get_match_picks) is clearly differentiated by scope and description.
All tool names follow a consistent verb_noun pattern in snake_case (get_account, list_suppressions, list_picks, get_match_picks, list_leagues, suppress_market, unsuppress_market). Verb choice and structure are predictable throughout.
Seven tools is well-scoped for a betting suggestions server: read operations for account, leagues, and picks, plus admin suppression management. Each tool earns its place with no redundancy.
The server covers account info, discovery (leagues), picks retrieval (global and per-match), and a full suppression lifecycle (list, create, cancel). No obvious gaps exist for the stated purpose.