# GolfCore (remote · mcp.golfcore.org)

Scorecards, tee yardages, USGA ratings and green contour maps for 30,000 golf courses worldwide.

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-26

## Components

- remote · `mcp.golfcore.org`: 74/100 (this document), [markdown](https://verifymcp.io/servers/org-golfcore-golfcore/mcp.md), [page](https://verifymcp.io/servers/org-golfcore-golfcore/mcp)

## Channel facts

- Endpoint: `https://mcp.golfcore.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-26.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 556 tokens (~556/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the GolfCore MCP server?

GolfCore is a hosted endpoint at https://mcp.golfcore.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http org-golfcore-golfcore 'https://mcp.golfcore.org/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "org-golfcore-golfcore": {
      "url": "https://mcp.golfcore.org/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-golfcore-golfcore": {
      "type": "http",
      "url": "https://mcp.golfcore.org/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.org-golfcore-golfcore]
url = "https://mcp.golfcore.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-golfcore-golfcore": {
      "type": "remote",
      "url": "https://mcp.golfcore.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-golfcore-golfcore --url 'https://mcp.golfcore.org/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-golfcore-golfcore:
    url: "https://mcp.golfcore.org/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "org-golfcore-golfcore": {
      "Transport": "http",
      "Url": "https://mcp.golfcore.org/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-golfcore-golfcore -t streamable-http -u 'https://mcp.golfcore.org/mcp'
```

### Other

```json
{
  "mcpServers": {
    "org-golfcore-golfcore": {
      "type": "http",
      "url": "https://mcp.golfcore.org/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 74, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (1)

### `search` (~432 tokens)

Search GolfCore

Search everything GolfCore holds for 30,000 golf courses in 153 countries. Ask by course name ('Pebble Beach'), by slug ('pebble-beach'), by place ('golf courses in Fife', 'Monterey'), or about GolfCore itself ('what does a caddie master use GolfCore for'). A course comes back with its address, town, region, country, coordinates, timezone, phone and website; flags for what GolfCore has mapped -- lidar green contours, a traced map of fairways, tees, greens, bunkers and water, a live wind grid, a scorecard, USGA ratings; and, when scope includes scorecards, its full card: par, yardage and stroke index for every hole, and yardage, par, course rating and slope rating for every tee, separately for men and women. Places come back as the town, region or country page that counts and lists every course there. Pages come from GolfCore's own site. Every result carries the url to cite, and a course's page carries the green figures this tool does not: greens mapped, contour count and interval, largest green elevation span, steepest measured slope, and tree canopy.

Input parameters:

- `limit` (integer): Results per scope. Default 5, maximum 20.
- `query` (string, required): What you are looking for, in plain English.
- `scope` (array): Optional. Narrow the search to these scopes: 'slug' treats the query as a GolfCore course slug and returns that exact course, 'courses' matches courses by name and town, 'scorecards' attaches each co…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/org-golfcore-golfcore/mcp#diagnostics

## Score history

- 2026-09-26: 74
- 2026-09-25: 74
- 2026-09-24: 74
- 2026-09-23: 73
- 2026-09-22: 73
- 2026-09-21: 72
- 2026-09-20: 72
- 2026-09-19: 71
- 2026-09-18: 71
- 2026-09-17: 70
- 2026-09-16: 70
- 2026-09-15: 69
- 2026-09-14: 69
- 2026-09-13: 68
- 2026-09-12: 68
- 2026-09-11: 67
- 2026-09-10: 67
- 2026-09-09: 67
- 2026-09-08: 66
- 2026-09-07: 66
- 2026-09-06: 65
- 2026-09-05: 65
- 2026-09-04: 64

## Common questions

### What is the GolfCore MCP server?

GolfCore is an MCP server listed in the public MCP registry as org.golfcore/golfcore. Scorecards, tee yardages, USGA ratings and green contour maps for 30,000 golf courses worldwide. This page covers its hosted endpoint (https://mcp.golfcore.org/mcp).

### Is the GolfCore MCP server safe to use?

GolfCore scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the GolfCore MCP server expose?

GolfCore exposes 1 tool: search. Their descriptions and schemas cost roughly 432 tokens of context every time the server is loaded.

### Does the GolfCore MCP server require authentication?

No. We connected to GolfCore without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the GolfCore MCP server still maintained?

GolfCore is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.golfcore.org/mcp
- Website: https://www.golfcore.org/
- Changelog RSS feed: https://verifymcp.io/servers/org-golfcore-golfcore/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-golfcore-golfcore/mcp.json
- HTML version of this page: https://verifymcp.io/servers/org-golfcore-golfcore/mcp