Manage Bet Codes
MCP server · api.managebetcodes.app · found in a public list · checked since 2026-11-14
Live, handshake completed · latest check
https://api.managebetcodes.app/v1/mcp MCP endpoint (Streamable HTTP)The name is the registry's label, not ours. Not reviewed by a person.
Our checks
An unpaid request daily, from eastern North AmericaLast 1 checks, oldest to newest; room for 29 more
1 passed, 0 failed, 29 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hourssince 2026-11-14 | 1 | 0 | — | — | — | — | — | — |
| 7 dayssince 2026-11-14 | 1 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-11-14 | 1 | 0 | — | — | — | — | — | — |
Milliseconds, from eastern North America, timing the whole MCP handshake (initialize to the tools/list answer). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.
Details
Tools listed by the server
mbc_book_codembc_bulk_convertmbc_convert_codembc_convert_to_allmbc_get_event_marketsmbc_get_usagembc_list_bookmakersmbc_list_marketsmbc_manage_jobs_and_historymbc_manage_trackingmbc_merge_codesmbc_resolve_picksmbc_search_eventsmbc_split_codembc_view_slipmbc_view_slip_image
- Tools
- 16
- This list since
- 2026-11-14
- First listed to us
- 2026-11-14
- List changes, 90 days
- 0
Names as the server reported them at our latest completed handshake (mcp-handshake/2); a listed tool is not a tested one. Definitions
Access
- Our latest check
- Nothing asked
- Stated
- not stated
- Payment model
- not known
- Currency
- not known
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Interface it declares
- Protocol
- MCP 2025-06-18
- Capabilities
- promptsresourcestools
- Transports
- streamable-http
As its initialize reply stated it at our check on (mcp-handshake/2): a claim, not tested. Definitions
Calls it declares
mbc_list_bookmakers → count bookmakersmbc_list_markets → count marketsmbc_get_usage → charge_order plan api_credits regular_credits rate_limitsmbc_view_slip code* bookmaker* → code bookmaker status selections total_oddsmbc_view_slip_image code* bookmaker* → code bookmaker mime_type credits_chargedmbc_convert_code code* from_bookmaker* to_bookmakers* → success source billingmbc_convert_to_all code* from_bookmaker* targets include_card → success pairs successful_pairs slips billingmbc_bulk_convert codes* targets include_card → success pairs successful_pairs slips billingmbc_split_code code* bookmaker* method order count target_odds counts → success new_codes parts billingmbc_merge_codes pairs* target → success target_code selections_count billingmbc_search_events bookmaker* queries* sport include_markets market_filter → resultsmbc_get_event_markets bookmaker* event_id* → bookmaker event_id markets
From the tool list it returned to our check (request-shape/2). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.
Links
What it states about itself, from its registry entry or package:
- Website: managebetcodes.app/mcp
- Repository: github.com/kayceepeece/Viewbetbot
Links only (links/3): we follow none of them when showing this page, and a link is not a recommendation. How links are chosen.
Listing
In the capability tree: Other (not placed in a branch yet) (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/7, tree/3) on 2026-11-14. Wrong place? Tell us.
In the index only: does not meet every one of our listing criteria (listing-criteria/6): ✗ what it does is unclear to our placement; ✓ its latest check passed.
Recent probes
| When | Result | Time to headers |
|---|---|---|
cloudflare:EWR |
Live, handshake completed HTTP 200 | 2197 ms |
What these figures do not show
- A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/2) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
- Listed in the Official MCP Registry; this data comes from the Official MCP Registry. Its listing's description is not republished.
- Limited evidence: monitored for under 1 day (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_2b648bf0b37adbe6