Skip to content

GolfCore MCP server

org.golfcore/golfcoregolfcore.orgstreamable-httpv1.4.0Scanned

AI caddie and flag distances for Premium golfers, plus course maps and tee-specific scorecards.

9 tools: 1 can delete or cancel things, 7 change things and 1 only read.

Tools: 1 delete, 0 irreversible, 7 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the GolfCore MCP server can do

The GolfCore MCP server is published by golfcore.org, a domain the MCP Registry verified. It has 9 tools. It can delete or cancel things (1 tool: api_revoke_key) and create or change data (7 tools: distance_to_flag, ask_caddie, subscribe_premium, api_account and 3 more). 1 tool only reads.

3 tools bring in text other people can write (search, subscribe_premium and api_upgrade).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 19, 2026, version 1.4.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Deletes or cancels 1Claude Code: deny
  • api_revoke_keyRevoke one of the signed-in person's GolfCore API keys.No findings

    Why it is in this group

    • The name "api_revoke_key" says "revoke": a word for removing or ending something.
    • The description says "cannot be restored".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Revoke one of the signed-in person's GolfCore API keys. Requests with it are refused within about a minute, and it cannot be restored. Confirm the key's name and prefix with the person before calling.

    Annotations the server declares

    • title: Revoke a GolfCore API key
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
Changes things 7Claude Code: ask
  • api_accountFor a developer using the GolfCore Course Data API: list the API accounts the signed-in person can see, or read one with its plan, this month's usage, monthly cap if one is set, an…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    For a developer using the GolfCore Course Data API: list the API accounts the signed-in person can see, or read one with its plan, this month's usage, monthly cap if one is set, and keys (prefixes only, never secrets). Use it before the other api_ tools to get account_id and key_id. Plans: free, 500 requests a month at 10 a minute; basic, $10 a month for 10,000 at 60 a minute, then $2.00 per 1,000; business, $50 a month for 100,000 at 300 a minute, then $1.00 per 1,000. Paid plans have no monthly cap unless the person sets one. If the person has no account, they create one at https://platform.golfcore.app.

    Annotations the server declares

    • title: Read GolfCore API account
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • api_budgetStarter and Pro have no monthly cap by default: requests past the included amount are billed at the plan's overage rate without limit.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Starter and Pro have no monthly cap by default: requests past the included amount are billed at the plan's overage rate without limit. This tool sets an optional cap, after which requests are refused until the month resets, or removes it when units is null. A cap starts at the plan's included requests (read them from api_account). Confirm the number and what it could cost with the person first.

    Annotations the server declares

    • title: Set or remove the GolfCore API monthly cap
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • api_create_keyCreate a GolfCore Course Data API key for the signed-in person's account.No findings

    Why it is in this group

    • The name "api_create_key" says "create": a word for a change.
    Description, as the server wrote it
    Create a GolfCore Course Data API key for the signed-in person's account. Returns the secret once; hand it to the person to store in their server's configuration, and never put it in chat logs, code, a mobile app or browser code. Confirm the name with the person first.

    Annotations the server declares

    • title: Create a GolfCore API key
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • api_upgradeStart an upgrade of the signed-in person's GolfCore API account to basic ($10 a month for 10,000 requests, then $2.00 per 1,000) or business ($50 a month for 100,000, then $1.00 pe…Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "start": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Start an upgrade of the signed-in person's GolfCore API account to basic ($10 a month for 10,000 requests, then $2.00 per 1,000) or business ($50 a month for 100,000, then $1.00 per 1,000). Returns a Stripe checkout URL for the person to review and pay; this tool does not charge them. If the account already has a paid plan it returns the billing page, where the person switches plans themselves. Ask which plan they want first.

    Annotations the server declares

    • title: Upgrade a GolfCore API plan
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • ask_caddieAsk GolfCore's caddie a question about the shot the golfer is standing over, such as which club to hit or where to aim.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Ask GolfCore's caddie a question about the shot the golfer is standing over, such as which club to hit or where to aim. Pass the question in their words, and lat and lng only if your device gives you their GPS position; otherwise GolfCore uses the position from the GolfCore app on their phone. The caddie reads the distance to the flag, the hazards and trees on the line, wind modeled for the terrain, the elevation change, and the golfer's own handicap and club distances from their GolfCore account, and answers with a club and a line; the golfer signs in to GolfCore the first time. It needs GolfCore Premium; without it the result lists the plans, and subscribe_premium starts one.

    Annotations the server declares

    • title: Ask the GolfCore caddie
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • distance_to_flagHow far the golfer is from the flag, from where they are standing: 'how far is that flag', 'what's the yardage'.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    How far the golfer is from the flag, from where they are standing: 'how far is that flag', 'what's the yardage'. Returns the course, the hole, its par and stroke index, and yards to the flag (today's pin as the club set it) and to the middle of the green. Pass lat and lng only if your device gives you the golfer's GPS position; otherwise call it with no arguments, and GolfCore reads the golfer's position from the GolfCore app on their phone. It is part of GolfCore Premium: the golfer signs in to GolfCore the first time, and without Premium the result lists the plans for subscribe_premium. position_age_s says how old that position is. When hole_inferred is true the hole was chosen from the position, so say which hole you assumed.

    Annotations the server declares

    • title: Distance to the flag
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • subscribe_premiumCreate a GolfCore Premium checkout link for the signed-in golfer.Reads text others writeNo findings

    Why it is in this group

    • The name "subscribe_premium" says "subscribe": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Create a GolfCore Premium checkout link for the signed-in golfer. Premium adds the caddie in this connector and the GolfCore app, plus green contour maps, live wind and offline course packs. Plans: day_pass, $3 for 24 hours of Premium, one charge and no subscription, the popular choice for a golfer on the course today; plus_monthly, $10 a month; and plus_yearly, $100 a year. A first-time subscriber pays half for the first month or first year. Ask the golfer which plan they want before calling. Returns a secure Stripe checkout URL and the current plan terms. Give the link to the golfer to review and pay; this tool does not charge them or activate Premium.

    Annotations the server declares

    • title: Subscribe to GolfCore Premium
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 1Show 1 read-only tool

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:17 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
8
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.golfcore.org/.well-known/oauth-protected-resource/mcp
Authorization servers
https://www.golfcore.app
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 8 tools that change things (1 destructive, 7 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.golfcore.org/mcp: tools/list returned 9 tools to an anonymous client, including api_revoke_key (destructive), distance_to_flag (write), ask_caddie (write), subscribe_premium (write), api_account (write) and 3 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.4.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__golfcore__search"
    ],
    "ask": [
      "mcp__golfcore__distance_to_flag",
      "mcp__golfcore__ask_caddie",
      "mcp__golfcore__subscribe_premium",
      "mcp__golfcore__api_account",
      "mcp__golfcore__api_create_key",
      "mcp__golfcore__api_upgrade",
      "mcp__golfcore__api_budget"
    ],
    "deny": [
      "mcp__golfcore__api_revoke_key"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as golfcore. Review it before you use it.

Capability tags behind 3 rules
  • mcp__golfcore__search untrusted-input
  • mcp__golfcore__subscribe_premium untrusted-input
  • mcp__golfcore__api_upgrade untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/org.golfcore/golfcore/verify?hash=0e26727a069266558c0884659ae03aa0391ec4f47cf657693b0d98bce10f6ccf" | jq -e '.changed == false'

Pinned hash 0e26727a0692, from Nov 19, 2026, 00:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/org.golfcore/golfcore/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for org.golfcore/golfcore
[![Anlyon Radar](https://radar.anlyon.com/badge/org.golfcore/golfcore.svg)](https://radar.anlyon.com/servers/org.golfcore/golfcore)

Source: MCP Registry. Synced Oct 21, 2026, 18:54 UTC.

GolfCore MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the GolfCore MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 8 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the GolfCore MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: api_revoke_key.

Can the GolfCore MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the GolfCore MCP server have?

9 tools: 1 destructive, 7 write, 1 read. api_revoke_key, distance_to_flag, ask_caddie, subscribe_premium, api_account, api_create_key, api_upgrade, api_budget and 1 more.

Does the GolfCore MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the GolfCore MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the GolfCore MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.