Acuity Scheduling MCP by usefulapi
REMOTE · ACUITY-SCHEDULING.USEFULAPI.IO
Read appointments, types, calendars and availability; create, cancel or reschedule bookings.
Available components
Last scanned (1 hour ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Productivity and Notes
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 1 Nov 26 −62
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “book_a_client_and_add_them_if_new” functional
- New prompt “find_open_times_for_an_appointment_type” functional
- New prompt “reschedule_or_cancel_an_appointment” functional
- New prompt “review_the_appointments_for_a_day_or_week” functional
- New prompt “see_which_group_classes_have_space” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.32.0 → 1.34.0 functional
- Server version: 1.31.0 → 1.32.0 functional
- Server version: 1.30.1 → 1.31.0 functional
- 30 Oct 26 −1
- Tool “acuity_list_appointments” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Server version: 1.30.0 → 1.30.1 functional
- Server version: 1.29.0 → 1.30.0 functional
- “acuity_list_appointments” added an optional parameter “excludeForms” cosmetic
- “acuity_list_appointments” added an optional parameter “offset” cosmetic
- “acuity_list_appointments” added an optional parameter “view” cosmetic
- “acuity_list_appointments” reworded the description of “direction” cosmetic
- “acuity_list_appointments” reworded the description of “max” cosmetic
- 29 Oct 26 0
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- 26 Oct 26 +1
- Stability: 0.97 → pass security
- 25 Oct 26 −1
- Stability: pass → 0.97 functional
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.0 → 1.21.3 functional
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 5 Nov 2026 · Probed https://acuity-scheduling.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of acuity-scheduling.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://acuity-scheduling.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/acuity-scheduling/ |
| http (plaintext) | http://acuity-scheduling.usefulapi.io/mcp | Inconclusive | 302 | http://acuity-scheduling.usefulapi.io/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 →
acuity_availability_classes Get available classes ~115
List group class time slots (for class-type appointment types) in a month. Acuity REST: GET /availability/classes.
| Name | Type | Req | Description |
|---|---|---|---|
| appointmentTypeID | integer | yes | Class appointment type id (required). |
| includeUnavailable | boolean | – | If true, also include full/unavailable class times. |
| month | string | yes | Month to check, formatted YYYY-MM, e.g. '2026-08'. |
| timezone | string | – | IANA timezone for the returned times, e.g. 'America/New_York'. |
No output schema declared.
No examples provided.
acuity_availability_dates Get available dates ~113
List dates in a month that have availability for an appointment type. Acuity REST: GET /availability/dates.
| Name | Type | Req | Description |
|---|---|---|---|
| appointmentTypeID | integer | yes | Appointment type id to check availability for (required). |
| calendarID | integer | – | Restrict to a specific calendar id. |
| month | string | yes | Month to check, formatted YYYY-MM, e.g. '2026-08'. |
| timezone | string | – | IANA timezone for the returned dates, e.g. 'America/New_York'. |
No output schema declared.
No examples provided.
acuity_availability_times Get available times ~116
List available time slots on a given date for an appointment type. Acuity REST: GET /availability/times.
| Name | Type | Req | Description |
|---|---|---|---|
| appointmentTypeID | integer | yes | Appointment type id to check availability for (required). |
| calendarID | integer | – | Restrict to a specific calendar id. |
| date | string | yes | 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'. |
No output schema declared.
No examples provided.
acuity_cancel_appointment Cancel appointment ~105
CANCELS an existing appointment. This MODIFIES the calendar and, unless suppressed, may send cancellation emails. Acuity REST: PUT /appointments/{id}/cancel.
| Name | Type | Req | Description |
|---|---|---|---|
| admin | boolean | – | If true, cancel as admin (bypasses client cancellation restrictions). |
| cancelNote | string | – | Optional note explaining the cancellation. |
| id | integer | yes | Appointment id to cancel (required). |
| noEmail | boolean | – | If true, suppress cancellation emails. |
No output schema declared.
No examples provided.
acuity_create_appointment Create appointment ~265
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.
| Name | Type | Req | Description |
|---|---|---|---|
| admin | boolean | – | If true, book as admin — bypasses availability checks and required-form enforcement. Default false. |
| appointmentTypeID | integer | yes | Appointment type id to book (required). |
| calendarID | integer | – | Calendar id to book on (defaults to an available one). |
| datetime | string | yes | Start time in ISO 8601 with offset, e.g. '2026-08-15T14:00:00-0400' (required). |
| string | yes | Client email (required). | |
| fields | array | – | Intake form field answers, each { id, value }. |
| firstName | string | yes | Client first name (required). |
| lastName | string | yes | 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'. |
No output schema declared.
No examples provided.
acuity_create_client Create client ~95
CREATES a new client record in the account's client list. This ADDS data to the account. Acuity REST: POST /clients.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Client email. | |
| firstName | string | yes | Client first name (required). |
| lastName | string | yes | Client last name (required). |
| notes | string | – | Notes about the client. |
| phone | string | – | Client phone number. |
No output schema declared.
No examples provided.
acuity_get_appointment Get appointment ~38
Get a single appointment by its id. Acuity REST: GET /appointments/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Appointment id. |
No output schema declared.
No examples provided.
acuity_get_me Get account info ~37
Get the authenticated Acuity account's profile (name, email, timezone, plan, currency). Acuity REST: GET /me.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
acuity_list_appointment_types List appointment types ~57
List the account's appointment types (services and classes), including price, duration and calendars. Acuity REST: GET /appointment-types.
| Name | Type | Req | Description |
|---|---|---|---|
| includeDeleted | boolean | – | If true, also include deleted/inactive appointment types. |
No output schema declared.
No examples provided.
acuity_list_appointments List appointments ~463
List appointments scheduled on the account. For bulk contact/parent lists, use view: contacts to return only id, firstName, lastName, email, phone and datetime, without forms/formsText. Contacts view or an explicit offset returns {appointments, pagination}; follow pagination.nextOffset with identical filters until null. Pages fit below the tool output cap and can contain fewer than max rows. Offsets are connector-managed by fetching a prefix (Acuity has no documented native offset); at 10,000 appointments per filter/date window, narrow minDate/maxDate and restart at 0. Appointments may change between calls; deduplicate by id. Default full view without offset preserves the original array response. Acuity REST: GET /appointments.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. Acuity defaults to DESC; paginated calls use DESC unless specified. |
| string | – | Filter by client email. | |
| excludeForms | boolean | – | Omit forms and formsText, including from full-view results. Automatically true for contacts view. Uses Acuity's excludeForms parameter. |
| firstName | string | – | Filter by client first name. |
| lastName | string | – | Filter by client last name. |
| max | integer | – | Max appointments to return (default 100). Paginated output may return fewer to fit the output cap; follow nextOffset. |
| 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). |
| offset | integer | – | Zero-based connector offset; enables paginated output. Start at 0, then use pagination.nextOffset with the same filters. At 10,000 rows, narrow the date range. |
| view | string | – | full (default): appointment details. contacts: only id, firstName, lastName, email, phone and datetime, in a compact paginated response; excludes intake forms and notes. |
No output schema declared.
No examples provided.
acuity_list_blocks List blocked-off times ~102
List blocked-off (unavailable) time ranges on the account's calendars. Acuity REST: GET /blocks.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
acuity_list_calendars List calendars ~36
List the account's calendars (staff/resources appointments can be booked on). Acuity REST: GET /calendars.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
acuity_list_clients List clients ~55
List clients on the account, optionally filtered by a search string (name/email/phone). Acuity REST: GET /clients.
| Name | Type | Req | Description |
|---|---|---|---|
| search | string | – | Optional search string to match client name, email, or phone. |
No output schema declared.
No examples provided.
acuity_list_forms List intake forms ~29
List the account's custom intake forms and their fields. Acuity REST: GET /forms.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
acuity_list_labels List labels ~31
List the appointment labels (colored tags) defined on the account. Acuity REST: GET /labels.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
acuity_list_orders List orders ~54
List store orders (product / package / gift-certificate purchases). Acuity REST: GET /orders.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Filter orders by buyer email. | |
| max | integer | – | Max orders to return. |
No output schema declared.
No examples provided.
acuity_list_products List products ~31
List the account's products / packages / gift certificates for sale. Acuity REST: GET /products.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
acuity_reschedule_appointment Reschedule appointment ~162
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.
| Name | Type | Req | Description |
|---|---|---|---|
| admin | boolean | – | If true, reschedule as admin (bypasses availability checks). |
| calendarID | integer | – | Move the appointment to this calendar id. |
| datetime | string | yes | New start time in ISO 8601 with offset, e.g. '2026-08-16T10:00:00-0400' (required). |
| id | integer | yes | Appointment id to reschedule (required). |
| noEmail | boolean | – | If true, suppress reschedule emails. |
No output schema declared.
No examples provided.
How do I install the Acuity Scheduling MCP by usefulapi server?
Acuity Scheduling MCP by usefulapi is a hosted endpoint at https://acuity-scheduling.usefulapi.io/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 · acuity-scheduling.usefulapi.io
claude mcp add --transport http io-usefulapi-acuity-scheduling 'https://acuity-scheduling.usefulapi.io/mcp'
What is the Acuity Scheduling MCP by usefulapi server?
Acuity Scheduling MCP by usefulapi is listed in the public MCP registry as io.usefulapi/acuity-scheduling. Read appointments, types, calendars and availability; create, cancel or reschedule bookings. This page covers its hosted endpoint (https://acuity-scheduling.usefulapi.io/mcp).
Is the Acuity Scheduling MCP by usefulapi server safe to use?
Acuity Scheduling MCP by usefulapi scores 18 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 Acuity Scheduling MCP by usefulapi server expose?
Acuity Scheduling MCP by usefulapi exposes 18 tools: acuity_list_appointments, acuity_get_appointment, acuity_list_appointment_types, acuity_list_calendars, acuity_availability_dates, and 13 more. Their descriptions and schemas cost roughly 1,904 tokens of context every time the server is loaded.
Does the Acuity Scheduling MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Acuity Scheduling MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Acuity Scheduling MCP by usefulapi server still maintained?
Acuity Scheduling MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.