Remote MCP · Endpoint

Manage Bet Codes MCP server

No. Manage Bet Codes answered an MCP handshake 37 minutes ago.

UpLast checked 37 minutes ago

Server URL

https://api.managebetcodes.app/v1/mcp

The last check completed an MCP handshake.

Registry name
app.managebetcodes/managebetcodes-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
792 ms
Tools exposed
16 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Convert, view, split, merge and track betting codes across bookmakers.
Listing
From the official MCP registry (active).
Recent checks of Manage Bet Codes
CheckedResultHandshake
37 minutes agoHandshake completed792 ms
4 days agoHandshake completed971 ms
7 days agoHandshake completed813 ms

The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 3 responding of 3.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Manage Bet Codes and makes no claim about it beyond what these checks measured.