# Yoya Booking (remote · yoya.ai)

Book meetings on a host's real availability. No auth - mirrors their public Yoya page.

- Trust score: 72/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

> **Recent critical change**: Authorization (2026-09-14). See the changelog below before you install this server.

## Components

- remote · `yoya.ai`: 72/100 (this document), [markdown](https://verifymcp.io/servers/makloai-yoya-booking/api-mcp-book.md), [page](https://verifymcp.io/servers/makloai-yoya-booking/api-mcp-book)

## Channel facts

- Endpoint: `https://yoya.ai/api/mcp/book`
- 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-09-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (book_meeting).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 643 tokens (~80/item across 8 items; 7 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 51/100
  - Stability check failed: schema churn in the 19 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 3 additions.
- **Tool Coverage**: 73/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 6% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the Yoya Booking MCP server?

Yoya Booking is a hosted endpoint at https://yoya.ai/api/mcp/book, 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 makloai-yoya-booking 'https://yoya.ai/api/mcp/book'
```

### Cursor

```json
{
  "mcpServers": {
    "makloai-yoya-booking": {
      "url": "https://yoya.ai/api/mcp/book"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "makloai-yoya-booking": {
      "type": "http",
      "url": "https://yoya.ai/api/mcp/book"
    }
  }
}
```

### Codex

```toml
[mcp_servers.makloai-yoya-booking]
url = "https://yoya.ai/api/mcp/book"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "makloai-yoya-booking": {
      "type": "remote",
      "url": "https://yoya.ai/api/mcp/book",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add makloai-yoya-booking --url 'https://yoya.ai/api/mcp/book' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  makloai-yoya-booking:
    url: "https://yoya.ai/api/mcp/book"
```

### Netclaw

```json
{
  "McpServers": {
    "makloai-yoya-booking": {
      "Transport": "http",
      "Url": "https://yoya.ai/api/mcp/book"
    }
  }
}
```

### Vellum

```bash
assistant mcp add makloai-yoya-booking -t streamable-http -u 'https://yoya.ai/api/mcp/book'
```

### Other

```json
{
  "mcpServers": {
    "makloai-yoya-booking": {
      "type": "http",
      "url": "https://yoya.ai/api/mcp/book"
    }
  }
}
```

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-09-19 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 44 to 48.

### 2026-09-17 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 38 to 41.

### 2026-09-15 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 31 to 34.

### 2026-09-14 (score 69, −1)

- [critical regression] Authorization: unverified → fail
- [security regression] Stability: 0.40 → fail
- [security] New tool “cancel_booking”, which the server declares destructive
- [security] New tool “reschedule_booking”, which the server declares destructive
- [security] Tool “book_meeting” rewrote its description, which is the text the model reads
- [security] Tool “get_booking” rewrote its description, which is the text the model reads
- [security] Tool “get_booking_page” rewrote its description, which is the text the model reads
- [security] Tool “list_available_times” rewrote its description, which is the text the model reads
- [security] Tool “book_meeting” is now declared destructive
- [functional regression] Tool coverage: 42% → 6%
- [functional regression] “book_meeting” added a required parameter “confirmationToken”, so existing callers break
- [functional regression] “book_meeting” added a required parameter “confirmed”, so existing callers break
- [functional improvement] Schema quality: 109 → 80
- [functional improvement] Tool “book_meeting” now declares an output schema
- [functional improvement] Tool “get_booking” now declares an output schema
- [functional improvement] Tool “get_booking_page” now declares an output schema
- [functional improvement] Tool “list_available_times” now declares an output schema
- [functional] The server now declares the “resources” capability
- [functional] First check of Capabilities: pass
- [functional] First check of Schema quality: 100
- [functional] First check of Tool coverage: 100
- [functional] MCP protocol: Implements a current MCP spec version (2026-07-28).
- [functional] MCP protocol version: 2025-11-25 → 2026-07-28
- [functional] New resource “Yoya booking”
- [functional] Server version: 1.0.0 → 2.0.0
- [functional] New tool “preview_booking”
- [cosmetic] “list_available_times” added an optional parameter “cursor”
- [cosmetic] “list_available_times” added an optional parameter “from”
- [cosmetic] “list_available_times” added an optional parameter “limit”
- [cosmetic] “list_available_times” added an optional parameter “timeOfDay”
- [cosmetic] “list_available_times” added an optional parameter “timezone”
- [cosmetic] “list_available_times” added an optional parameter “to”
- [cosmetic] “book_meeting” reworded the description of “fieldAnswers”
- [cosmetic] “book_meeting” reworded the description of “meetingType”
- [cosmetic] “book_meeting” reworded the description of “purpose”
- [cosmetic] “book_meeting” reworded the description of “requestId”
- [cosmetic] “book_meeting” reworded the description of “timezone”
- [cosmetic] Tool “book_meeting” changed its title: Book a meeting → Confirm a reviewed meeting
- [cosmetic] Tool “get_booking” changed its title: Get a booking → Check a booking
- [cosmetic] Tool “list_available_times” changed its title: List available times → Find available meeting times

### 2026-09-13 (score 70, +1)

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

### 2026-09-11 (score 69, +1)

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

### 2026-09-09 (score 68, +1)

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

### 2026-09-07 (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.

## MCP tools (7)

### `get_booking_page` (~39 tokens)

Get a Yoya booking page

Read a public Yoya booking link or slug. Includes required guest fields and meeting options. No host account access.

Input parameters:

- `slug` (string, required)

Output parameters:

- `code` (string)
- `message` (string)
- `nextCursor` (string|null)
- `nextOffset`
- `ok` (boolean)
- `syncStatus` (string)

### `list_available_times` (~141 tokens)

Find available meeting times

Find up to 10 times (max 50), labeled in the guest's IANA timezone. Filter by inclusive from/exclusive to datetimes and morning (06–12), afternoon (12–18) or evening (18–24) in the guest timezone. Pass nextCursor unchanged to continue with the same filters. Slots are suggestions; preview then book rechecks availability. Never invent slot IDs.

Input parameters:

- `cursor` (string)
- `from` (string)
- `limit` (integer)
- `slug` (string, required)
- `timeOfDay` (string)
- `timezone` (string)
- `to` (string)

Output parameters:

- `code` (string)
- `message` (string)
- `nextCursor` (string|null)
- `nextOffset`
- `ok` (boolean)
- `syncStatus` (string)

### `preview_booking` (~128 tokens)

Review a booking before confirming

Validate guest details and the selected time without booking or sending email. Show the returned summary to the guest and ask for explicit approval. Then call book_meeting with the returned normalized booking, requestId and confirmationToken.

Input parameters:

- `email` (string, required)
- `fieldAnswers` (object)
- `meetingType` (string)
- `name` (string, required)
- `purpose` (string)
- `requestId` (string): Reuse the ID returned by preview_booking for retries.
- `slotId` (string, required)
- `slug` (string, required)
- `timezone` (string)

Output parameters:

- `code` (string)
- `message` (string)
- `nextCursor` (string|null)
- `nextOffset`
- `ok` (boolean)
- `syncStatus` (string)

### `book_meeting` (~150 tokens)

Confirm a reviewed meeting

Creates a booking and sends invitations. Only call after the guest explicitly approves preview_booking. Copy the preview's booking fields and confirmationToken unchanged. Reuse requestId and token on network retries; never claim notifications are delivered until syncStatus is ready.

Input parameters:

- `confirmationToken` (string, required)
- `confirmed` (boolean, required)
- `email` (string, required)
- `fieldAnswers` (object)
- `meetingType` (string)
- `name` (string, required)
- `purpose` (string)
- `requestId` (string): Reuse the ID returned by preview_booking for retries.
- `slotId` (string, required)
- `slug` (string, required)
- `timezone` (string)

Output parameters:

- `code` (string)
- `message` (string)
- `nextCursor` (string|null)
- `nextOffset`
- `ok` (boolean)
- `syncStatus` (string)

### `get_booking` (~44 tokens)

Check a booking

Read a booking using its private manage-link token. Includes meeting-link synchronization status. Treat this token as a password; do not share it publicly.

Input parameters:

- `token` (string, required)

Output parameters:

- `code` (string)
- `message` (string)
- `nextCursor` (string|null)
- `nextOffset`
- `ok` (boolean)
- `syncStatus` (string)

### `cancel_booking` (~49 tokens)

Cancel a booking

Cancel using a private manage token. Ask the guest for explicit approval first; this sends cancellation notifications.

Input parameters:

- `confirmed` (boolean, required)
- `reason` (string)
- `token` (string, required)

Output parameters:

- `code` (string)
- `message` (string)
- `nextCursor` (string|null)
- `nextOffset`
- `ok` (boolean)
- `syncStatus` (string)

### `reschedule_booking` (~75 tokens)

Reschedule a booking

Move a booking using its private manage token and a fresh slot ID from list_available_times. Ask for explicit approval first. The original booking stays intact if the new time cannot be reserved.

Input parameters:

- `confirmed` (boolean, required)
- `reason` (string)
- `slotId` (string, required)
- `token` (string, required)

Output parameters:

- `code` (string)
- `message` (string)
- `nextCursor` (string|null)
- `nextOffset`
- `ok` (boolean)
- `syncStatus` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/makloai-yoya-booking/api-mcp-book#diagnostics

## Score history

- 2026-09-20: 72
- 2026-09-19: 72
- 2026-09-18: 71
- 2026-09-17: 71
- 2026-09-16: 70
- 2026-09-15: 70
- 2026-09-14: 69
- 2026-09-13: 70
- 2026-09-12: 69
- 2026-09-11: 69
- 2026-09-10: 68
- 2026-09-09: 68
- 2026-09-08: 67
- 2026-09-07: 67
- 2026-09-06: 66
- 2026-09-05: 66
- 2026-09-04: 65
- 2026-09-03: 65
- 2026-09-02: 64
- 2026-09-01: 64

## Common questions

### What is the Yoya Booking MCP server?

Yoya Booking is an MCP server listed in the public MCP registry as io.github.makloai/yoya-booking. Book meetings on a host's real availability. No auth - mirrors their public Yoya page. This page covers its hosted endpoint (https://yoya.ai/api/mcp/book).

### Is the Yoya Booking MCP server safe to use?

Yoya Booking scores 72 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 Yoya Booking MCP server expose?

Yoya Booking exposes 7 tools: get_booking_page, list_available_times, preview_booking, book_meeting, get_booking, and 2 more. Their descriptions and schemas cost roughly 626 tokens of context every time the server is loaded.

### Does the Yoya Booking MCP server require authentication?

No. We connected to Yoya Booking without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Yoya Booking MCP server still maintained?

Yoya Booking is still listed as active in the MCP registry. We last reached this channel on 20 September 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://yoya.ai/api/mcp/book
- Website: https://yoya.ai/
- Changelog RSS feed: https://verifymcp.io/servers/makloai-yoya-booking/api-mcp-book.xml
- Changelog JSON feed: https://verifymcp.io/servers/makloai-yoya-booking/api-mcp-book.json
- HTML version of this page: https://verifymcp.io/servers/makloai-yoya-booking/api-mcp-book