Remote MCP · Endpoint

The Odds Gap MCP server

No. The Odds Gap answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://theoddsgap.com/assistant/v1/mcp

The last check completed an MCP handshake.

Registry name
com.theoddsgap/answers
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
124 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Ask The Odds Gap sports betting price questions from your AI assistant.
Listing
From the official MCP registry (active).
Recent checks of The Odds Gap
CheckedResultHandshake
1 hour agoHandshake completed124 ms
2 days agoHandshake completed132 ms
4 days agoHandshake completed123 ms
7 days agoHandshake completed115 ms
9 days agoHandshake completed110 ms
11 days agoHandshake completed121 ms
13 days agoHandshake completed137 ms
15 days agoHandshake completed115 ms
16 days agoHandshake completed148 ms
18 days agoHandshake completed211 ms
19 days agoHandshake completed423 ms
20 days agoHandshake completed143 ms
23 days agoHandshake completed240 ms
24 days agoHandshake completed1.10 s

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

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 The Odds Gap and makes no claim about it beyond what these checks measured.