HairDora Salon Scheduling
REMOTE · MCP.HAIRDORA.COM
See your salon's free slots, appointments, stylists, services, clients, quotes and payments.
Available components
Last scanned (29 minutes ago)
Scores higher than 95% of remote servers
Reachable. Last reached 17 Oct 2026.
Category CRM and Sales
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 Security92
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- 67% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 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
- 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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 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.
- 15 Oct 26 +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.
- 13 Oct 26 +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.
- 12 Oct 26 +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.
- 10 Oct 26 +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.
- 7 Oct 26 +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.
- 3 Oct 26 −1
- Schema quality: 100% → 67% ▼ functional
- Schema quality: 222 → 192 ▲ functional
- New resource “hairdora-workspace” functional
- New resource “hairdora-workspace-v1” functional
- New tool “open_hairdora” functional
- 30 Sept 26 +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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 17 Oct 2026 · Probed https://mcp.hairdora.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.hairdora.com | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 3 Sept 2026 | 19 Mar 2027 | RSA 2048 | SHA256-RSA | a8be5d56f3f8800cfe769108771c78a |
| SANs: *.hairdora.com, hairdora.com | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.hairdora.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| hairdora.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="hairdora", resource_metadata="https://mcp.hairdora.com/.well-known/oauth-protected-resource", error="invalid_token", error_description="missing Bearer token"
Bearer realm="hairdora", resource_metadata="https://mcp.hairdora.com/.well-known/oauth-protected-resource", error="invalid_token", error_description="missing Bearer token"Protected resource metadata
| Document | https://mcp.hairdora.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.hairdora.com |
| Authorisation server | https://api.authrice.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.hairdora.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.hairdora.com/mcp | HTTPS enforced |
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_appointment Get appointment details ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| appointmentId | string | yes | Id of one appointment, as the appointment list returns it (24 lowercase hex characters) |
| Name | Type | Req | Description |
|---|---|---|---|
| appointment | – | yes | 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 | yes | – |
No examples provided.
get_client Get client details ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| clientId | string | yes | Id of one client, as the client list returns it (24 lowercase hex characters) |
| Name | Type | Req | Description |
|---|---|---|---|
| client | – | yes | 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 | yes | – |
No examples provided.
get_salon Get salon details and opening hours ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| salonId | string | yes | Id of one of the user's salons, as the salon list returns it (24 lowercase hex characters) |
| Name | Type | Req | Description |
|---|---|---|---|
| salon | – | yes | 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 | yes | – |
No examples provided.
get_salon_availability Find free appointment slots ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| salonId | string | yes | Id of one of the user's salons, as the salon list returns it (24 lowercase hex characters) |
| Name | Type | Req | Description |
|---|---|---|---|
| days | array | yes | 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 | yes | – |
No examples provided.
list_appointments List salon appointments ~194
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| appointments | array | yes | Bookings, latest start first. Free-text notes, reminders, contact details, organization data and payment details are excluded. |
| count | integer | yes | – |
| hasMore | boolean | yes | – |
No examples provided.
list_calendar_events List closures, days off and blocked time ~172
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| events | array | yes | 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 | yes | – |
No examples provided.
list_clients Look up salon clients ~134
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| clients | array | yes | 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 | yes | – |
| hasMore | boolean | yes | – |
No examples provided.
list_payments List salon payments ~192
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| hasMore | boolean | yes | – |
| payments | array | yes | 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… |
No examples provided.
list_providers List stylists who take appointments ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| salonId | string | yes | Id of one of the user's salons, as the salon list returns it (24 lowercase hex characters) |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| hasMore | boolean | yes | – |
| providers | array | yes | 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 | yes | – |
No examples provided.
list_quotes List client quotes ~217
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| hasMore | boolean | yes | – |
| quotes | array | yes | Quotes, newest first. Free-text notes, quoted line details and amounts, discounts, contact details and organization data are excluded. |
No examples provided.
list_salons List your salons ~64
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| hasMore | boolean | yes | True when the organization has more than 100 salons |
| salons | array | yes | Salons in the signed-in organization. Contact, address, payment, organization and configuration fields are excluded. |
No examples provided.
list_services Look up service prices ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| hasMore | boolean | yes | – |
| services | array | yes | Services the salon offers, with prices. Internal metadata and organization data are excluded. |
No examples provided.
open_hairdora HairDora Salon Scheduling ~69
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| truncated | boolean | yes | – |
No examples provided.
show_salon_overview Show salon overview ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| salonId | string | yes | Id of one of the user's salons, as the salon list returns it (24 lowercase hex characters) |
| Name | Type | Req | Description |
|---|---|---|---|
| appointmentCount | integer | yes | – |
| appointmentCountIsLowerBound | boolean | yes | – |
| appointments | array | yes | The next upcoming appointments, earliest first |
| clientCount | integer | yes | – |
| clientCountIsLowerBound | boolean | yes | – |
| salon | – | yes | 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 | yes | – |
| serviceCountIsLowerBound | boolean | yes | – |
| services | array | yes | – |
No examples provided.
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.
remote · mcp.hairdora.com
claude mcp add --transport http com-hairdora-hairdora 'https://mcp.hairdora.com/mcp'
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.