Remote MCP · Endpoint

GetCourt MCP server

No. GetCourt answered an MCP handshake 58 minutes ago.

UpLast checked 58 minutes ago

Server URL

https://getcourt.co/mcp

The last check completed an MCP handshake.

Registry name
io.github.denis1011101/getcourt
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
352 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Find upcoming tennis, padel and squash games with free spots, by city, sport, level and date.
Listing
From the official MCP registry (active).
Recent checks of GetCourt
CheckedResultHandshake
58 minutes agoHandshake completed352 ms
1 day agoHandshake completed319 ms
3 days agoHandshake completed319 ms
6 days agoHandshake completed312 ms
8 days agoHandshake completed294 ms
9 days agoHandshake completed328 ms
11 days agoHandshake completed332 ms
11 days agoHandshake completed342 ms
13 days agoHandshake completed397 ms
16 days agoHandshake completed300 ms
17 days agoHandshake completed322 ms
19 days agoHandshake completed460 ms
20 days agoHandshake completed375 ms
21 days agoHandshake completed304 ms
22 days agoCredentials required—

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