Remote MCP · Endpoint

Caddence MCP server

No. Caddence answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://caddence.golf/mcp

The last check completed an MCP handshake.

Registry name
golf.caddence/caddence
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
155 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Live UK golf equipment prices: retailer offers, price history and deal ratings in GBP.
Listing
From the official MCP registry (active).
Recent checks of Caddence
CheckedResultHandshake
1 hour agoHandshake completed155 ms
2 days agoHandshake completed371 ms
4 days agoHandshake completed380 ms
5 days agoHandshake completed216 ms
7 days agoHandshake completed385 ms
8 days agoHandshake completed391 ms
9 days agoHandshake completed389 ms
12 days agoHandshake completed191 ms
13 days agoHandshake completed444 ms
15 days agoHandshake completed406 ms
16 days agoHandshake completed491 ms
18 days agoHandshake completed461 ms
19 days agoHandshake completed381 ms
20 days agoHandshake completed394 ms
20 days agoHandshake completed417 ms
21 days agoHandshake completed499 ms
22 days agoHandshake completed481 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 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 Caddence and makes no claim about it beyond what these checks measured.