# HairDora Salon Scheduling (remote · mcp.hairdora.com)

See your salon's free slots, appointments, stylists, services, clients, quotes and payments.

- Trust score: 87/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `mcp.hairdora.com`: 87/100 (this document), [markdown](https://verifymcp.io/servers/com-hairdora-hairdora/mcp.md), [page](https://verifymcp.io/servers/com-hairdora-hairdora/mcp)

## Channel facts

- Endpoint: `https://mcp.hairdora.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.1.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 92/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - 67% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3865 tokens (~193/item across 20 items; 14 tools + 6 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the HairDora Salon Scheduling MCP server?

HairDora Salon Scheduling is a hosted endpoint at https://mcp.hairdora.com/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.

### Claude

```bash
claude mcp add --transport http com-hairdora-hairdora 'https://mcp.hairdora.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-hairdora-hairdora": {
      "url": "https://mcp.hairdora.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-hairdora-hairdora": {
      "type": "http",
      "url": "https://mcp.hairdora.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-hairdora-hairdora]
url = "https://mcp.hairdora.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-hairdora-hairdora": {
      "type": "remote",
      "url": "https://mcp.hairdora.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-hairdora-hairdora --url 'https://mcp.hairdora.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-hairdora-hairdora:
    url: "https://mcp.hairdora.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-hairdora-hairdora": {
      "Transport": "http",
      "Url": "https://mcp.hairdora.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-hairdora-hairdora -t streamable-http -u 'https://mcp.hairdora.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-hairdora-hairdora": {
      "type": "http",
      "url": "https://mcp.hairdora.com/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-15 (score 87, +1)

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

### 2026-10-13 (score 86, +1)

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

### 2026-10-12 (score 85, +1)

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

### 2026-10-10 (score 84, +1)

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

### 2026-10-07 (score 83, +2)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 40. That category is still filling its 30-day observation window: 9 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.

### 2026-10-03 (score 81, −1)

- [functional regression] Schema quality: 100% → 67%
- [functional improvement] Schema quality: 222 → 192
- [functional] New resource “hairdora-workspace”
- [functional] New resource “hairdora-workspace-v1”
- [functional] New tool “open_hairdora”

### 2026-09-30 (score 82, +1)

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

### 2026-09-28 (score 81, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (14)

### `list_salons` (~64 tokens)

List your salons

Use this when someone asks which hair salons they run in HairDora, or a salon's id is needed. Returns up to 100 salons with id, name, currency, default language and last edit time. Not for a salon's address, phone or opening hours.

Output parameters:

- `count` (integer)
- `hasMore` (boolean): True when the organization has more than 100 salons
- `salons` (array): Salons in the signed-in organization. Contact, address, payment, organization and configuration fields are excluded.

### `get_salon` (~84 tokens)

Get salon details and opening hours

Use this when someone asks for one salon's opening hours, address, phone, website, timezone or default appointment length. Returns that salon's business settings with up to 14 opening-hour rows, Monday first. Not for free booking slots.

Input parameters:

- `salonId` (string, required): Id of one of the user's salons, as the salon list returns it (24 lowercase hex characters)

Output parameters:

- `salon`: Business settings of the salon; null when not found. Organization ids, payment configuration, credentials, integrations, reminders, staff data and internal metadata are excluded.
- `status` (string)

### `get_salon_availability` (~100 tokens)

Find free appointment slots

Use this when someone asks when their hair salon has free appointment slots or the next opening. Returns, per day, how many online-booking slots are open plus the first start and last end time, for the next 14 days that have openings (no client or stylist names). Not for making a booking.

Input parameters:

- `salonId` (string, required): Id of one of the user's salons, as the salon list returns it (24 lowercase hex characters)

Output parameters:

- `days` (array): One row per day with open online-booking slots inside the salon's booking window, in date order. Slot counts and times only; who holds a booked time is never exposed.
- `status` (string)

### `list_providers` (~88 tokens)

List stylists who take appointments

Use this when someone asks which stylists or hairdressers work at their salon or can be booked. Returns up to 100 hairdresser display names from the organization that owns the salon (no contact details or schedules). Not for stylists' days off.

Input parameters:

- `salonId` (string, required): Id of one of the user's salons, as the salon list returns it (24 lowercase hex characters)

Output parameters:

- `count` (integer)
- `hasMore` (boolean)
- `providers` (array): Display names of organization members with the hairdresser role; roles are organization-wide, not per salon. Staff ids, contact details, avatar URLs, role records, schedules and organization data are…
- `status` (string)

### `list_clients` (~134 tokens)

Look up salon clients

Use this when someone asks who their clients are, or needs a client id to look up that person's appointments, payments or quotes. Returns up to 100 clients (20 by default) across all the user's salons, or just one, with id, name, salon and last edit time, in no particular order and without a name search. Not for a client's email, phone or notes.

Input parameters:

- `limit` (integer): Maximum number of clients to return (default 20, maximum 100)
- `salonId` (string): Only clients of this salon, by an id from the user's salon list; every salon when absent

Output parameters:

- `clients` (array): Clients with the ids needed to look up their bookings, payments and quotes. Email, phone, address, operator notes, service and colour history, organization data and other profile fields are excluded.
- `count` (integer)
- `hasMore` (boolean)

### `get_client` (~78 tokens)

Get client details

Use this when someone asks about one salon client, such as their preferred language or which salon they belong to. Returns the client's name, salon, language and last edit time. Not for the client's email, phone or booking history.

Input parameters:

- `clientId` (string, required): Id of one client, as the client list returns it (24 lowercase hex characters)

Output parameters:

- `client`: Name, salon, language and edit time only; null when not found. Email, phone, address, operator notes, service and colour history, organization data and other profile fields are excluded.
- `status` (string)

### `list_appointments` (~194 tokens)

List salon appointments

Use this when someone asks how many appointments are booked on a day or in a period, how many were canceled or no-shows, or when a client is booked. Returns appointments across all the user's salons, or just one, with id, client and salon ids, times and status for any date window, latest first, up to 100. Not for the services inside an appointment.

Input parameters:

- `clientId` (string): Only appointments of this client, by an id from the client list
- `endTime` (string): Only appointments ending before this ISO 8601 time
- `limit` (integer): Maximum number of appointments to return (default 20, maximum 100)
- `salonId` (string): Only appointments at this salon, by an id from the user's salon list; every salon when absent
- `startTime` (string): Only appointments starting at or after this ISO 8601 time

Output parameters:

- `appointments` (array): Bookings, latest start first. Free-text notes, reminders, contact details, organization data and payment details are excluded.
- `count` (integer)
- `hasMore` (boolean)

### `get_appointment` (~83 tokens)

Get appointment details

Use this when someone asks what services a specific appointment includes, their prices, or the appointment's status. Returns one appointment's client and salon ids, times, status and up to 50 booked services with prices. Not for finding bookings by date.

Input parameters:

- `appointmentId` (string, required): Id of one appointment, as the appointment list returns it (24 lowercase hex characters)

Output parameters:

- `appointment`: One booking with up to 50 booked services and their prices; null when not found. Free-text notes, reminders, contact details, organization data and payment data are excluded.
- `status` (string)

### `list_calendar_events` (~172 tokens)

List closures, days off and blocked time

Use this when someone asks when their salon is closed or has extra opening hours, or when a stylist or chair is blocked for holidays, vacations, sick days, training or meetings. Returns blocks and extra openings with salon, type, scope, effect, all-day flag and times for all salons unless one is given, earliest first (no titles or notes). Not for client appointments.

Input parameters:

- `endTime` (string): Only events ending before this ISO 8601 time
- `limit` (integer): Maximum number of calendar events to return (default 20, maximum 100)
- `salonId` (string): Only blocks for this salon, by an id from the user's salon list; every salon when absent
- `startTime` (string): Only events starting at or after this ISO 8601 time

Output parameters:

- `count` (integer)
- `events` (array): Closures, days off and extra openings, earliest first. Free-text titles and notes, chair ids, staff ids, organization data and private reasons are excluded.
- `hasMore` (boolean)

### `list_services` (~122 tokens)

Look up service prices

Use this when someone asks what their salon charges for a cut, colour, blow-dry or other service, or what services it offers. Returns services with id, name, price and salon for all their salons unless one is given, 50 by default and up to 100. Not for what a particular client had done.

Input parameters:

- `limit` (integer): Maximum number of services to return (default 50, maximum 100)
- `salonId` (string): Only services of this salon, by an id from the user's salon list; every salon when absent

Output parameters:

- `count` (integer)
- `hasMore` (boolean)
- `services` (array): Services the salon offers, with prices. Internal metadata and organization data are excluded.

### `list_payments` (~192 tokens)

List salon payments

Use this when someone asks what payments their salon took, whether a client paid, or how much came in over a period. Returns payment records with id, client and salon ids, date, amount, currency and status for any date window and all salons unless one is given, newest first, up to 100 (no card details). Not for charging or refunding a client.

Input parameters:

- `clientId` (string): Only payments from this client, by an id from the client list
- `endTime` (string): Only payments ending before this ISO 8601 time
- `limit` (integer): Maximum number of payments to return (default 20, maximum 100)
- `salonId` (string): Only payments at this salon, by an id from the user's salon list; every salon when absent
- `startTime` (string): Only payments starting at or after this ISO 8601 time

Output parameters:

- `count` (integer)
- `hasMore` (boolean)
- `payments` (array): Payment records, newest first; this tool cannot charge, refund or move funds. Cardholder data, processor and customer ids, credentials, errors, discounts, staff commission splits, operator notes and…

### `list_quotes` (~217 tokens)

List client quotes

Use this when someone asks about price quotes given to salon clients, such as which are pending, approved or rejected. Returns quotes with id, client and salon ids, status and date for all salons unless one is given, newest first, up to 100; the status filter applies within that page. Not for quote amounts or line items.

Input parameters:

- `clientId` (string): Only quotes for this client, by an id from the client list
- `endTime` (string): Only quotes ending before this ISO 8601 time
- `limit` (integer): Maximum number of quotes to return (default 20, maximum 100)
- `salonId` (string): Only quotes from this salon, by an id from the user's salon list; every salon when absent
- `startTime` (string): Only quotes starting at or after this ISO 8601 time
- `status` (string): Only quotes with this status: DRAFT, PENDING, REJECTED or APPROVED. Applied within the fetched page of newest quotes

Output parameters:

- `count` (integer)
- `hasMore` (boolean)
- `quotes` (array): Quotes, newest first. Free-text notes, quoted line details and amounts, discounts, contact details and organization data are excluded.

### `show_salon_overview` (~104 tokens)

Show salon overview

Use this when someone wants a quick overview or dashboard of one hair salon. Returns an overview card with the salon's details, a client count, the next 8 upcoming appointments with time, status and number of services, and up to 12 services with prices (no client names or contact details). Not for one specific booking.

Input parameters:

- `salonId` (string, required): Id of one of the user's salons, as the salon list returns it (24 lowercase hex characters)

Output parameters:

- `appointmentCount` (integer)
- `appointmentCountIsLowerBound` (boolean)
- `appointments` (array): The next upcoming appointments, earliest first
- `clientCount` (integer)
- `clientCountIsLowerBound` (boolean)
- `salon`: Salon metadata; null when not found. The overview excludes client names, contact details, client and appointment ids, notes, organization data, staff ids, payment data and service history.
- `serviceCount` (integer)
- `serviceCountIsLowerBound` (boolean)
- `services` (array)

### `open_hairdora` (~69 tokens)

HairDora Salon Scheduling

Use this when someone wants to open HairDora and browse their salons, upcoming appointment previews, service prices and booking availability in an interactive sidebar. Returns up to 100 salons to start from (no client names, contact details or private notes). Not for booking, cancelling or charging for appointments.

Output parameters:

- `items` (array)
- `truncated` (boolean)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-hairdora-hairdora/mcp#diagnostics

## Score history

- 2026-10-17: 87
- 2026-10-16: 87
- 2026-10-15: 87
- 2026-10-14: 86
- 2026-10-13: 86
- 2026-10-12: 85
- 2026-10-10: 84
- 2026-10-07: 83
- 2026-10-04: 81
- 2026-10-03: 81
- 2026-10-02: 82
- 2026-10-01: 82
- 2026-09-30: 82
- 2026-09-29: 81
- 2026-09-28: 81
- 2026-09-27: 80
- 2026-09-26: 79
- 2026-09-25: 79

## Common questions

### What is the HairDora Salon Scheduling MCP server?

HairDora Salon Scheduling is an MCP server listed in the public MCP registry as com.hairdora/hairdora. See your salon's free slots, appointments, stylists, services, clients, quotes and payments. This page covers its hosted endpoint (https://mcp.hairdora.com/mcp).

### Is the HairDora Salon Scheduling MCP server safe to use?

HairDora Salon Scheduling scores 87 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 HairDora Salon Scheduling MCP server expose?

HairDora Salon Scheduling exposes 14 tools: list_salons, get_salon, get_salon_availability, list_providers, list_clients, and 9 more. Their descriptions and schemas cost roughly 1,701 tokens of context every time the server is loaded.

### Does the HairDora Salon Scheduling MCP server require authentication?

Yes. HairDora Salon Scheduling asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the HairDora Salon Scheduling MCP server still maintained?

HairDora Salon Scheduling is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.hairdora.com/mcp
- Website: https://www.hairdora.com/developers/#mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-hairdora-hairdora/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-hairdora-hairdora/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-hairdora-hairdora/mcp