Remote MCP · Endpoint

Duffer Golf MCP server

No. Duffer Golf answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://duffergolf.net/mcp

The last check completed an MCP handshake.

Registry name
net.duffergolf/duffer-golf
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
81 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Read-only Duffer Golf facts: models and prices, room fit, FAQ, dealers and contact.
Website
https://duffergolf.net/
Listing
From the official MCP registry (active).
Recent checks of Duffer Golf
CheckedResultHandshake
1 hour agoHandshake completed81 ms
1 day agoHandshake completed78 ms
4 days agoHandshake completed114 ms
7 days agoHandshake completed73 ms
9 days agoHandshake completed151 ms
11 days agoHandshake completed127 ms
13 days agoHandshake completed217 ms
15 days agoHandshake completed103 ms
17 days agoHandshake completed107 ms
19 days agoHandshake completed49 ms
21 days agoHandshake completed60 ms
22 days agoHandshake completed90 ms
23 days agoHandshake completed60 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Duffer Golf and makes no claim about it beyond what these checks measured.