# Appointedd MCP by usefulapi (remote · appointedd.usefulapi.io)

Read Appointedd bookings, customers and availability; create, change and cancel bookings.

- Trust score: 18/100 (low)
- Change this week: −44
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

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

## Channel facts

- Endpoint: `https://appointedd.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.11.1`

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

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

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

## Install

### How do I install the Appointedd MCP by usefulapi server?

Appointedd MCP by usefulapi is a hosted endpoint at https://appointedd.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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-appointedd 'https://appointedd.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-appointedd": {
      "url": "https://appointedd.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-appointedd": {
      "type": "http",
      "url": "https://appointedd.usefulapi.io/mcp"
    }
  }
}
```

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-appointedd": {
      "Transport": "http",
      "Url": "https://appointedd.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-appointedd -t streamable-http -u 'https://appointedd.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-appointedd": {
      "type": "http",
      "url": "https://appointedd.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-11-02 (score 18, −49)

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

### 2026-11-01 (score 67, +1)

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

### 2026-10-31 (score 66, +3)

- [security improvement] Authorization: partial → pass
- [functional improvement] MCP protocol: fail → pass
- [functional] New prompt “book_a_customer_into_a_slot”
- [functional] New prompt “find_the_next_open_slot_for_a_service”
- [functional] New prompt “list_tomorrow_s_bookings”
- [functional] New prompt “look_up_a_customer_and_their_bookings”
- [functional] New prompt “mark_arrivals_and_no_shows”
- [functional] New prompt “move_or_cancel_a_booking”
- [functional] MCP protocol version: 2025-06-18 → 2025-11-25
- [functional] Server version: 1.7.0 → 1.9.0
- [functional] Server version: 1.6.0 → 1.7.0
- [functional] Server version: 1.5.2 → 1.6.0

### 2026-10-30 (score 63, +1)

- [functional] Server version: 1.5.1 → 1.5.2
- [functional] Server version: 1.5.0 → 1.5.1

### 2026-10-29 (score 62, 0)

- [functional] Server version: 1.4.0 → 1.5.0
- [functional] Server version: 1.3.0 → 1.4.0

### 2026-10-28 (score 62, +1)

- [functional] Server version: 1.1.0 → 1.3.0

### 2026-10-27 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-10-26 (score 61)

First indexed and scored.

## MCP tools (20)

### `appointedd_list_bookings` (~520 tokens)

List bookings

List bookings, newest first by default. Filter by time window (after/before), customer, service, resource, category, status or creation/update time. Each booking has its service, resource, start/end, status and the customers on it (with their notes, questions and statuses). Page with `next`. GET /bookings.

Input parameters:

- `after` (string): Only bookings that start at or after this date-time.
- `before` (string): Only bookings that end at or before this date-time.
- `categories` (array): Only bookings of service categories with one of these ids.
- `created_after` (string): ISO 8601 date-time, e.g. 2026-11-02T09:00:00Z (a date-time without an offset is read in UTC unless a timezone is given).
- `created_before` (string): ISO 8601 date-time, e.g. 2026-11-02T09:00:00Z (a date-time without an offset is read in UTC unless a timezone is given).
- `customers` (array): Only bookings for customers with one of these ids.
- `end` (string): Page cursor: pass the previous reply's `prev` to get the preceding page.
- `ids` (array): Only bookings with one of these ids.
- `limit` (integer): Results per page, 1-100 (default 25).
- `order_by` (string): Sort direction (the API default is desc).
- `resources` (array): Only bookings of resources with one of these ids.
- `services` (array): Only bookings of services with one of these ids.
- `sort_by` (string): Sort property (default natural).
- `start` (string): Page cursor: pass the previous reply's `next` to get the following page.
- `statuses` (array): Only bookings with one of these statuses.
- `timezone` (string): IANA time zone for the dates and times in the reply, e.g. Europe/London (default UTC).
- `updated_after` (string): ISO 8601 date-time, e.g. 2026-11-02T09:00:00Z (a date-time without an offset is read in UTC unless a timezone is given).
- `updated_before` (string): ISO 8601 date-time, e.g. 2026-11-02T09:00:00Z (a date-time without an offset is read in UTC unless a timezone is given).

### `appointedd_list_customers` (~152 tokens)

List customers

List customers in the CRM: name, email, phone/mobile, address, tags, custom fields, marketing opt-in. Page with `next`. GET /customers.

Input parameters:

- `end` (string): Page cursor: pass the previous reply's `prev` to get the preceding page.
- `ids` (array): Only customers with one of these ids.
- `limit` (integer): Results per page, 1-100 (default 25).
- `order_by` (string): Sort direction (the API default is desc).
- `sort_by` (string): Sort property (default natural).
- `start` (string): Page cursor: pass the previous reply's `next` to get the following page.

### `appointedd_get_customer` (~39 tokens)

Get customer

One customer by id. GET /customers/{customer_id}.

Input parameters:

- `customer_id` (string, required): Appointedd id (24-character hex string).

### `appointedd_list_resources` (~165 tokens)

List resources

List resources (the staff members, rooms or equipment that bookings are made for): name, assigned service ids and resource group ids. Page with `next`. GET /resources.

Input parameters:

- `end` (string): Page cursor: pass the previous reply's `prev` to get the preceding page.
- `ids` (array): Only resources with one of these ids.
- `limit` (integer): Results per page, 1-100 (default 25).
- `order_by` (string): Sort direction (the API default is desc).
- `services` (array): Only resources assigned to services with one of these ids.
- `sort_by` (string)
- `start` (string): Page cursor: pass the previous reply's `next` to get the following page.

### `appointedd_list_resource_groups` (~125 tokens)

List resource groups

List resource groups (id and name). Page with `next`. GET /resources/groups.

Input parameters:

- `end` (string): Page cursor: pass the previous reply's `prev` to get the preceding page.
- `ids` (array): Only resource groups with one of these ids.
- `limit` (integer): Results per page, 1-100 (default 25).
- `order_by` (string): Sort direction (the API default is desc).
- `start` (string): Page cursor: pass the previous reply's `next` to get the following page.

### `appointedd_list_services` (~121 tokens)

List services

List services (what can be booked): name, category, durations and prices, buffers, occupancy and booking type. Page with `next`. GET /services.

Input parameters:

- `end` (string): Page cursor: pass the previous reply's `prev` to get the preceding page.
- `ids` (array): Only services with one of these ids.
- `limit` (integer): Results per page, 1-100 (default 25).
- `start` (string): Page cursor: pass the previous reply's `next` to get the following page.

### `appointedd_get_service` (~50 tokens)

Get service

One service by id, including its booking questions, durations, prices and buffers. GET /services/{service_id}.

Input parameters:

- `service_id` (string, required): Appointedd id (24-character hex string).

### `appointedd_list_service_categories` (~109 tokens)

List service categories

List service categories (id and name). Page with `next`. GET /services/categories.

Input parameters:

- `end` (string): Page cursor: pass the previous reply's `prev` to get the preceding page.
- `ids` (array): Only service categories with one of these ids.
- `limit` (integer): Results per page, 1-100 (default 25).
- `start` (string): Page cursor: pass the previous reply's `next` to get the following page.

### `appointedd_get_service_category` (~42 tokens)

Get service category

One service category by id. GET /services/categories/{category_id}.

Input parameters:

- `category_id` (string, required): Appointedd id (24-character hex string).

### `appointedd_find_available_intervals` (~270 tokens)

Find available times

Find the start times at which a service can be booked in the given ranges, with the free resource ids for each (and existing group bookings with room). Step 1 of making a booking: pick a start, then appointedd_create_reservation. Read-only. POST /availability/intervals/search.

Input parameters:

- `duration` (integer): Continuous minutes that must be free. Default: the service's default duration.
- `ignore_notice_restriction` (boolean): Ignore the organisation's/service's notice period.
- `ignore_service_schedule` (boolean): Ignore the service's schedule.
- `ranges` (array, required): One or more date-time ranges to search, e.g. [{start, end}].
- `resource_group_ids` (array): Resource groups whose resources to check. Not together with resource_ids.
- `resource_ids` (array): Resources (staff, rooms) to check. Default: all resources assigned to the service. Not together with resource_group_ids.
- `service_id` (string, required): Service the booking would be for (use appointedd_list_services).
- `spaces` (integer): Spaces needed (excludes group bookings with too few spaces). Default 1.
- `timezone` (string): IANA time zone for range times without an offset and for the reply. Default UTC.

### `appointedd_find_available_dates` (~247 tokens)

Find available days

Find which days in the given ranges have any availability for a service (a calendar view; use appointedd_find_available_intervals for the times). Read-only. POST /availability/days/search.

Input parameters:

- `duration` (integer): Continuous minutes that must be free. Default: the service's default duration.
- `ignore_notice_restriction` (boolean): Ignore the organisation's/service's notice period.
- `ignore_service_schedule` (boolean): Ignore the service's schedule.
- `ranges` (array, required): One or more date-time ranges to search, e.g. [{start, end}].
- `resource_group_ids` (array): Resource groups whose resources to check. Not together with resource_ids.
- `resource_ids` (array): Resources (staff, rooms) to check. Default: all resources assigned to the service. Not together with resource_group_ids.
- `service_id` (string, required): Service the booking would be for (use appointedd_list_services).
- `spaces` (integer): Spaces needed (excludes group bookings with too few spaces). Default 1.
- `timezone` (string): IANA time zone for range times without an offset and for the reply. Default UTC.

### `appointedd_get_reservation` (~84 tokens)

Get reservation

One reservation (availability slot) by id: its service, resource, times and expiry. GET /availability/slots/{reservation_id}.

Input parameters:

- `reservation_id` (string, required): Appointedd id (24-character hex string).
- `timezone` (string): IANA time zone for the dates and times in the reply, e.g. Europe/London (default UTC).

### `appointedd_create_customer` (~90 tokens)

Create customer

WRITE: create a customer in the CRM (first and last name required; email, mobile, phone, tags optional). POST /customers.

Input parameters:

- `email` (string)
- `firstname` (string, required): First name.
- `lastname` (string, required): Last name.
- `mobile` (string)
- `phone` (string)
- `tags` (array): Tags to put on the customer.

### `appointedd_update_customer` (~117 tokens)

Update customer

WRITE: change a customer's name, email, mobile, phone or tags. Only the fields you pass are sent; `tags` replaces the customer's tag list. PUT /customers/{customer_id}.

Input parameters:

- `customer_id` (string, required): Appointedd id (24-character hex string).
- `email` (string)
- `firstname` (string)
- `lastname` (string)
- `mobile` (string)
- `phone` (string)
- `tags` (array): New tag list (replaces the old one).

### `appointedd_create_reservation` (~285 tokens)

Create reservation (hold a time)

WRITE: hold a date and time for a booking (step 2). The reservation blocks that slot for `expires_after` minutes (default: the organisation's setting); then call appointedd_create_booking with the returned reservation id. Without resource_id a free resource assigned to the service is picked. POST /availability/slots.

Input parameters:

- `duration` (integer): Booking length in minutes; pass the same `duration` you searched with. Default: the service's default duration.
- `expires_after` (integer): Minutes until the hold expires.
- `ignore_notice_restriction` (boolean): Ignore the notice period; set it if you searched with it.
- `ignore_service_schedule` (boolean): Ignore the service's schedule; set it if you searched with it.
- `required_spaces` (integer): Spaces needed (default 1).
- `resource_group_ids` (array): Restrict the automatic resource choice to these groups.
- `resource_id` (string): Resource to book. Default: any free resource of the service.
- `service_id` (string, required): Appointedd id (24-character hex string).
- `start` (string, required): Start date-time, normally a `start` returned by appointedd_find_available_intervals.
- `timezone` (string): IANA time zone of `start` (when it has no offset) and of the reply. Default UTC.

### `appointedd_create_booking` (~184 tokens)

Create booking

WRITE: turn an active reservation into a booking (step 3) for one or more customers; Appointedd matches each customer to the CRM by name/email/mobile or creates it. Payment requests are NOT sent unless send_payment_request is true. With an empty customers list an empty booking is created. POST /bookings.

Input parameters:

- `customers` (array, required): Customers to add; [] for an empty booking.
- `label` (string): Label shown on the booking in the appointment screen.
- `reservation_id` (string, required): Id returned by appointedd_create_reservation (must not have expired).
- `send_payment_request` (boolean): Send each customer a payment request (default false here; the API's own default is true).
- `timezone` (string): IANA time zone for the dates and times in the reply, e.g. Europe/London (default UTC).

### `appointedd_update_booking` (~212 tokens)

Update booking

WRITE: change a booking's service, resource, label or total spaces, or move it by giving `parts` with new start/end times. Customers are NOT emailed unless send_notifications is true. PUT /bookings/{booking_id}.

Input parameters:

- `booking_id` (string, required): Appointedd id (24-character hex string).
- `ignore_service_schedule` (boolean): Allow moving outside the service's schedule.
- `label` (string)
- `parts` (array): New time parts of the booking (start/end); an availability check runs when moving.
- `resource_id` (string): Assign the booking to this resource.
- `send_notifications` (boolean): Email each customer that the booking changed (default false here; the API's own default is true).
- `service_id` (string): Move the booking to this service.
- `timezone` (string): IANA time zone for the dates and times in the reply, e.g. Europe/London (default UTC).
- `total_spaces` (integer)

### `appointedd_update_booking_customer` (~142 tokens)

Update customer on booking

WRITE: set the arrival status (Arrived, Complete, No Show, No Status) and/or notes of one customer on a booking. customer_booking_id is the customer's `customer_booking_id` (or `customer_id`) in the booking's customers list. PUT /bookings/{booking_id}/customers/{customer_booking_id}.

Input parameters:

- `booking_id` (string, required): Appointedd id (24-character hex string).
- `customer_booking_id` (string, required): `customer_booking_id` (or `customer_id`) from the booking's customers list.
- `notes` (string): Replaces the customer's notes on this booking.
- `status` (string)

### `appointedd_cancel_booking` (~77 tokens)

Cancel booking

WRITE (cannot be undone): cancel a whole booking. Appointedd may notify the customers according to the organisation's settings. To remove one customer from a group booking use appointedd_cancel_booking_customer. POST /bookings/{booking_id}/cancel.

Input parameters:

- `booking_id` (string, required): Appointedd id (24-character hex string).

### `appointedd_cancel_booking_customer` (~102 tokens)

Cancel customer on booking

WRITE (cannot be undone): cancel one customer's place on a booking (the booking stays for the others). customer_booking_id is the `customer_booking_id` in the booking's customers list. POST /bookings/{booking_id}/customers/{customer_booking_id}/cancel.

Input parameters:

- `booking_id` (string, required): Appointedd id (24-character hex string).
- `customer_booking_id` (string, required): `customer_booking_id` from the booking's customers list.

## Diagnostics

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

## Score history

- 2026-11-05: 18
- 2026-11-04: 18
- 2026-11-03: 18
- 2026-11-02: 18
- 2026-11-01: 67
- 2026-10-31: 66
- 2026-10-30: 63
- 2026-10-29: 62
- 2026-10-28: 62
- 2026-10-27: 61
- 2026-10-26: 61

## Common questions

### What is the Appointedd MCP by usefulapi server?

Appointedd MCP by usefulapi is listed in the public MCP registry as io.usefulapi/appointedd. Read Appointedd bookings, customers and availability; create, change and cancel bookings. This page covers its hosted endpoint (https://appointedd.usefulapi.io/mcp).

### Is the Appointedd MCP by usefulapi server safe to use?

Appointedd 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 Appointedd MCP by usefulapi server expose?

Appointedd MCP by usefulapi exposes 20 tools: appointedd_list_bookings, appointedd_list_customers, appointedd_get_customer, appointedd_list_resources, appointedd_list_resource_groups, and 15 more. Their descriptions and schemas cost roughly 3,133 tokens of context every time the server is loaded.

### Does the Appointedd MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Appointedd 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 Appointedd MCP by usefulapi server still maintained?

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

## Links

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