Remote MCP · Endpoint

io.github.iFan6oy/flash-props-api MCP server

No. io.github.iFan6oy/flash-props-api answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.flashodds.live/mcp

The last check completed an MCP handshake.

Registry name
io.github.iFan6oy/flash-props-api
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
157 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Flash Props API: player-prop analysis, projections, evidence, and line movement over REST/MCP.
Listing
From the official MCP registry (active).
Recent checks of io.github.iFan6oy/flash-props-api
CheckedResultHandshake
1 hour agoHandshake completed157 ms
1 day agoHandshake completed906 ms
2 days agoHandshake completed277 ms
3 days agoHandshake completed254 ms
4 days agoHandshake completed291 ms
5 days agoHandshake completed266 ms
6 days agoHandshake completed379 ms
9 days agoHandshake completed131 ms
11 days agoHandshake completed131 ms
14 days agoHandshake completed3.17 s
16 days agoHandshake completed294 ms
18 days agoHandshake completed414 ms
20 days agoHandshake completed2.22 s
22 days agoHandshake completed498 ms
24 days agoHandshake completed132 ms
26 days agoHandshake completed164 ms
28 days agoHandshake completed130 ms
29 days agoHandshake completed816 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 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 io.github.iFan6oy/flash-props-api and makes no claim about it beyond what these checks measured.