asap golf
REMOTE · ASAP.GOLF
Find public tee times, create friend polls and prepare tee-time alerts across US golf regions.
Available components
Last scanned (1 day ago)
Scores higher than 59% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Entertainment and Games
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 653 tokens (~108/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 38% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 0
- Tool “search_tee_times” rewrote its description, which is the text the model reads security
- “search_tee_times” reworded the description of “refresh” cosmetic
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 13 Nov 26 69
First indexed and scored.
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 21 Nov 2026 · Probed https://asap.golf/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=asap.golf | CN=YR2,O=Let's Encrypt,C=US | 20 Oct 2026 | 18 Jan 2027 | RSA 2048 | SHA256-RSA | 5946a0fdadf535400ed43b6b77e5bbf4cc1 |
| SANs: asap.golf | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of asap.golf. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| golf. | DS published | 62921 | 8 | Verified |
| asap.golf. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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=63072000 |
| content-security-policy | base-uri 'self'; object-src 'none'; form-action 'self'; frame-ancestors 'self' https://chatgpt.com https://*.chatgpt.com https://*.chatgpt.site |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://asap.golf/api/mcp | Verified | 200 | |
| http (plaintext) | http://asap.golf/api/mcp | HTTPS enforced | 308 | https://asap.golf/api/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 →
create_tee_time_poll ~52
Create a shareable tee-time poll from up to eight search options. Availability is checked again; this does not book a tee time. Friends vote at the returned link.
| Name | Type | Req | Description |
|---|---|---|---|
| options | array | yes | – |
No output schema declared.
No examples provided.
get_tee_time_poll ~58
Get poll options and aggregate vote counts from an asap.golf share link or poll token. Individual ballots are not returned.
| Name | Type | Req | Description |
|---|---|---|---|
| poll | string | yes | The complete https://asap.golf/p/… link or its poll token. |
No output schema declared.
No examples provided.
list_courses ~50
List public courses in a region. Use offset to page through results.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| query | string | – | – |
| region | string | yes | – |
No output schema declared.
No examples provided.
list_regions ~17
List supported golf regions and their time zones.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
prepare_alert ~233
Prepare a link to review and save a tee-time alert on asap.golf. This does not create or activate an alert. The golfer must open the link, sign in, review and save it, and connect a notification method to receive alerts. Use course IDs returned by search.
| Name | Type | Req | Description |
|---|---|---|---|
| courseIds | array | yes | Connected course IDs in the selected region. |
| days | integer | – | Number of dates for a one-time alert; default 1. |
| expiresDays | integer | – | – |
| from | integer | yes | Earliest local tee time, minutes after midnight. |
| holes | integer | – | 0 means any round length. |
| maxPrice | number | – | – |
| name | string | – | – |
| players | integer | yes | – |
| recurrence | string | – | – |
| region | string | yes | Supported region ID returned by search. |
| startDate | string | yes | First date in YYYY-MM-DD, in the region’s local time. |
| to | integer | yes | Latest local tee time, minutes after midnight. |
| weekdays | array | – | Days to repeat: Sunday is 0. Required for weekly alerts. |
No output schema declared.
No examples provided.
search_tee_times ~197
Search tee times for up to 50 selected courses on one date. Reuse valid cache and automatically pull missing or expired inventory in bounded batches. Read coverage and deferredCourseIds: unknown or deferred coverage is not proof of no availability. When continuation is present, wait until notBefore, call its tool with its arguments, and merge results by course while retaining earlier successful options.
| Name | Type | Req | Description |
|---|---|---|---|
| courseIds | array | yes | – |
| date | string | yes | Local date in YYYY-MM-DD format, within the next 31 days |
| fromMinute | integer | – | – |
| holes | integer | – | – |
| limit | integer | – | – |
| maxPrice | number | – | – |
| players | integer | yes | – |
| refresh | boolean | – | Compatibility option; missing or expired inventory is pulled automatically regardless of this value. Valid cache and provider cooldowns are always respected. |
| region | string | yes | – |
| toMinute | integer | – | – |
No output schema declared.
No examples provided.
How do I install the asap golf MCP server?
asap golf is a hosted endpoint at https://asap.golf/api/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 · asap.golf
claude mcp add --transport http golf-asap-asap-golf 'https://asap.golf/api/mcp'
What is the asap golf MCP server?
asap golf is an MCP server listed in the public MCP registry as golf.asap/asap-golf. Find public tee times, create friend polls and prepare tee-time alerts across US golf regions. This page covers its hosted endpoint (https://asap.golf/api/mcp).
Is the asap golf MCP server safe to use?
asap golf scores 73 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 asap golf MCP server expose?
asap golf exposes 6 tools: list_regions, list_courses, search_tee_times, prepare_alert, create_tee_time_poll, get_tee_time_poll. Their descriptions and schemas cost roughly 607 tokens of context every time the server is loaded.
Does the asap golf MCP server require authentication?
No. We connected to asap golf without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the asap golf MCP server still maintained?
asap golf is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the asap golf MCP server?
VerifyMCP ran 13 checks on asap golf, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.