Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
GolfCore is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
AI caddie and flag distances for Premium golfers, plus course maps and tee-specific scorecards.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http golfcore-mcp https://mcp.golfcore.org/mcp
# 2 — ask your agent for something these tools do
# search, distance_to_flag, ask_caddie and 6 more
GolfCore costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http golfcore-mcp https://mcp.golfcore.org/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search everything GolfCore holds for more than 30,000 golf courses in more than 180 countries and territories. Ask by course name ('Pebble Beach'), by its name in local script ('宮崎カントリークラブ'), by architect ('Donald Ross'), by slug ('pebble-beach'), by place, passing just the place name ('St Andrews', 'Monterey'), or about GolfCore itself ('what does a caddie master use GolfCore for'). A course come
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | What you are looking for, in plain English. May be empty when near is given; with near, it filters courses by name or town. |
| near | object | no | Optional. A point to search around, such as the person's location or their hotel. Courses come back nearest first, each with its distance in miles. |
| radius_miles | number | no | Optional, with near. How far to look, in miles. Default 25, maximum 250. |
| coverage | string | no | Optional. Only courses GolfCore has this for: 'contours' lidar green contour maps, 'traced' a traced course map, 'scorecard' a hole-by-hole card, 'rated' USGA course and slope ratings. |
| scope | array | no | 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 cou |
| limit | integer | no | Results per scope. Default 5, maximum 20. |
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 p
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lat | number | no | Optional. The golfer's precise latitude, only when your device gives you their GPS position. Never ask the golfer for coordinates: leave lat and lng out and GolfCore uses the position from the GolfCor |
| lng | number | no | Optional. The golfer's precise longitude, with lat. |
| course | string | no | Optional. The course slug, when known. Otherwise the course is found from the position. |
| hole | string | no | Optional. The hole number the golfer says they are on. Otherwise the hole is chosen from the position. |
| accuracy_m | number | no | Optional. The location's horizontal accuracy in meters, when the device reports 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 terrai
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lat | number | no | Optional. The golfer's precise latitude, only when your device gives you their GPS position. Never ask the golfer for coordinates: leave lat and lng out and GolfCore uses the position from the GolfCor |
| lng | number | no | Optional. The golfer's precise longitude, with lat. |
| course | string | no | Optional. The course slug, when known. Otherwise the course is found from the position. |
| hole | string | no | Optional. The hole number the golfer says they are on. Otherwise the hole is chosen from the position. |
| accuracy_m | number | no | Optional. The location's horizontal accuracy in meters, when the device reports it. |
| question | string | yes | The golfer's question, in their words. |
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 subscribe
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan | string | yes | The plan the golfer chose. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account_id | integer | no | Optional. One account's detail; omit to list all. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account_id | integer | yes | From api_account. |
| name | string | yes | What the key is for, such as the server or app. |
| expiry | string | no | Default 90_days. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account_id | integer | yes | From api_account. |
| key_id | integer | yes | From api_account's keys. |
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. As
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account_id | integer | yes | From api_account. |
| plan | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account_id | integer | yes | From api_account. |
| units | integer/null | yes | Monthly request cap, or null for no cap. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install GolfCore or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| distance_to_flag | no tags | |
| ask_caddie | state-write | state-write: declares readOnlyHint: false |
| subscribe_premium | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| api_account | no tags | |
| api_create_key | state-write | state-write: declares readOnlyHint: false |
| api_revoke_key | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| api_upgrade | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| api_budget | state-write | state-write: declares readOnlyHint: false |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.4.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish GolfCore can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.