Skip to content

Yoya Booking MCP server

io.github.makloai/yoya-bookingmakloaistreamable-httpv1.0.0Scanned

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

7 tools: 3 can delete or cancel things and 4 only read.

Tools: 3 delete, 0 irreversible, 0 write, 4 read.
  • Reads private data · 1
  • Reads text others write · 5
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Yoya Booking MCP server can do

The Yoya Booking MCP server is published by the GitHub account makloai. It has 7 tools. It can delete or cancel things (3 tools: book_meeting, cancel_booking and reschedule_booking). 4 tools only read.

1 tool reads private data (preview_booking); 5 tools bring in text other people can write (list_available_times, preview_booking, book_meeting and 2 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 21, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Deletes or cancels 3Claude Code: deny
  • book_meetingCreates a free booking or returns PAYMENT_REQUIRED with a secure payment URL for paid meetings.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Creates a free booking or returns PAYMENT_REQUIRED with a secure payment URL for paid meetings. Paid meetings are not booked until payment succeeds; show the link and never claim confirmation before that. 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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
    • title: Confirm a reviewed meeting
  • cancel_bookingCancel using a private manage token.Reads text others writeNo findings

    Why it is in this group

    • The name "cancel_booking" says "cancel": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Cancel using a private manage token. Ask the guest for explicit approval first; this sends cancellation notifications.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
    • title: Cancel a booking
  • reschedule_bookingMove a booking using its private manage token and a fresh slot ID from list_available_times.Reads text others writeNo findings

    Why it is in this group

    • The name "reschedule_booking" says "reschedule": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
    • title: Reschedule a booking
Only reads 4Show 4 read-only tools
  • get_bookingRead a booking using its private manage-link token.No findings

    Why it is in this group

    • The name "get_booking" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Check a booking
  • get_booking_pageRead a public Yoya booking link or slug.No findings

    Why it is in this group

    • The name "get_booking_page" says "get": a word for reading.
    Description, as the server wrote it
    Read a public Yoya booking link or slug. Includes required guest fields and meeting options. No host account access.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Get a Yoya booking page
  • list_available_timesFind up to 10 times (max 50), labeled in the guest's IANA timezone.Reads text others writeNo findings

    Why it is in this group

    • The name "list_available_times" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • title: Find available meeting times
  • preview_bookingValidate guest details and the selected time without booking or sending email.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "preview_booking" says "preview": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "validate" and "email": it reads mail.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "validate" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • title: Review a booking before confirming

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write5
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:07 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://yoya.ai/.well-known/oauth-protected-resource
Authorization servers
https://yoya.ai/api/auth
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 destructive). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://yoya.ai/api/mcp/book: tools/list returned 7 tools to an anonymous client, including book_meeting (destructive), cancel_booking (destructive), reschedule_booking (destructive)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools7 changed.~7 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http yoya-booking https://yoya.ai/api/mcp/book
claude mcp add --transport http yoya-booking https://yoya.ai/api/mcp/book

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__yoya-booking__get_booking_page",
      "mcp__yoya-booking__list_available_times",
      "mcp__yoya-booking__preview_booking",
      "mcp__yoya-booking__get_booking"
    ],
    "ask": [],
    "deny": [
      "mcp__yoya-booking__book_meeting",
      "mcp__yoya-booking__cancel_booking",
      "mcp__yoya-booking__reschedule_booking"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as yoya-booking. Review it before you use it.

Capability tags behind 5 rules
  • mcp__yoya-booking__list_available_times untrusted-input
  • mcp__yoya-booking__preview_booking private-data, untrusted-input
  • mcp__yoya-booking__book_meeting untrusted-input
  • mcp__yoya-booking__cancel_booking untrusted-input
  • mcp__yoya-booking__reschedule_booking untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.makloai/yoya-booking/verify?hash=10f27060774731a823ca288d35c46f0522c7db56b12b605df115adae76bd03b9" | jq -e '.changed == false'

Pinned hash 10f270607747, from Nov 21, 2026, 00:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.makloai/yoya-booking/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.makloai/yoya-booking
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.makloai/yoya-booking.svg)](https://radar.anlyon.com/servers/io.github.makloai/yoya-booking)

Source: MCP Registry. Synced Oct 21, 2026, 18:38 UTC.

Yoya Booking MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Yoya Booking MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Yoya Booking MCP server delete data?

Yes. 3 tools can delete, cancel or revoke something: book_meeting, cancel_booking and reschedule_booking.

Can the Yoya Booking MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Yoya Booking MCP server have?

7 tools: 3 destructive, 4 read. book_meeting, cancel_booking, reschedule_booking, get_booking_page, list_available_times, preview_booking and get_booking.

Does the Yoya Booking MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Yoya Booking MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Yoya Booking MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 21, 2026. Every change is on this page and in its Atom feed.