# io.usefulapi/acuity-scheduling (remote · acuity-scheduling.usefulapi.io)

Read appointments, types, calendars and availability; create, cancel or reschedule bookings.

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

## Components

- remote · `acuity-scheduling.usefulapi.io`: 74/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-acuity-scheduling/acuity-scheduling.md), [page](https://verifymcp.io/servers/io-usefulapi-acuity-scheduling/acuity-scheduling)

## Channel facts

- Endpoint: `https://acuity-scheduling.usefulapi.io/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-08-03.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1627 tokens (~90/item across 18 items; 18 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http io-usefulapi-acuity-scheduling https://acuity-scheduling.usefulapi.io/mcp
```

### Codex

```toml
[mcp_servers.io-usefulapi-acuity-scheduling]
url = "https://acuity-scheduling.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-acuity-scheduling": {
      "type": "remote",
      "url": "https://acuity-scheduling.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-acuity-scheduling --url https://acuity-scheduling.usefulapi.io/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-acuity-scheduling:
    url: "https://acuity-scheduling.usefulapi.io/mcp"
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-acuity-scheduling": {
      "type": "http",
      "url": "https://acuity-scheduling.usefulapi.io/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-08-02 (score 74, +1)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.20 → unverified
- [security regression] Authorization: pass → unverified
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional] First check of Schema quality: unverified

### 2026-07-31 (score 73, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 70, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 72, +1)

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

### 2026-07-27 (score 71, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 68)

First indexed and scored.

## MCP tools (18)

### `acuity_list_appointments` (~186 tokens)

List appointments

List appointments scheduled on the account, with optional filters. Acuity REST: GET /appointments.

Input parameters:

- `appointmentTypeID` (integer): Filter to a specific appointment type id.
- `calendarID` (integer): Filter to a specific calendar id.
- `canceled` (boolean): If true, return canceled appointments (default false).
- `direction` (string): Sort order by datetime. ASC (default) or DESC.
- `email` (string): Filter by client email.
- `firstName` (string): Filter by client first name.
- `lastName` (string): Filter by client last name.
- `max` (integer): Max appointments to return.
- `maxDate` (string): Only appointments on/before this date (YYYY-MM-DD or ISO datetime).
- `minDate` (string): Only appointments on/after this date (YYYY-MM-DD or ISO datetime).

### `acuity_get_appointment` (~38 tokens)

Get appointment

Get a single appointment by its id. Acuity REST: GET /appointments/{id}.

Input parameters:

- `id` (integer, required): Appointment id.

### `acuity_list_appointment_types` (~57 tokens)

List appointment types

List the account's appointment types (services and classes), including price, duration and calendars. Acuity REST: GET /appointment-types.

Input parameters:

- `includeDeleted` (boolean): If true, also include deleted/inactive appointment types.

### `acuity_list_calendars` (~36 tokens)

List calendars

List the account's calendars (staff/resources appointments can be booked on). Acuity REST: GET /calendars.

### `acuity_availability_dates` (~113 tokens)

Get available dates

List dates in a month that have availability for an appointment type. Acuity REST: GET /availability/dates.

Input parameters:

- `appointmentTypeID` (integer, required): Appointment type id to check availability for (required).
- `calendarID` (integer): Restrict to a specific calendar id.
- `month` (string, required): Month to check, formatted YYYY-MM, e.g. '2026-08'.
- `timezone` (string): IANA timezone for the returned dates, e.g. 'America/New_York'.

### `acuity_availability_times` (~116 tokens)

Get available times

List available time slots on a given date for an appointment type. Acuity REST: GET /availability/times.

Input parameters:

- `appointmentTypeID` (integer, required): Appointment type id to check availability for (required).
- `calendarID` (integer): Restrict to a specific calendar id.
- `date` (string, required): Date to check, formatted YYYY-MM-DD, e.g. '2026-08-15'.
- `timezone` (string): IANA timezone for the returned times, e.g. 'America/New_York'.

### `acuity_availability_classes` (~115 tokens)

Get available classes

List group class time slots (for class-type appointment types) in a month. Acuity REST: GET /availability/classes.

Input parameters:

- `appointmentTypeID` (integer, required): Class appointment type id (required).
- `includeUnavailable` (boolean): If true, also include full/unavailable class times.
- `month` (string, required): Month to check, formatted YYYY-MM, e.g. '2026-08'.
- `timezone` (string): IANA timezone for the returned times, e.g. 'America/New_York'.

### `acuity_list_clients` (~55 tokens)

List clients

List clients on the account, optionally filtered by a search string (name/email/phone). Acuity REST: GET /clients.

Input parameters:

- `search` (string): Optional search string to match client name, email, or phone.

### `acuity_list_forms` (~29 tokens)

List intake forms

List the account's custom intake forms and their fields. Acuity REST: GET /forms.

### `acuity_list_products` (~31 tokens)

List products

List the account's products / packages / gift certificates for sale. Acuity REST: GET /products.

### `acuity_list_orders` (~54 tokens)

List orders

List store orders (product / package / gift-certificate purchases). Acuity REST: GET /orders.

Input parameters:

- `email` (string): Filter orders by buyer email.
- `max` (integer): Max orders to return.

### `acuity_list_blocks` (~102 tokens)

List blocked-off times

List blocked-off (unavailable) time ranges on the account's calendars. Acuity REST: GET /blocks.

Input parameters:

- `calendarID` (integer): Filter to a specific calendar id.
- `max` (integer): Max blocks to return.
- `maxDate` (string): Only blocks on/before this date (YYYY-MM-DD or ISO datetime).
- `minDate` (string): Only blocks on/after this date (YYYY-MM-DD or ISO datetime).

### `acuity_list_labels` (~31 tokens)

List labels

List the appointment labels (colored tags) defined on the account. Acuity REST: GET /labels.

### `acuity_get_me` (~37 tokens)

Get account info

Get the authenticated Acuity account's profile (name, email, timezone, plan, currency). Acuity REST: GET /me.

### `acuity_create_appointment` (~265 tokens)

Create appointment

CREATES a new appointment (books a client into a time slot). This MODIFIES the calendar and, unless suppressed, may send confirmation emails. Acuity REST: POST /appointments.

Input parameters:

- `admin` (boolean): If true, book as admin — bypasses availability checks and required-form enforcement. Default false.
- `appointmentTypeID` (integer, required): Appointment type id to book (required).
- `calendarID` (integer): Calendar id to book on (defaults to an available one).
- `datetime` (string, required): Start time in ISO 8601 with offset, e.g. '2026-08-15T14:00:00-0400' (required).
- `email` (string, required): Client email (required).
- `fields` (array): Intake form field answers, each { id, value }.
- `firstName` (string, required): Client first name (required).
- `lastName` (string, required): Client last name (required).
- `noEmail` (boolean): If true, suppress client/owner confirmation emails.
- `notes` (string): Notes to attach to the appointment.
- `phone` (string): Client phone number.
- `timezone` (string): IANA timezone for the datetime, e.g. 'America/New_York'.

### `acuity_cancel_appointment` (~105 tokens)

Cancel appointment

CANCELS an existing appointment. This MODIFIES the calendar and, unless suppressed, may send cancellation emails. Acuity REST: PUT /appointments/{id}/cancel.

Input parameters:

- `admin` (boolean): If true, cancel as admin (bypasses client cancellation restrictions).
- `cancelNote` (string): Optional note explaining the cancellation.
- `id` (integer, required): Appointment id to cancel (required).
- `noEmail` (boolean): If true, suppress cancellation emails.

### `acuity_reschedule_appointment` (~162 tokens)

Reschedule appointment

RESCHEDULES an existing appointment to a new time (and optionally a new calendar). This MODIFIES the calendar and, unless suppressed, may send update emails. Acuity REST: PUT /appointments/{id}/reschedule.

Input parameters:

- `admin` (boolean): If true, reschedule as admin (bypasses availability checks).
- `calendarID` (integer): Move the appointment to this calendar id.
- `datetime` (string, required): New start time in ISO 8601 with offset, e.g. '2026-08-16T10:00:00-0400' (required).
- `id` (integer, required): Appointment id to reschedule (required).
- `noEmail` (boolean): If true, suppress reschedule emails.

### `acuity_create_client` (~95 tokens)

Create client

CREATES a new client record in the account's client list. This ADDS data to the account. Acuity REST: POST /clients.

Input parameters:

- `email` (string): Client email.
- `firstName` (string, required): Client first name (required).
- `lastName` (string, required): Client last name (required).
- `notes` (string): Notes about the client.
- `phone` (string): Client phone number.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-acuity-scheduling/acuity-scheduling#diagnostics

## Score history

- 2026-08-03: 74
- 2026-08-02: 74
- 2026-08-01: 73
- 2026-07-31: 73
- 2026-07-30: 70
- 2026-07-29: 72
- 2026-07-28: 72
- 2026-07-27: 71
- 2026-07-26: 68

## Links

- Remote endpoint: https://acuity-scheduling.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-acuity-scheduling/acuity-scheduling/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-acuity-scheduling/acuity-scheduling/changelog.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-acuity-scheduling/acuity-scheduling