Remote MCP · Endpoint

Private Clubs MCP server

No. Private Clubs answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://www.theprivateclubs.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.theprivateclubs/private-clubs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
115 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search, look up and compare private membership clubs worldwide
Listing
From the official MCP registry (active).
Recent checks of Private Clubs
CheckedResultHandshake
34 minutes agoHandshake completed115 ms
9 days agoHandshake completed105 ms
10 days agoHandshake completed141 ms
11 days agoHandshake completed222 ms
12 days agoHandshake completed168 ms
14 days agoHandshake completed216 ms
14 days agoHandshake completed109 ms
15 days agoHandshake completed98 ms
17 days agoHandshake completed172 ms
19 days agoHandshake completed156 ms
21 days agoHandshake completed129 ms
24 days agoHandshake completed233 ms
26 days agoHandshake completed99 ms
28 days agoHandshake completed106 ms

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