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.

Timeplex K-Beauty Booking

REMOTE · CHAT.TIMEPLEX.AI · SCANNED AUG 20

Real-time booking for Korean beauty & wellness shops — search availability, get a booking link.

Available components

67 Trust /100
Trust breakdown (6 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 →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability82
  • 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 1055 tokens (~150/item across 7 items; 6 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 Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 88% of tool parameters carry a description.Partial
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · chat.timeplex.ai

# add to Claude Code
claude mcp add --transport http ai-timeplex-booking https://chat.timeplex.ai/mcp
# ~/.codex/config.toml
[mcp_servers.ai-timeplex-booking]
url = "https://chat.timeplex.ai/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-timeplex-booking": {
      "type": "remote",
      "url": "https://chat.timeplex.ai/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-timeplex-booking --url https://chat.timeplex.ai/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ai-timeplex-booking:
    url: "https://chat.timeplex.ai/mcp"
// mcp.json
{
  "mcpServers": {
    "ai-timeplex-booking": {
      "type": "http",
      "url": "https://chat.timeplex.ai/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 19 Aug 26 +1
    • Stability: unverified → 0.03 functional
  • 18 Aug 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 20 Aug 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=YR1,O=Let's Encrypt,C=US 25 Jul 2026 23 Oct 2026 RSA 2048 SHA256-RSA 560341a5d5035f1e5997b15fc445036c682
SANs: chat.timeplex.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
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
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
MCP tools · 6 exposed · ~1,033 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.

Tool Tokens
get_booking_status ~70

Look up booking and payment status by reservation number, including whether it can be cancelled and the refund terms. To actually cancel, hand the customer the status_url from the response — cancelling is done there, not through this MCP. Reply in the user's language.

NameTypeReqDescription
res_nostringyesReservation number

No output schema declared.

No examples provided.

get_shop_services ~83

Get a shop's service menu (name, price, duration) and its staff/seats. Pass lang to receive the content translated into the customer's language.

NameTypeReqDescription
langstringCustomer language (optional): ko|en|ja|zh|th. Defaults to the original text (ko).
slugstringyesShop slug returned by search_shops

No output schema declared.

No examples provided.

request_booking ~79

Submit a booking request for a shop that is not onboarded to Timeplex yet (bookable=false). Timeplex concierge staff contact the shop directly and reply to the customer. Share the returned link with the user.

NameTypeReqDescription
langstringCustomer language (optional)
venue_namestringyesName of the shop the customer wants to book

No output schema declared.

No examples provided.

search_availability ~119

Check available time slots for a date. If time is given, it also judges whether that exact slot is bookable and returns nearby alternatives when it is not.

NameTypeReqDescription
datestringyesYYYY-MM-DD (Asia/Seoul)
itemsarrayyesBooking items. Hair: [{service_id, resource_id}]. Massage: [{service_id, qty}] (qty = number of people).
slugstringyes
timestringHH:MM (optional) — judge whether this exact time is bookable

No output schema declared.

No examples provided.

search_shops ~291

Find Korean beauty & wellness shops on Timeplex. bookable=true means you can check availability and book through this MCP; false means it needs request_booking (Timeplex concierge arranges it manually). Shops fall into two categories: hair (hair salons) and beauty (everything else — massage, spa, nail, skin care, waxing, scrub, etc.). Each shop result carries its category. Each result carries the shop address, so you can answer area questions ("shops in Seoul") without extra calls. Always reply to the user in the language they used, and start the reply with the response's reply_header line.

NameTypeReqDescription
locationstringArea filter (optional), in English or Korean — "Seoul", "Gangnam", "Hongdae", "Busan", "Jeju", "강남", "홍대"… Matched against the shop address. Shops with no address registered are excluded when this is…
querystringShop name, partial match (optional). If no name matches, it is also interpreted as a shop category.
service_typestringShop category (optional). Accepts broad categories ("hair", "beauty") and specific ones ("massage", "spa", "head spa", "nail", "skin care", "esthetic", "waxing", "scrub"), in English or Korean. Leave…

No output schema declared.

No examples provided.

start_booking ~391

Build a link that lets the customer continue the booking for the chosen shop, service and time. **This creates and changes nothing — it only builds a link.** So never ask "shall I create a link?"; once a shop is known, call it right away and include the link in your reply. date, time and items are all optional — **if the customer has not picked a date or time yet, still call it with just the shop** and hand over the link; they pick the rest on the booking page. Never withhold the link to ask for a date first. It books nothing — the customer must open the link, enter email, name and phone, and pay. Payment submits the booking and secures the slot; the **final confirmation comes from the shop owner** afterwards. Put **link_markdown into your reply as-is** — never expose the raw URL. Pass on guidance, and mention that the slot is not held until payment (whoever pays first gets it) and that the shop owner confirms it after that. Describe the remaining steps only as "just enter your email, name and phone, then pay" — keep it light, and always write your reply in the language the user used, starting with the response's reply_header line.

NameTypeReqDescription
datestringYYYY-MM-DD (Asia/Seoul). Optional — omit if the customer has not picked a date; they choose it on the booking page.
itemsarrayOptional — omit if no service is chosen yet. Hair: [{service_id, resource_id}] — **exactly one** (hair shops book one service at a time). Massage: [{service_id, qty}] — multiple allowed (several serv…
slugstringyes
timestringHH:MM. Optional — omit if the customer has not picked a time.

No output schema declared.

No examples provided.