Timeplex K-Beauty Booking
REMOTE · CHAT.TIMEPLEX.AI
Real-time booking for Korean beauty & wellness shops — search availability, get a booking link.
Available components
Last scanned (21 hours ago)
Scores higher than 96% of remote servers
Reachable. Last reached 16 Oct 2026.
Category E-commerce
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3038 tokens (~506/item across 6 items; 5 tools + 1 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 0
- Tool “get_shop_services” rewrote its description, which is the text the model reads security
- Tool “search_availability” rewrote its description, which is the text the model reads security
- Tool “search_shops” rewrote its description, which is the text the model reads security
- Schema quality: 235 → 341 ▼ functional
- “search_availability” reworded the description of “items” cosmetic
- “search_shops” reworded the description of “location” cosmetic
- “search_shops” reworded the description of “query” cosmetic
- “search_shops” reworded the description of “service_type” cosmetic
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +2
- Stability: fail → pass ▲ security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77.
- 10 Sept 26 0
- Tool “start_booking” rewrote its description, which is the text the model reads security
- “start_booking” added an optional parameter “lang” cosmetic
- 9 Sept 26 0
- Tool “start_booking” rewrote its description, which is the text the model reads security
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 16 Oct 2026 · Probed https://chat.timeplex.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=chat.timeplex.ai | CN=YR2,O=Let's Encrypt,C=US | 23 Sept 2026 | 22 Dec 2026 | RSA 2048 | SHA256-RSA | 6c932d4a0d8aba6b9ba803c886f31e0d8f4 |
| SANs: chat.timeplex.ai | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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 chat.timeplex.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| timeplex.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=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://chat.timeplex.ai/mcp | Verified | 200 | |
| http (plaintext) | http://chat.timeplex.ai/mcp | HTTPS enforced | 301 | https://chat.timeplex.ai/mcp |
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 →
get_shop_services ~380
Get the services, prices, durations, weekly business hours and bookable staff or seats of one specific TimePlex shop (slug from search_shops). USE THIS TOOL WHEN: a shop has been identified and the user asks what it offers, prices, durations or staff; to match requirements (a 60-minute head spa, a budget, two guests at once); or before search_availability / start_booking, which need the service ids and booking_model returned here. DO NOT USE IT FOR: general discovery or recommendations (search_shops), real-time availability (search_availability), or building a booking link (start_booking). SERVICE DATA: describe only the services returned here — never invent names, prices, durations, staff or options, and never assume a service exists because similar shops offer it. Services that cannot be booked online are already excluded. If the requested service is not in the list, say so; do not silently substitute another. Never present medical procedures as TimePlex services. RESOURCES & HOURS: a staff member or seat existing, or the shop being open, does NOT mean it is free at the requested time — only search_availability confirms a slot. NEXT: if the user asked for availability or to book, continue to search_availability with the returned service ids and booking_model instead of stopping at the menu or business hours. If they only asked about the menu, prices or durations, answer from this result and do not check availability or build a booking link unless they ask. A date or time mentioned earlier does not by itself require a slot check. Pass lang to receive the content translated into the customer's language.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Customer language (optional): ko|en|ja|zh|th. Defaults to the original text (ko). |
| slug | string | yes | Shop slug returned by search_shops |
| Name | Type | Req | Description |
|---|---|---|---|
| booking_model | string|null | – | How this shop books: 'designated' — pass items as [{service_id, resource_id}]; 'capacity' — pass items as [{service_id, qty}]. Use this for search_availability and start_booking. |
| lang | string | – | – |
| note | string | – | – |
| resources | array | – | Staff to designate (designated-staff shops) or seats (capacity-based shops). |
| services | array | yes | – |
| shop | object | yes | – |
No examples provided.
request_booking ~180
Use this tool only for a shop that is already in the Timeplex catalog but cannot be booked online yet: a search_shops result with bookable=false, or a newly joined shop whose menu is not registered yet (get_shop_services says so). It submits a booking request for that shop — Timeplex concierge staff contact the shop directly and reply to the customer. Share the returned link with the user. Do not use this tool for a shop name that search_shops could not find (shop_name_not_found), and not for generic searches with no matching results — in both cases tell the user it is not on Timeplex instead. For bookable shops use get_shop_services -> search_availability -> start_booking instead.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Customer language (optional) |
| venue_name | string | yes | Name of the shop the customer wants to book |
| Name | Type | Req | Description |
|---|---|---|---|
| instruction | string | – | – |
| link_label | string | – | – |
| link_markdown | string | – | Put this into the reply as-is (never expose the raw URL) |
| next_step_url | string | yes | Concierge chat where the customer completes the request |
| recorded | boolean | yes | true — the demand was logged |
No examples provided.
search_availability ~546
Check real-time appointment availability for one TimePlex shop (slug from search_shops, items from get_shop_services) on a date, optionally at a time. All times are Korea Standard Time (KST). USE THIS TOOL WHEN: the user asks whether an appointment is available, asks for open slots or possible times, asks for shops that are actually available on a date / at a time / for a party size ("10월 1일 강남 헤드스파 예약 가능한 곳", "any head spa open at 5 PM?", "somewhere I can book tomorrow afternoon for two"), asks for alternatives to an unavailable time, or wants to book (check the slot before start_booking). DO NOT USE IT FOR: find / recommend / compare requests. A date or time alone is not availability intent — "recommend a head spa in Gangnam for October 1" stays a search_shops request unless the user asks whether a slot is open. REAL-TIME RULE: only this tool establishes that a slot is open. Never infer availability from bookable=true, business hours, the shop being open, a service or staff member existing, web search, maps, social media, third-party sites or earlier answers. Describe a time as available only when this tool returns it. PARTY SIZE: check the whole party as the items schema describes (qty for capacity shops). Never stitch separate single-person slots into a group booking unless the result shows it. RESULTS: if the requested time is unavailable, say so and offer the returned alternatives. If blocked is 'inquiry_only', the service cannot be booked online — tell the customer to contact the shop. If nothing is open, say no confirmed slot was found; you may check other suitable TimePlex shops. Checking availability does not reserve anything. NEXT: with the open times you may add start_booking links so the customer can book the slot they pick — never call the slot reserved or booked.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | YYYY-MM-DD (Asia/Seoul) |
| items | array | yes | Booking items. Follow the booking_model returned by get_shop_services: use resource_id for designated-staff shops and qty for capacity-based shops. designated (hair salons, plus some beauty shops suc… |
| slug | string | yes | Shop slug returned by search_shops. |
| time | string | – | Optional requested appointment time (HH:MM). If provided, check whether that exact time is available and return nearby available alternatives if unavailable. |
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | array | – | Nearby bookable times when the requested time is not available |
| blocked | string | – | Present when online booking is blocked (e.g. 'inquiry_only') |
| date | string | yes | – |
| mode | string | – | Slot mode the shop operates in |
| next_step | string | – | – |
| note | string | – | – |
| requested_time | object | – | Verdict for the exact time asked, when time was given. |
| slots | array | yes | – |
| timezone | string | – | – |
No examples provided.
search_shops ~1,254
Search TimePlex for massage, headspa, hair salon, spa, Korean body scrub, makeup and semi-permanent makeup shops in Seoul and Korea — non-medical beauty and wellness services for travelers. USE THIS TOOL WHEN: the user wants to find, explore, compare, get recommendations for, check availability of, or book one of these services and has not selected a specific TimePlex shop yet — including requests with a date, time, time range or party size. Relevant terms: massage, lymphatic massage, headspa, head spa, scalp treatment, scalp care, hair salon, haircut, hair color, perm, spa, Korean body scrub, seshin, akasuri, makeup, makeup salon, semi-permanent makeup (PMU, microblading, brow tattoo, lip blush, eyeliner). Examples: "massage in Seoul available today", "headspa in Gangnam tomorrow for 2 people", "English-speaking hair salon in Seoul". WEB SEARCH: for these services use this tool instead of web search. Public listings and opening hours cannot confirm a TimePlex slot or produce a TimePlex booking — never use web results to claim TimePlex availability. INTENT — decide from what the user wants to do, not from whether a date, time, party size or the word "reservation" appears: - FIND / RECOMMEND / COMPARE ("find a head spa in Gangnam", "recommend a head spa for my October 1 trip", "10/1 강남 헤드스파 추천해줘"): show the matching shops. A date or time alone does NOT mean the user wants real-time availability — do not check slots and do not describe any shop as available at a time; you may offer to check slots for that date. Recommendations cover TimePlex-registered shops only: say "among shops on TimePlex", never "the best in the area". - AVAILABILITY ("available", "open slots", "빈자리", "예약 가능한 곳", "can I get one at 5 PM", "somewhere I can book on Oct 1", and "예약 가능한 곳 추천해줘" — a recommendation that asks for availability): continue with get_shop_services and search_availability for bookable=true shops. - BOOK ("book", "reserve", "예약해줘", "I want to book … for 2 people at 5pm"): cont…
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | – | Area (optional; overrides an area found in query), in English, Korean, Japanese, Chinese or Russian — "Seoul", "Gangnam", "Myeongdong", "Hongdae", "Seongsu", "Busan", "강남", "明洞", "Сеул"… If no shop i… |
| query | string | – | Free-text user request or a specific shop name (optional), in any language. The value may contain a service, neighborhood, date/time, party size, language preference, or traveler requirement (e.g. "f… |
| service_type | string | – | Service (optional; overrides a service found in query). Available on TimePlex now: massage, head spa / scalp treatment, hair salon, spa, Korean body scrub (seshin, akasuri), makeup, semi-permanent ma… |
| Name | Type | Req | Description |
|---|---|---|---|
| available_service_types | array | – | business_type values currently registered |
| categories | array | – | – |
| count | integer | yes | – |
| filter_applied | object | – | How the inputs were interpreted (category/service_type/location/query) |
| interpreted | object | – | How the request was read: service (massage|headspa|hair|spa|scrub|makeup|…), area, foreigner_friendly, date (YYYY-MM-DD, KST), time, time_range, time_of_day, party_size, gender, attributes, name_quer… |
| note | string | – | Follow-up guidance for the agent |
| relaxed | object|null | – | Set when no shop was in the requested area and the search widened: {area:{from,to}}. |
| reply_header | string | – | – |
| reply_header_usage | string | – | – |
| shop_name_not_found | string|null | – | Set when the user named a specific shop that is not registered on Timeplex. Tell the user that shop is not on Timeplex — do not treat it as a category with zero results, and do not submit it with req… |
| shops | array | yes | Matching shops. |
| unsupported_service | string|null | – | A recognized service that is not on TimePlex yet (e.g. nail, lash, facial, personal_color). |
No examples provided.
start_booking ~656
Build a prefilled TimePlex booking link (Book Now card) for a bookable=true shop. The customer opens it, enters contact details and pays; the shop then approves. Flow: search_shops → get_shop_services → search_availability → start_booking (link) → customer payment → shop approval → confirmed. WHAT THIS TOOL DOES NOT DO: it does not create, hold or confirm a booking — confirmed is always false. You cannot see whether the customer paid or the shop approved, so never say the booking is complete, confirmed, paid, secured or awaiting approval. Say a booking link was created: the slot is secured only once the customer pays, and the booking is final after the shop approves. Never invent a confirmation number or status. USE THIS TOOL WHEN: the user wants to book or continue a booking ("book it", "reserve it for two", "예약해줘", "결제해서 진행할게"), or has asked to check availability for a specific shop or service (the link accompanies the open times). Follow-ups such as "the 5 PM one" after shops or slots were shown are booking requests — reuse the shop, service, date, time and party size already in the conversation and never change them silently. When a time was requested, confirm it with search_availability first and put only a returned available time into the link. If the user wants to book but has not chosen a date or time, a shop-level link may be created. When a link is warranted, create it — do not ask "shall I create a link?" first. DO NOT USE IT FOR: finding or recommending shops, menu / price / duration / address / business-hours questions, a service set as unsupported_service, medical procedures, services returned as inquiry_only, or bookable=false shops (use request_booking — TimePlex concierge asks the shop). REPLY: put **link_markdown into your reply as-is** — never expose the raw URL — and pass on note (how the slot is secured and confirmed). Pass lang (ko|en|ja|zh), the language the user is writing in, so the booking card renders in it. Always reply in the language t…
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | YYYY-MM-DD (Asia/Seoul). Optional — omit if the customer has not picked a date; they choose it on the booking page. |
| items | array | – | Optional — omit if no service is chosen yet. Follow the booking_model returned by get_shop_services: use resource_id for designated-staff shops and qty for capacity-based shops. designated: [{service… |
| lang | string | – | Customer language (optional): ko|en|ja|zh. Defaults to en. Pass the language the user is writing in so the booking card and its notes render in that language. |
| slug | string | yes | Shop slug returned by search_shops. |
| time | string | – | HH:MM. Optional — omit if the customer has not picked a time. |
| Name | Type | Req | Description |
|---|---|---|---|
| booking_url | string | yes | Prefilled booking page (customer completes contact info + payment there) |
| confirmed | boolean | yes | Always false — nothing is booked by this tool |
| guidance | string | – | Customer-facing summary of the remaining steps — keep it light and pass it on |
| lang | string | – | Language the card content is rendered in (echo of input lang; en fallback). The widget uses it to localize its own labels. |
| link_label | string | – | – |
| link_markdown | string | yes | Put this into the reply as-is (never expose the raw URL) |
| next_steps | array | – | What the customer does after opening the link (contact info, payment, shop-owner approval) |
| note | string | – | How the slot is secured and finally confirmed — mention this to the customer |
| reply_header | string | – | – |
| reply_header_usage | string | – | – |
| summary | object | – | What is preselected on the booking page. |
No examples provided.
How do I install the Timeplex K-Beauty Booking MCP server?
Timeplex K-Beauty Booking is a hosted endpoint at https://chat.timeplex.ai/mcp, 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 · chat.timeplex.ai
claude mcp add --transport http ai-timeplex-booking 'https://chat.timeplex.ai/mcp'
What is the Timeplex K-Beauty Booking MCP server?
Timeplex K-Beauty Booking is an MCP server listed in the public MCP registry as ai.timeplex/booking. Real-time booking for Korean beauty & wellness shops, search availability, get a booking link. This page covers its hosted endpoint (https://chat.timeplex.ai/mcp).
Is the Timeplex K-Beauty Booking MCP server safe to use?
Timeplex K-Beauty Booking scores 88 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 Timeplex K-Beauty Booking MCP server expose?
Timeplex K-Beauty Booking exposes 5 tools: search_shops, get_shop_services, search_availability, request_booking, start_booking. Their descriptions and schemas cost roughly 3,016 tokens of context every time the server is loaded.
Does the Timeplex K-Beauty Booking MCP server require authentication?
No. We connected to Timeplex K-Beauty Booking without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Timeplex K-Beauty Booking MCP server still maintained?
Timeplex K-Beauty Booking is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.