Yoya Booking
REMOTE · YOYA.AI · SCANNED SEP 20
Book meetings on a host's real availability. No auth - mirrors their public Yoya page.
Available components
Recent critical change
Authorization (14 Sept 2026). See the changelog before you install this server.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (book_meeting). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 643 tokens (~80/item across 8 items; 7 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management51
- Stability check failed: schema churn in the 19 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 3 additions. See how to fix → Fail
Tool Coverage73
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 6% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
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.
remote · yoya.ai
claude mcp add --transport http makloai-yoya-booking 'https://yoya.ai/api/mcp/book'
{
"mcpServers": {
"makloai-yoya-booking": {
"url": "https://yoya.ai/api/mcp/book"
}
}
} {
"servers": {
"makloai-yoya-booking": {
"type": "http",
"url": "https://yoya.ai/api/mcp/book"
}
}
} [mcp_servers.makloai-yoya-booking] url = "https://yoya.ai/api/mcp/book"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"makloai-yoya-booking": {
"type": "remote",
"url": "https://yoya.ai/api/mcp/book",
"enabled": true
}
}
} openclaw mcp add makloai-yoya-booking --url 'https://yoya.ai/api/mcp/book' --transport streamable-http
mcp_servers:
makloai-yoya-booking:
url: "https://yoya.ai/api/mcp/book" {
"McpServers": {
"makloai-yoya-booking": {
"Transport": "http",
"Url": "https://yoya.ai/api/mcp/book"
}
}
} assistant mcp add makloai-yoya-booking -t streamable-http -u 'https://yoya.ai/api/mcp/book'
{
"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.
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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 44 to 48.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 38 to 41.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 31 to 34.
- 14 Sept 26 −1
- Authorization: unverified → fail ▼ critical
- 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 security
- Tool coverage: 42% → 6% ▼ functional
- “book_meeting” added a required parameter “confirmationToken”, so existing callers break ▼ functional
- “book_meeting” added a required parameter “confirmed”, so existing callers break ▼ functional
- Schema quality: 109 → 80 ▲ functional
- Tool “book_meeting” now declares an output schema ▲ functional
- Tool “get_booking” now declares an output schema ▲ functional
- Tool “get_booking_page” now declares an output schema ▲ functional
- 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” functional
- “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 cosmetic
- 13 Sept 26 +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.
- 11 Sept 26 +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.
- 9 Sept 26 +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.
- 7 Sept 26 +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.
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 20 Sept 2026 · Probed https://yoya.ai/api/mcp/book
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=yoya.ai | CN=YR1,O=Let's Encrypt,C=US | 6 Sept 2026 | 5 Dec 2026 | RSA 2048 | SHA256-RSA | 613476070f922dbb175aa9f989b51a2380b |
| SANs: yoya.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of yoya.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| yoya.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | frame-ancestors 'none' |
| x-frame-options | DENY |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://yoya.ai/api/mcp/book | Verified | 200 | |
| http (plaintext) | http://yoya.ai/api/mcp/book | HTTPS enforced | 308 | https://yoya.ai/api/mcp/book |
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 →
book_meeting Confirm a reviewed meeting ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmationToken | string | yes | – |
| confirmed | boolean | yes | – |
| string | yes | – | |
| fieldAnswers | object | – | – |
| meetingType | string | – | – |
| name | string | yes | – |
| purpose | string | – | – |
| requestId | string | – | Reuse the ID returned by preview_booking for retries. |
| slotId | string | yes | – |
| slug | string | yes | – |
| timezone | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | – |
| message | string | – | – |
| nextCursor | string|null | – | – |
| nextOffset | – | – | – |
| ok | boolean | yes | – |
| syncStatus | string | – | – |
No examples provided.
cancel_booking Cancel a booking ~49
Cancel using a private manage token. Ask the guest for explicit approval first; this sends cancellation notifications.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | yes | – |
| reason | string | – | – |
| token | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | – |
| message | string | – | – |
| nextCursor | string|null | – | – |
| nextOffset | – | – | – |
| ok | boolean | yes | – |
| syncStatus | string | – | – |
No examples provided.
get_booking Check a booking ~44
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.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | – |
| message | string | – | – |
| nextCursor | string|null | – | – |
| nextOffset | – | – | – |
| ok | boolean | yes | – |
| syncStatus | string | – | – |
No examples provided.
get_booking_page Get a Yoya booking page ~39
Read a public Yoya booking link or slug. Includes required guest fields and meeting options. No host account access.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | – |
| message | string | – | – |
| nextCursor | string|null | – | – |
| nextOffset | – | – | – |
| ok | boolean | yes | – |
| syncStatus | string | – | – |
No examples provided.
list_available_times Find available meeting times ~141
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| from | string | – | – |
| limit | integer | – | – |
| slug | string | yes | – |
| timeOfDay | string | – | – |
| timezone | string | – | – |
| to | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | – |
| message | string | – | – |
| nextCursor | string|null | – | – |
| nextOffset | – | – | – |
| ok | boolean | yes | – |
| syncStatus | string | – | – |
No examples provided.
preview_booking Review a booking before confirming ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – | |
| fieldAnswers | object | – | – |
| meetingType | string | – | – |
| name | string | yes | – |
| purpose | string | – | – |
| requestId | string | – | Reuse the ID returned by preview_booking for retries. |
| slotId | string | yes | – |
| slug | string | yes | – |
| timezone | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | – |
| message | string | – | – |
| nextCursor | string|null | – | – |
| nextOffset | – | – | – |
| ok | boolean | yes | – |
| syncStatus | string | – | – |
No examples provided.
reschedule_booking Reschedule a booking ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | yes | – |
| reason | string | – | – |
| slotId | string | yes | – |
| token | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | – |
| message | string | – | – |
| nextCursor | string|null | – | – |
| nextOffset | – | – | – |
| ok | boolean | yes | – |
| syncStatus | string | – | – |
No examples provided.
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.