Bookafy MCP by usefulapi
REMOTE · BOOKAFY.USEFULAPI.IO
Review appointments, customers and staff, and manage Bookafy bookings.
Available components
Last scanned (6 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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.
- 2 Nov 26 −48
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.07 → 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 +4
- Authorization: partial → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- MCP protocol: fail → pass ▲ functional
- New prompt “find_a_customer_record” functional
- New prompt “reschedule_an_appointment” functional
- New prompt “review_a_staff_calendar” functional
- New prompt “share_a_self_booking_link” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.2.0 → 1.4.0 functional
- Server version: 1.1.0 → 1.2.0 functional
- Server version: 1.0.2 → 1.1.0 functional
- 30 Oct 26 62
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 5 Nov 2026 · Probed https://bookafy.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 bookafy.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://bookafy.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/bookafy/ |
| http (plaintext) | http://bookafy.usefulapi.io/mcp | Inconclusive | 302 | http://bookafy.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 →
bookafy_cancel_appointment Cancel appointment ~108
WRITE, IRREVERSIBLE: delete (cancel) an appointment. Bookafy may notify the customer and remove the event from connected calendars, and the appointment cannot be restored through the API. Only call it when the user explicitly asked to cancel this appointment. DELETE /api/v3/appointments/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| appointment_id | integer | yes | Appointment id (from bookafy_list_appointments). |
| staff_user_id | integer | yes | Staff user the appointment is with (its user_id). |
No output schema declared.
No examples provided.
bookafy_create_appointment Create appointment ~326
WRITE: book an appointment for a customer with a staff member and service (ids from bookafy_list_staff and bookafy_list_services). The customer is created from the given name/email/phone. Bookafy may email the booking confirmation to the customer and add the event to connected calendars, so only call it when the user clearly asked to book. Times are converted to UTC. POST /api/v3/appointments.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_fields | object | – | Custom booking-form answers as {field_name: value}, with underscores for spaces, e.g. {"What_is_your_DOB": "1990"}. |
| customer_email | string | – | Customer's email (the confirmation goes there). |
| customer_name | string | yes | Customer's full name. |
| customer_phone | string | – | Customer's phone number. |
| description | string | – | Notes shown with the appointment. |
| end | string | yes | End, ISO 8601 date-time with timezone (after start, at most 24 h later). |
| price | number | – | Price of the appointment (default: the service's price). |
| service_id | integer | yes | Service id assigned to that staff user (from bookafy_list_services). |
| staff_user_id | integer | yes | Staff user id (from bookafy_list_staff). |
| start | string | yes | Start, ISO 8601 date-time with timezone, e.g. 2026-11-02T09:30:00-05:00. |
| title | string | – | Title shown for the appointment (default: Bookafy's own). |
No output schema declared.
No examples provided.
bookafy_create_customer Create customer ~115
WRITE: add a customer record (name required; email, phone and custom booking-form answers optional). It does not book anything. POST /api/v3/customers.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_fields | object | – | Custom booking-form answers as {field_name: value}, with underscores for spaces, e.g. {"What_is_your_DOB": "1990"}. |
| string | – | Customer's email. | |
| name | string | yes | Customer's full name. |
| phone | string | – | Customer's phone number. |
No output schema declared.
No examples provided.
bookafy_get_account Get account ~41
The account this API key belongs to: the admin user's email. Use it to confirm which Bookafy account is connected. GET /api/v3/me.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bookafy_get_class Get class with sessions and attendees ~172
One class with its sessions and the attendees booked on each (name, email, phone, booking time). Optional filters narrow the sessions. GET /api/v3/classes/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| attendee_name | string | – | Only sessions with an attendee of this name. |
| class_id | integer | yes | Class id (from bookafy_list_classes). |
| duration | integer | – | Only sessions of this length in minutes. |
| from | string | – | Only sessions starting at or after this moment (yyyy-mm-dd or ISO 8601 date-time with timezone). |
| price | number | – | Only sessions with this price. |
| provider_name | string | – | Only sessions run by this provider. |
| to | string | – | Only sessions ending before this moment (yyyy-mm-dd or ISO 8601 date-time with timezone). |
No output schema declared.
No examples provided.
bookafy_list_appointment_types List appointment types with booking links ~48
The appointment types grouped by category, each with its public booking-page link — use it to give a customer the link to book themselves. GET /api/v3/appointment_types.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bookafy_list_appointments List appointments ~222
List the appointments of ONE staff member (identified by their email: take it from bookafy_list_staff), newest first, optionally within a UTC date range. Each item has the service, customer, start/end time (UTC), title, price, duration and status. Page with page/per_page (default 25). Cancel/reschedule tokens are never returned. GET /api/v3/appointments.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Only appointments starting at or after this moment: yyyy-mm-dd (midnight UTC) or ISO 8601 date-time with timezone. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). |
| staff_email | string | yes | Email of the staff user whose appointments to list (from bookafy_list_staff). |
| to | string | – | Only appointments ending before this moment: yyyy-mm-dd (midnight UTC) or ISO 8601 date-time with timezone. |
No output schema declared.
No examples provided.
bookafy_list_classes List classes ~50
List classes and one-off appointments with price, duration, location, seats, booking link and their sessions (date, seats total/filled/remaining, zoom link). GET /api/v3/classes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bookafy_list_customers List customers ~140
List the account's customers (id, name, email, phone and custom booking-form answers). Bookafy returns the whole list at once; use `search` (matches name, email or phone) and `limit`/`offset` to page through it. GET /api/v3/customers.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Most customers to return, 1-500 (default 100). |
| offset | integer | – | Skip this many matches (default 0). Pass the previous reply's next_offset to read on. |
| search | string | – | Only customers whose name, email or phone contains this text (case-insensitive). |
No output schema declared.
No examples provided.
bookafy_list_services List services ~51
List every service (appointment type) with id, name, price, duration, buffers, category, scheduling mode and online-meeting options. Use the ids when booking. GET /api/v3/services.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bookafy_list_session_attendees List session attendees ~60
The attendees of one class session (name, email, phone). Get session ids from bookafy_list_classes. GET /api/v3/sessions.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | integer | yes | Session id (sessionId in bookafy_list_classes). |
No output schema declared.
No examples provided.
bookafy_list_staff List staff ~42
List the staff users (id, name, email, booking-page URL). Use the id or email for appointments. GET /api/v3/staff_members.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bookafy_list_webhooks List webhook subscriptions ~43
List the webhook subscriptions (id, callback URL, event type such as appointment_created or customer_updated). Read-only. GET /api/v3/api_subscriptions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bookafy_update_appointment Update appointment ~272
WRITE: reschedule or edit an existing appointment. Send the required staff, service, new times and customer name — read current values with bookafy_list_appointments first. Omitted optional fields are not sent. The customer may be notified of the change. Times are converted to UTC. PUT /api/v3/appointments/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| appointment_id | integer | yes | Appointment id (from bookafy_list_appointments). |
| custom_fields | object | – | Custom booking-form answers as {field_name: value}, with underscores for spaces, e.g. {"What_is_your_DOB": "1990"}. |
| customer_email | string | – | Customer's email. |
| customer_name | string | yes | Customer's full name. |
| customer_phone | string | – | Customer's phone number. |
| description | string | – | Notes shown with the appointment. |
| end | string | yes | New end, ISO 8601 date-time with timezone (after start, at most 24 h later). |
| price | number | – | Price of the appointment. |
| service_id | integer | yes | Service id. |
| staff_user_id | integer | yes | Staff user the appointment is with. |
| start | string | yes | New start, ISO 8601 date-time with timezone. |
| title | string | – | Appointment title. |
No output schema declared.
No examples provided.
bookafy_update_customer Update customer ~151
WRITE: change a customer's details. Bookafy needs the name every time, so pass the current name when you only change the email or phone. Fields you leave out are not sent. PUT /api/v3/customers/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_fields | object | – | Custom booking-form answers as {field_name: value}, with underscores for spaces, e.g. {"What_is_your_DOB": "1990"}. |
| customer_id | integer | yes | Customer id (from bookafy_list_customers). |
| string | – | New email. | |
| name | string | yes | Customer's full name (required by Bookafy on every update). |
| phone | string | – | New phone number. |
No output schema declared.
No examples provided.
How do I install the Bookafy MCP by usefulapi server?
Bookafy MCP by usefulapi is a hosted endpoint at https://bookafy.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 · bookafy.usefulapi.io
claude mcp add --transport http io-usefulapi-bookafy 'https://bookafy.usefulapi.io/mcp'
What is the Bookafy MCP by usefulapi server?
Bookafy MCP by usefulapi is listed in the public MCP registry as io.usefulapi/bookafy. Review appointments, customers and staff, and manage Bookafy bookings. This page covers its hosted endpoint (https://bookafy.usefulapi.io/mcp).
Is the Bookafy MCP by usefulapi server safe to use?
Bookafy 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 Bookafy MCP by usefulapi server expose?
Bookafy MCP by usefulapi exposes 15 tools: bookafy_get_account, bookafy_list_appointments, bookafy_create_appointment, bookafy_update_appointment, bookafy_cancel_appointment, and 10 more. Their descriptions and schemas cost roughly 1,841 tokens of context every time the server is loaded.
Does the Bookafy MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Bookafy 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 Bookafy MCP by usefulapi server still maintained?
Bookafy 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.