A timeout, disconnect or output error does not always mean the server did no work. Preserve the request ID and inspect Usage before deliberately making another data request.
REST service errors
A 503 or 504 means a required dependency is unavailable or a deadline expired. Do not replace the response with cached active odds or continuously retry. Errors themselves are free, but a separate completed request can have settled before your client failed to observe it.
MCP connection and tool checks
Use https://api.oddswire.io/mcp and the supported OAuth or API-key host setup.
Confirm your owner/admin workspace has its active key and required data permissions.
List tools and run the free get_usage observation.
For data, choose an approved namespace and discover fixture identities before requesting odds.
A connector can authenticate successfully and still have no data grants. Narrow filters for a result that exceeds tool row/byte limits. MCP makes no automatic retry or pagination; an output-size rejection can follow a charged upstream response.
Escalate safely
Send support the host/client name, operation/tool, request ID, approximate UTC time and redacted error. Do not send API keys, OAuth tokens, cookies or a complete private response. See MCP limits and setup.