ELDRICK Golf Club Fitting MCP server
online · 100% uptimeby api.eldrick.com·
com.eldrick.api/fitting·v1.16.0Golf club fitting MCP server: fits drivers, woods, hybrids, irons and wedges; scores real clubs.
B77/100grade B
Safety scan
B77/100
not scanned yet
Adoption
New
Little public usage data yet
Reviews
Write oneNobody has reviewed ELDRICK Golf Club Fitting yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
ELDRICK Golf Club Fitting tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How ELDRICK Golf Club Fitting compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 50% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 343 ms
- faster than 43% of 30,031 servers
Release history: 5 versions in the registry since 2026-10-10, latest 2026-10-26, typically one every 3 days.
Install ELDRICK Golf Club Fitting in Claude Code, Cursor or VS Code
claude mcp add --transport http fitting https://api.eldrick.com/mcp
ELDRICK Golf Club Fitting: common questions
- Is ELDRICK Golf Club Fitting MCP server safe?
- Mostly: it is graded B (77/100). Read the ELDRICK Golf Club Fitting safety report
- How do I install ELDRICK Golf Club Fitting?
- It runs remotely at api.eldrick.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does ELDRICK Golf Club Fitting need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is ELDRICK Golf Club Fitting maintained?
- The latest release is v1.16.0.
- Is ELDRICK Golf Club Fitting up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does ELDRICK Golf Club Fitting compare with other MCP servers?
- safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 343 ms (faster than 43% of 30,031 servers). Full comparison.