Remote MCP · Endpoint

DunkAPI MCP server

No. DunkAPI answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.dunkapi.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.noahowsh/dunkapi
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
112 ms
Tools exposed
20 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
NBA player props by sportsbook since 2023, plus play-by-play, shot locations and odds. REST and MCP.
Listing
From the official MCP registry (active).
Recent checks of DunkAPI
CheckedResultHandshake
1 hour agoHandshake completed112 ms
1 day agoHandshake completed113 ms
2 days agoHandshake completed120 ms
3 days agoHandshake completed141 ms
4 days agoHandshake completed126 ms
5 days agoHandshake completed141 ms
6 days agoHandshake completed191 ms
9 days agoHandshake completed210 ms
11 days agoHandshake completed129 ms
14 days agoHandshake completed122 ms
16 days agoHandshake completed106 ms
18 days agoHandshake completed108 ms
20 days agoHandshake completed116 ms
22 days agoHandshake completed129 ms
24 days agoHandshake completed117 ms

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

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