Remote MCP · Endpoint

com.voxodds/voxodds MCP server

Yes, as of 2 hours ago: the server returned an HTTP error.

DownLast checked 2 hours ago

Server URL

https://voxodds.com/mcp

The last check failed: the server returned an HTTP error.

Registry name
com.voxodds/voxodds
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
18 tools
Uptime, last 30 days
83.3% from 18 checks
Described by its publisher as
All-in outcome rankings with live depth, fees, verified rules, EV checks, and track records.
Listing
From the official MCP registry (active).
Recent checks of com.voxodds/voxodds
CheckedResultHandshake
2 hours agoFailed - the server returned an HTTP error—
1 day agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
3 days agoHandshake completed63 ms
4 days agoHandshake completed57 ms
5 days agoHandshake completed60 ms
7 days agoHandshake completed48 ms
9 days agoHandshake completed45 ms
12 days agoHandshake completed50 ms
14 days agoHandshake completed110 ms
16 days agoHandshake completed50 ms
18 days agoHandshake completed44 ms
20 days agoHandshake completed43 ms
22 days agoHandshake completed48 ms
24 days agoHandshake completed106 ms
26 days agoHandshake completed47 ms
27 days agoHandshake completed46 ms
29 days agoHandshake completed54 ms

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

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 com.voxodds/voxodds and makes no claim about it beyond what these checks measured.