Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

booboooking Appointment Booking

REMOTE · MCP.BOOBOOOKING.COM

Book appointments with service providers on booboooking.com — no token required.

68 Trust /100

Last scanned (20 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Productivity and Notes

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1180 tokens (~196/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +1

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

  • 18 Nov 26 +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.

  • 17 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 16 Nov 26 66

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://mcp.booboooking.com

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.booboooking.com CN=YR1,O=Let's Encrypt,C=US 19 Oct 2026 17 Jan 2027 RSA 2048 SHA256-RSA 5f732d10a571f8e3cee3ee48f2fd410f393
SANs: mcp.booboooking.com
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 mcp.booboooking.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
booboooking.com. No DS 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=31536000; includeSubDomains
content-security-policy default-src 'self' https://reservoprix.storage.googleapis.com https://storage.googleapis.com; script-src 'self' 'nonce-ikDFe2v3PxYxIH60' https://reservoprix.lm.r.appspot.com https://accounts.google.com https://www.googletagmanager.com https://reservoprix.storage.googleapis.com https://storage.googleapis.com https://spocont.com https://hiranytu.hu https://aktualis.info https://hungarian.news https://booboooking.com https://ekkor.hu https://karfelmero.hu https://cdn.jsdelivr.net https://maps.googleapis.com https://maps.gstatic.com; style-src 'self' 'unsafe-inline' https://fonts.gstatic.com https://fonts.googleapis.com https://reservoprix.storage.googleapis.com https://spocont.com https://hiranytu.hu https://aktualis.info https://hungarian.news https://booboooking.com https://ekkor.hu https://karfelmero.hu https://reservoprix.lm.r.appspot.com; img-src 'self' data: https://reservoprix.storage.googleapis.com https://storage.googleapis.com https://lh3.googleusercontent.com https://maps.googleapis.com https://maps.g
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.booboooking.com Verified 200
http (plaintext) http://mcp.booboooking.com HTTPS enforced 301 https://mcp.booboooking.com/
MCP tools · 6 exposed · ~879 tokens

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 →

Tool Tokens
booboooking_book ~293

Book an appointment on booboooking.com (free OR paid services — payment is always in cash at the appointment, no online payment). customer_name, customer_email and customer_phone are the customer's own details, confirmed by the user. customer_phone is validated as international E.164 (`+` and country code, no spaces or dashes, e.g. `+36201234567`); a local-format number is rejected. On success the response includes the reservation `id` and `pin`, both needed to look up or cancel the booking, and optionally `cash_due: { amount, currency }`, the amount payable in cash at the appointment.

NameTypeReqDescription
customer_emailstring–Customer email address
customer_namestring–Customer full name
customer_phonestring–Customer phone number in international E.164 format, e.g. "+36201234567" — convert local-format numbers (e.g. "06201234567") before calling this tool.
datestringyesDate in YYYYMMDD format (e.g. "20260415")
providerstringyesProvider identifier
service_idstringyesService ID from booboooking_list_services
timestringyesStart time in HH:MM format (e.g. "09:30") — use the "time" field from booboooking_check_availability results

No output schema declared.

No examples provided.

booboooking_cancel ~118

Cancel a reservation on booboooking.com. Requires the reservation_id AND pin that were returned from the original booboooking_book call — both are needed as proof of booking ownership. The pin is also in the customer's confirmation email; a wrong pin is refused.

NameTypeReqDescription
pinstringyesThe PIN returned from the original booking
providerstringyesProvider identifier (same as the one used for booking)
reservation_idstringyesThe `id` returned from the original booking (24-hex MongoDB ObjectId)

No output schema declared.

No examples provided.

booboooking_check_availability ~142

Check available time slots for a provider and service on booboooking.com. Returns available dates with slots — each slot has a "time" field (use this for booboooking_book) and a "display" field (show this to the user). Use this before booking.

NameTypeReqDescription
days_aheadnumber–How many days to check (default: 14, max: 30)
providerstringyesProvider identifier
service_idstringyesService ID from booboooking_list_services (the "id" field)
start_datestring–Start date in YYYYMMDD format (default: today)

No output schema declared.

No examples provided.

booboooking_find_next_available ~150

Search forward for the next available appointment slots for a provider and service on booboooking.com. Returns up to `count` openings sorted chronologically. Useful when you need "the next available appointment" without a specific date in mind.

NameTypeReqDescription
countinteger–Number of openings to return (default: 3, max: 10)
from_datestring–Start search from this date in YYYYMMDD format (default: today)
providerstringyesProvider identifier
search_daysinteger–Days to search ahead (default: 30, max: 60)
service_idstringyesService ID from booboooking_list_services

No output schema declared.

No examples provided.

booboooking_get_booking ~106

Retrieve a booking by its reservation ID. Requires the PIN from the original booking response to prove ownership. Returns full booking details including payment state if the reservation was created via the payment flow.

NameTypeReqDescription
pinstringyesThe PIN returned from the original booboooking_book call
providerstringyesProvider identifier (same as used for booking)
reservation_idstringyesThe reservation ID returned from booboooking_book (24-char hex MongoDB ObjectId)

No output schema declared.

No examples provided.

booboooking_list_services ~70

List available services for a provider on booboooking.com. Returns service names, IDs, duration, and price. Call this first to find the service ID needed for availability and booking.

NameTypeReqDescription
providerstringyesProvider identifier (e.g. "radnaimark", "tomi")

No output schema declared.

No examples provided.

Install

How do I install the booboooking Appointment Booking MCP server?

booboooking Appointment Booking is a hosted endpoint at https://mcp.booboooking.com/, 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 · mcp.booboooking.com

# add to Claude Code
claude mcp add --transport http com-spocont-booboooking 'https://mcp.booboooking.com/'
Common questions

What is the booboooking Appointment Booking MCP server?

booboooking Appointment Booking is an MCP server listed in the public MCP registry as com.spocont/booboooking. Book appointments with service providers on booboooking.com, no token required. This page covers its hosted endpoint (https://mcp.booboooking.com).

Is the booboooking Appointment Booking MCP server safe to use?

booboooking Appointment Booking scores 68 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 booboooking Appointment Booking MCP server expose?

booboooking Appointment Booking exposes 6 tools: booboooking_list_services, booboooking_check_availability, booboooking_book, booboooking_cancel, booboooking_find_next_available, booboooking_get_booking. Their descriptions and schemas cost roughly 879 tokens of context every time the server is loaded.

Does the booboooking Appointment Booking MCP server require authentication?

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

Is the booboooking Appointment Booking MCP server still maintained?

booboooking Appointment Booking is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the booboooking Appointment Booking MCP server?

VerifyMCP ran 13 checks on booboooking Appointment Booking, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.