# io.usefulapi/youcanbookme (remote · youcanbookme.usefulapi.io)

Manage YouCanBook.me bookings, booking pages, appointment types, team members and locations.

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

## Components

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

## Channel facts

- Endpoint: `https://youcanbookme.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**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2696 tokens (~149/item across 18 items; 18 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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-youcanbookme https://youcanbookme.usefulapi.io/mcp
```

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-youcanbookme": {
      "type": "http",
      "url": "https://youcanbookme.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-01 (score 71, +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-07-31 (score 70, +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 67, −2)

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

### 2026-07-29 (score 69, +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-28 (score 68, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-07-27 (score 67, +55)

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

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

First indexed and scored.

## MCP tools (18)

### `list_bookings` (~316 tokens)

List bookings

List bookings (appointments) on the YouCanBookMe account. YCBM API: GET /v1/bookings. Filter by profileId (booking page), an after/before time window, cancelled status, and a free-text searchText; select fields with `fields`. Paginated via page (0-based) + maxResults. Returns a JSON array of bookings.

Input parameters:

- `after` (string): Only bookings starting AFTER this time (ISO 8601, e.g. 2026-07-01T00:00:00Z).
- `before` (string): Only bookings starting BEFORE this time (ISO 8601).
- `cancelled` (boolean): Filter by cancelled status: true = only cancelled, false = only active. Omit for all.
- `fields` (string): Comma-separated field paths to return (e.g. "id,title,startsAt"). Supports dotted paths for nested objects. Omit to get the default field set.
- `maxResults` (integer): Maximum records per page (page size). Defaults to the API's own default when omitted.
- `page` (integer): Pagination page number, 0-based (offset-based paging). Use with maxResults.
- `params` (object): Additional documented query-string filters to send verbatim (merged with the typed params above).
- `profileId` (string): Restrict to bookings on this profile (booking page) id.
- `searchText` (string): Free-text search across booking fields (e.g. attendee name/email).

### `get_booking` (~100 tokens)

Get a booking

Fetch a single booking (appointment) by id. YCBM API: GET /v1/bookings/{bookingId}. Use `fields` to select which fields to return. Returns the booking object.

Input parameters:

- `bookingId` (string, required): The booking id.
- `fields` (string): Comma-separated field paths to return (e.g. "id,title,startsAt"). Supports dotted paths for nested objects. Omit to get the default field set.

### `list_profiles` (~201 tokens)

List profiles (booking pages)

List all profiles (booking pages) on the account. YCBM API: GET /v1/profiles. A profile is a bookable page with its own subdomain, appointment types, team members, and locations. Use `fields` to select fields (e.g. "id,title,subdomain"). Paginated via page (0-based) + maxResults. Returns a JSON array of profiles.

Input parameters:

- `fields` (string): Comma-separated field paths to return (e.g. "id,title,startsAt"). Supports dotted paths for nested objects. Omit to get the default field set.
- `maxResults` (integer): Maximum records per page (page size). Defaults to the API's own default when omitted.
- `page` (integer): Pagination page number, 0-based (offset-based paging). Use with maxResults.
- `params` (object): Additional documented query-string filters to send verbatim (merged with the typed params above).

### `get_profile` (~116 tokens)

Get a profile (booking page)

Fetch a single profile (booking page) by id. YCBM API: GET /v1/profiles/{profileId}. Use `fields` to select fields, including nested sub-resources (appointmentTypes, teamMembers, locations). Returns the profile object.

Input parameters:

- `fields` (string): Comma-separated field paths to return (e.g. "id,title,startsAt"). Supports dotted paths for nested objects. Omit to get the default field set.
- `profileId` (string, required): The profile (booking page) id.

### `list_team_members` (~82 tokens)

List a profile's team members

List the team members configured on a profile (booking page). YCBM API: GET /v1/profiles/{profileId} with a teamMembers field selection. Returns the profile's teamMembers block (each member has id, name, email, description, pic, calendarId).

Input parameters:

- `profileId` (string, required): The profile (booking page) id.

### `list_appointment_types` (~80 tokens)

List a profile's appointment types

List the appointment types configured on a profile (booking page). YCBM API: GET /v1/profiles/{profileId} with an appointmentTypes field selection. Returns the profile's appointmentTypes block (each with id, name, description, slotLength, price).

Input parameters:

- `profileId` (string, required): The profile (booking page) id.

### `list_locations` (~74 tokens)

List a profile's locations

List the locations configured on a profile (booking page). YCBM API: GET /v1/profiles/{profileId} with a locations field selection. Returns the profile's locations block (each with id, kind, value, notes, strategy).

Input parameters:

- `profileId` (string, required): The profile (booking page) id.

### `list_available_accounts` (~61 tokens)

List available accounts (calendars)

List the accounts/calendars available to your account — used to find the calendarId for a team member. YCBM API: GET /v1/{accountId}/availableAccounts (accountId is taken from your configured credentials). Returns a JSON array.

### `youcanbookme_request` (~114 tokens)

Raw read request

Power-user escape hatch: GET any YCBM API path not wrapped by a dedicated tool. READ-ONLY — only GET is allowed. Pass the FULL API path after the origin, starting with a slash, INCLUDING any query string, e.g. "/v1/bookings?maxResults=5" or "/v1/profiles". Returns the parsed JSON.

Input parameters:

- `path` (string, required): Full API path after the origin, starting with "/", e.g. "/v1/bookings?maxResults=5".

### `create_booking` (~246 tokens)

Create a booking

MUTATES YouCanBookMe data: creates a booking (appointment) on a profile. YCBM API: POST /v1/bookings (JSON). Required: profileId, startsAt, endsAt (ISO 8601 times). Optional: title, timeZone, locale, units. Complex fields like `answers` (form-field answers) and `linkFields` should be passed via the `fields` passthrough. Returns the created booking.

Input parameters:

- `endsAt` (string, required): Booking end time, ISO 8601 (required).
- `fields` (object): Additional documented YCBM fields to send in the JSON write body — merged OVER the typed fields above.
- `locale` (string): Locale for the booking (e.g. en-GB).
- `profileId` (string, required): The profile (booking page) id to book on (required).
- `startsAt` (string, required): Booking start time, ISO 8601 (required).
- `timeZone` (string): IANA time zone for the booking (e.g. Europe/London).
- `title` (string): Booking title.
- `units` (integer): Number of slot units to book.

### `update_booking` (~269 tokens)

Update a booking

MUTATES YouCanBookMe data: updates an existing booking (reschedule, rename, mark cancelled/no-show). YCBM API: PATCH /v1/bookings/{bookingId} (JSON, partial update). Set any of title/startsAt/endsAt/cancelled/noShow/timeZone/locale/units; use the `fields` passthrough for answers/linkFields or other documented fields. The path id is never sent in the body.

Input parameters:

- `bookingId` (string, required): The booking id to update (path only; required).
- `cancelled` (boolean): Set true to cancel the booking, false to un-cancel.
- `endsAt` (string): New end time, ISO 8601 (reschedule).
- `fields` (object): Additional documented YCBM fields to send in the JSON write body — merged OVER the typed fields above.
- `locale` (string): New locale.
- `noShow` (boolean): Mark the attendee as a no-show (true) or not (false).
- `startsAt` (string): New start time, ISO 8601 (reschedule).
- `timeZone` (string): New IANA time zone.
- `title` (string): New booking title.
- `units` (integer): New number of slot units.

### `cancel_booking` (~80 tokens)

Cancel a booking

MUTATES YouCanBookMe data: cancels a booking. Convenience wrapper for PATCH /v1/bookings/{bookingId} with { cancelled: true } — safer and reversible (re-activate via update_booking cancelled=false) versus deleting. Returns the updated booking.

Input parameters:

- `bookingId` (string, required): The booking id to cancel (path only; required).

### `update_profile` (~145 tokens)

Update a profile (booking page)

MUTATES YouCanBookMe data: updates a profile's (booking page) configuration. YCBM API: PATCH /v1/profiles/{profileId} (JSON, partial update). Pass the fields to change via the `fields` passthrough (e.g. { title, subdomain, ... }) — profile fields are numerous and use YCBM's own names. The path id is never sent in the body.

Input parameters:

- `fields` (object): Additional documented YCBM fields to send in the JSON write body — merged OVER the typed fields above.
- `profileId` (string, required): The profile (booking page) id to update (path only; required).

### `create_appointment_type` (~140 tokens)

Create an appointment type

MUTATES YouCanBookMe data: adds an appointment type to a profile. YCBM API: POST /v1/profiles/{profileId}/appointmenttypes/items (JSON). Required: name; use the `fields` passthrough for description, slotLength, price, etc. The path profileId is never sent in the body.

Input parameters:

- `fields` (object): Additional documented YCBM fields to send in the JSON write body — merged OVER the typed fields above.
- `name` (string, required): The appointment type name (required).
- `profileId` (string, required): The profile (booking page) id (path only; required).

### `update_appointment_type` (~154 tokens)

Update an appointment type

MUTATES YouCanBookMe data: updates an appointment type on a profile. YCBM API: PATCH /v1/profiles/{profileId}/appointmenttypes/items/{appointmentTypeId} (JSON, partial update). Pass changed fields (name, description, slotLength, price, ...) via the `fields` passthrough. Path ids are never sent in the body.

Input parameters:

- `appointmentTypeId` (string, required): The appointment type id to update (path only; required).
- `fields` (object): Additional documented YCBM fields to send in the JSON write body — merged OVER the typed fields above.
- `profileId` (string, required): The profile (booking page) id (path only; required).

### `create_team_member` (~175 tokens)

Add a team member

MUTATES YouCanBookMe data: adds a team member to a profile. YCBM API: POST /v1/profiles/{profileId}/teammembers/items (JSON). Required: name; calendarId links the member to a calendar (find it via list_available_accounts). Use the `fields` passthrough for email, description, pic, etc. The path profileId is never sent in the body.

Input parameters:

- `calendarId` (string): The calendar id to link (see list_available_accounts).
- `fields` (object): Additional documented YCBM fields to send in the JSON write body — merged OVER the typed fields above.
- `name` (string, required): The team member's display name (required).
- `profileId` (string, required): The profile (booking page) id (path only; required).

### `update_team_member` (~154 tokens)

Update a team member

MUTATES YouCanBookMe data: updates a team member on a profile. YCBM API: PATCH /v1/profiles/{profileId}/teammembers/items/{teamMemberId} (JSON, partial update). Pass changed fields (name, email, description, calendarId, ...) via the `fields` passthrough. Path ids are never sent in the body.

Input parameters:

- `fields` (object): Additional documented YCBM fields to send in the JSON write body — merged OVER the typed fields above.
- `profileId` (string, required): The profile (booking page) id (path only; required).
- `teamMemberId` (string, required): The team member id to update (path only; required).

### `create_location` (~189 tokens)

Add a location

MUTATES YouCanBookMe data: adds a location to a profile. YCBM API: POST /v1/profiles/{profileId}/locations (JSON). Required: kind (location type) and strategy (how it is assigned). Use the `fields` passthrough for value, notes, and other documented fields. The path profileId is never sent in the body.

Input parameters:

- `fields` (object): Additional documented YCBM fields to send in the JSON write body — merged OVER the typed fields above.
- `kind` (string, required): The location kind/type (required).
- `notes` (string): Notes shown with the location.
- `profileId` (string, required): The profile (booking page) id (path only; required).
- `strategy` (string, required): The location assignment strategy (required).
- `value` (string): The location value (e.g. an address or link).

## Diagnostics

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

## Score history

- 2026-08-03: 71
- 2026-08-02: 71
- 2026-08-01: 71
- 2026-07-31: 70
- 2026-07-30: 67
- 2026-07-29: 69
- 2026-07-28: 68
- 2026-07-27: 67
- 2026-07-26: 12

## Links

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