# asap golf (remote · asap.golf)

Find public tee times, create friend polls and prepare tee-time alerts across US golf regions.

- Trust score: 74/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-22

## Components

- remote · `asap.golf`: 74/100 (this document), [markdown](https://verifymcp.io/servers/golf-asap-asap-golf/api-mcp.md), [page](https://verifymcp.io/servers/golf-asap-asap-golf/api-mcp)

## Channel facts

- Endpoint: `https://asap.golf/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-22.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 653 tokens (~108/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 79/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 38% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http golf-asap-asap-golf 'https://asap.golf/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "golf-asap-asap-golf": {
      "url": "https://asap.golf/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "golf-asap-asap-golf": {
      "type": "http",
      "url": "https://asap.golf/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.golf-asap-asap-golf]
url = "https://asap.golf/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "golf-asap-asap-golf": {
      "type": "remote",
      "url": "https://asap.golf/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add golf-asap-asap-golf --url 'https://asap.golf/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  golf-asap-asap-golf:
    url: "https://asap.golf/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "golf-asap-asap-golf": {
      "Transport": "http",
      "Url": "https://asap.golf/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add golf-asap-asap-golf -t streamable-http -u 'https://asap.golf/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "golf-asap-asap-golf": {
      "type": "http",
      "url": "https://asap.golf/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-22 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-20 (score 73, +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.

### 2026-11-19 (score 72, 0)

- [security] Tool “search_tee_times” rewrote its description, which is the text the model reads
- [cosmetic] “search_tee_times” reworded the description of “refresh”

### 2026-11-18 (score 72, +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.

### 2026-11-16 (score 71, +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.

### 2026-11-14 (score 70, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-13 (score 69)

First indexed and scored.

## MCP tools (6)

### `list_regions` (~17 tokens)

List supported golf regions and their time zones.

### `list_courses` (~50 tokens)

List public courses in a region. Use offset to page through results.

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `query` (string)
- `region` (string, required)

### `search_tee_times` (~197 tokens)

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.

Input parameters:

- `courseIds` (array, required)
- `date` (string, required): Local date in YYYY-MM-DD format, within the next 31 days
- `fromMinute` (integer)
- `holes` (integer)
- `limit` (integer)
- `maxPrice` (number)
- `players` (integer, required)
- `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, required)
- `toMinute` (integer)

### `prepare_alert` (~233 tokens)

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.

Input parameters:

- `courseIds` (array, required): Connected course IDs in the selected region.
- `days` (integer): Number of dates for a one-time alert; default 1.
- `expiresDays` (integer)
- `from` (integer, required): Earliest local tee time, minutes after midnight.
- `holes` (integer): 0 means any round length.
- `maxPrice` (number)
- `name` (string)
- `players` (integer, required)
- `recurrence` (string)
- `region` (string, required): Supported region ID returned by search.
- `startDate` (string, required): First date in YYYY-MM-DD, in the region’s local time.
- `to` (integer, required): Latest local tee time, minutes after midnight.
- `weekdays` (array): Days to repeat: Sunday is 0. Required for weekly alerts.

### `create_tee_time_poll` (~52 tokens)

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.

Input parameters:

- `options` (array, required)

### `get_tee_time_poll` (~58 tokens)

Get poll options and aggregate vote counts from an asap.golf share link or poll token. Individual ballots are not returned.

Input parameters:

- `poll` (string, required): The complete https://asap.golf/p/… link or its poll token.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/golf-asap-asap-golf/api-mcp#diagnostics

## Score history

- 2026-11-22: 74
- 2026-11-21: 73
- 2026-11-20: 73
- 2026-11-19: 72
- 2026-11-18: 72
- 2026-11-17: 71
- 2026-11-16: 71
- 2026-11-15: 70
- 2026-11-14: 70
- 2026-11-13: 69

## Common questions

### 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 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 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 22 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.

## Links

- Remote endpoint: https://asap.golf/api/mcp
- Website: https://asap.golf/connect
- Changelog RSS feed: https://verifymcp.io/servers/golf-asap-asap-golf/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/golf-asap-asap-golf/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/golf-asap-asap-golf/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/golf-asap-asap-golf/api-mcp
