Remote MCP · Endpoint
co.loopgolf/tee-times MCP server
Yes, as of 9 hours ago: the check failed for an unclassified reason.
DownLast checked 9 hours ago
Server URL
https://www.loopgolf.co/api/ai/mcp
The last check failed: the check failed for an unclassified reason.
- Registry name
- co.loopgolf/tee-times
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- Not measured yet
- Uptime, last 30 days
- 0.0% from 17 checks
- Described by its publisher as
- Live golf tee time availability across US courses. Search by location, date, players, and price.
- Website
- https://www.loopgolf.co/ai
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 9 hours ago | Failed - the check failed for an unclassified reason | — |
| 2 days ago | Failed - the check failed for an unclassified reason | — |
| 4 days ago | Failed - the check failed for an unclassified reason | — |
| 5 days ago | Failed - the check failed for an unclassified reason | — |
| 7 days ago | Failed - the check failed for an unclassified reason | — |
| 8 days ago | Failed - the check failed for an unclassified reason | — |
| 9 days ago | Failed - the check failed for an unclassified reason | — |
| 12 days ago | Failed - the check failed for an unclassified reason | — |
| 14 days ago | Failed - the check failed for an unclassified reason | — |
| 15 days ago | Failed - the check failed for an unclassified reason | — |
| 16 days ago | Failed - the check failed for an unclassified reason | — |
| 18 days ago | Failed - the check failed for an unclassified reason | — |
| 19 days ago | Failed - the check failed for an unclassified reason | — |
| 19 days ago | Failed - the check failed for an unclassified reason | — |
| 20 days ago | Failed - the check failed for an unclassified reason | — |
| 21 days ago | Failed - the check failed for an unclassified reason | — |
| 23 days ago | Failed - the check failed for an unclassified reason | — |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 0 responding of 17.
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 co.loopgolf/tee-times and makes no claim about it beyond what these checks measured.