GolfCore
REMOTE · MCP.GOLFCORE.ORG · SCANNED SEP 26
Scorecards, tee yardages, USGA ratings and green contour maps for 30,000 golf courses worldwide.
Available components
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. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · mcp.golfcore.org
claude mcp add --transport http org-golfcore-golfcore 'https://mcp.golfcore.org/mcp'
{
"mcpServers": {
"org-golfcore-golfcore": {
"url": "https://mcp.golfcore.org/mcp"
}
}
} {
"servers": {
"org-golfcore-golfcore": {
"type": "http",
"url": "https://mcp.golfcore.org/mcp"
}
}
} [mcp_servers.org-golfcore-golfcore] url = "https://mcp.golfcore.org/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"org-golfcore-golfcore": {
"type": "remote",
"url": "https://mcp.golfcore.org/mcp",
"enabled": true
}
}
} openclaw mcp add org-golfcore-golfcore --url 'https://mcp.golfcore.org/mcp' --transport streamable-http
mcp_servers:
org-golfcore-golfcore:
url: "https://mcp.golfcore.org/mcp" {
"McpServers": {
"org-golfcore-golfcore": {
"Transport": "http",
"Url": "https://mcp.golfcore.org/mcp"
}
}
} assistant mcp add org-golfcore-golfcore -t streamable-http -u 'https://mcp.golfcore.org/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +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.
- 22 Sept 26 +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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 26 Sept 2026 · Probed https://mcp.golfcore.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=golfcore.org | CN=WE1,O=Google Trust Services,C=US | 12 Aug 2026 | 10 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 53fd4dcedc62d690e00b3ff140071ca |
| SANs: golfcore.org, mcp.golfcore.org, *.mcp.golfcore.org | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.golfcore.org. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| golfcore.org. | present | 2371 | 13 | Verified |
| mcp.golfcore.org. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.golfcore.org/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.golfcore.org/mcp | HTTPS enforced | 301 | https://mcp.golfcore.org/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
search Search GolfCore ~432
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per scope. Default 5, maximum 20. |
| query | string | yes | 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… |
No output schema declared.
No examples provided.
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.