Serverdex live check · status history

Manage Bet Codes MCP server status

● Answering1,002 ms handshakechecked Nov 22, 2026, 12:09 UTC

No. At the last Serverdex check (Nov 22, 2026, 12:09 UTC) the Manage Bet Codes endpoint answered the MCP initialize handshake in 1,002 ms and listed 16 tools.

Uptime, 30 days
100%
4 days on record
Uptime, 90 days
100%
4 days on record
Answering since
Nov 18, 2026
without a failed check
Tools now
16
≈ 5.1k tokens of definitions

Status history

1 change on record · only changes are stored, not every check
  1. First checked: answering

Questions

Is Manage Bet Codes down right now?
No. At the last Serverdex check (Nov 22, 2026, 12:09 UTC) the Manage Bet Codes endpoint answered the MCP initialize handshake in 1,002 ms and listed 16 tools.
How is Manage Bet Codes checked?
Serverdex calls the server's hosted endpoint about once a day with a plain MCP initialize followed by tools/list, with no credentials, and records only changes: a status flip or a change in the tool list. Uptime is time-weighted from those changes, so a server checked for less than a day shows no percentage.
What does "needs sign-in" mean for Manage Bet Codes?
The endpoint is reachable and speaks HTTP, but returns 401 or 403 until a key or OAuth sign-in is supplied. The server is up; the Serverdex check cannot read its tools without an account.

Back to the Manage Bet Codes listing · test any endpoint yourself with the MCP server health check · what changed across the registry today: MCP server changelog.