GolfCore
Registry code: 3d5c548c06378973
GolfCore covers more than 30,000 golf courses in more than 180 countries and territories. On the course, when the golfer asks how far the flag is, call distance_to_flag; when they want advice on a shot, call ask_caddie with their question. Pass lat and lng only if your device gives you their GPS position, and never ask the golfer for coordinates: without them GolfCore reads the golfer's position from the GolfCore app on their phone. Both are GolfCore Premium: the golfer signs in to GolfCore once, and without Premium the result lists the plans for subscribe_premium. For everything else there…
- endpoint
- https://mcp.golfcore.org/mcp
- door code
- 661b8792e3f31f99
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is GolfCore live?
- Yes — it answered the hub's last check (checked 58m ago). It answered 99% of checks over the last 30 days.
- Is GolfCore free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does GolfCore have?
- 9 tools: search, api_create_key, ask_caddie, subscribe_premium, api_account, api_revoke_key, api_upgrade, api_budget, ….
- Is GolfCore safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.3%· all time 99.2%
last good check
of 9 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- topic
- games & entertainment sports
- used for
- get distance to the golf flag
- ask a caddie for shot advice
- search golf course data
- manage golf data api keys
- takes → gives
- text, data → data, text
- tools
- 4 reads4 changes data1 moves money
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
api_create_key changes data auth-required never probed
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.
{ "type": "object", "required": [ "account_id", "name" ], "properties": { "name": { "type": "string", "description": "What the key is for, such as the server or app." }, "expiry": { "enum": [ "30_days", "90_days", "1_year", "never" ], "type": "string", "description": "Default 90_days." }, "account_id": { "type": "integer", "description": "From api_account." } }, "additionalProperties": false }arguments 28 linesask_caddie reads auth-required never probed
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.
{ "type": "object", "required": [ "question" ], "properties": { "lat": { "type": "number", "maximum": 90, "minimum": -90, "description": "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 GolfCore app on their phone." }, "lng": { "type": "number", "maximum": 180, "minimum": -180, "description": "Optional. The golfer's precise longitude, with lat." }, "hole": { "type": "string", "description": "Optional. The hole number the golfer says they are on. Otherwise the hole is chosen from the position." }, "course": { "type": "string", "description": "Optional. The course slug, when known. Otherwise the course is found from the position." }, "question": { "type": "string", "description": "The golfer's question, in their words." }, "accuracy_m": { "type": "number", "description": "Optional. The location's horizontal accuracy in meters, when the device reports it." } }, "additionalProperties": false }arguments 37 linessubscribe_premium changes data auth-required never probed
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.
{ "type": "object", "required": [ "plan" ], "properties": { "plan": { "enum": [ "day_pass", "plus_monthly", "plus_yearly" ], "type": "string", "description": "The plan the golfer chose." } }, "additionalProperties": false }arguments 18 linesapi_account reads auth-required 15h ago
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.
{ "type": "object", "properties": { "account_id": { "type": "integer", "description": "Optional. One account's detail; omit to list all." } }, "additionalProperties": false }arguments 10 linesapi_revoke_key changes data auth-required never probed
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.
{ "type": "object", "required": [ "account_id", "key_id" ], "properties": { "key_id": { "type": "integer", "description": "From api_account's keys." }, "account_id": { "type": "integer", "description": "From api_account." } }, "additionalProperties": false }arguments 18 linesapi_upgrade moves money auth-required never probed
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.
{ "type": "object", "required": [ "account_id", "plan" ], "properties": { "plan": { "enum": [ "basic", "business" ], "type": "string" }, "account_id": { "type": "integer", "description": "From api_account." } }, "additionalProperties": false }arguments 21 linesapi_budget changes data auth-required never probed
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.
{ "type": "object", "required": [ "account_id", "units" ], "properties": { "units": { "type": [ "integer", "null" ], "minimum": 1, "description": "Monthly request cap, or null for no cap." }, "account_id": { "type": "integer", "description": "From api_account." } }, "additionalProperties": false }arguments 22 linesdistance_to_flag reads auth-required 8h ago
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.
{ "type": "object", "properties": { "lat": { "type": "number", "maximum": 90, "minimum": -90, "description": "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 GolfCore app on their phone." }, "lng": { "type": "number", "maximum": 180, "minimum": -180, "description": "Optional. The golfer's precise longitude, with lat." }, "hole": { "type": "string", "description": "Optional. The hole number the golfer says they are on. Otherwise the hole is chosen from the position." }, "course": { "type": "string", "description": "Optional. The course slug, when known. Otherwise the course is found from the position." }, "accuracy_m": { "type": "number", "description": "Optional. The location's horizontal accuracy in meters, when the device reports it." } }, "additionalProperties": false }arguments 30 linessearch reads unknown 8h ago
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 comes back with its address, town, region, country, coordinates, timezone, phone and website, its architect and the year it opened where known, and its name in Japanese or Korean script where that differs; 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. For 'courses near me' or 'near this hotel', pass near with the person's coordinates: courses come back nearest first with their distance in miles, and query may be left empty. Each course also carries app_url, the link that opens that course's map in the GolfCore app, in a browser or on a phone, with no account needed to start; append &hole=N to open on a given hole.
{ "type": "object", "properties": { "near": { "type": "object", "required": [ "lat", "lng" ], "properties": { "lat": { "type": "number", "maximum": 90, "minimum": -90 }, "lng": { "type": "number", "maximum": 180, "minimum": -180 } }, "description": "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.", "additionalProperties": false }, "limit": { "type": "integer", "description": "Results per scope. Default 5, maximum 20." }, "query": { "type": "string", "description": "What you are looking for, in plain English. May be empty when near is given; with near, it filters courses by name or town." }, "scope": { "type": "array", "items": { "enum": [ "product", "country", "region", "city", "courses", "scorecards", "slug" ], "type": "string" }, "description": "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 course's per-hole card and tee ratings to it, 'city', 'region' and 'country' return pages that count and list every course in a place, 'product' returns GolfCore's own pages. Omit to search all of them. Combine freely, e.g. [\"slug\",\"scorecards\"] for one exact card, or [\"city\",\"courses\"]. Leave 'scorecards' out when you only need to know which courses exist; the cards are large." }, "coverage": { "enum": [ "contours", "traced", "scorecard", "rated" ], "type": "string", "description": "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." }, "radius_miles": { "type": "number", "description": "Optional, with near. How far to look, in miles. Default 25, maximum 250." } }, "additionalProperties": false }arguments 65 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id3d5c548c06378973.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/3d5c548c06378973/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/3d5c548c06378973?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.