Remote MCP · Endpoint

HairDora Salon Scheduling MCP server

No. HairDora Salon Scheduling answered an MCP handshake 59 minutes ago.

UpLast checked 59 minutes ago

Server URL

https://mcp.hairdora.com/mcp

The last check completed an MCP handshake.

Registry name
com.hairdora/hairdora
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
543 ms
Tools exposed
21 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
See your salon's free slots, appointments, stylists, services, clients, quotes and payments.
Listing
From the official MCP registry (active).
Recent checks of HairDora Salon Scheduling
CheckedResultHandshake
59 minutes agoHandshake completed543 ms
9 days agoHandshake completed650 ms
10 days agoHandshake completed311 ms
11 days agoHandshake completed189 ms
12 days agoHandshake completed129 ms
14 days agoHandshake completed183 ms
14 days agoHandshake completed176 ms
15 days agoHandshake completed218 ms
17 days agoHandshake completed173 ms
19 days agoHandshake completed146 ms
21 days agoHandshake completed145 ms
24 days agoHandshake completed192 ms
26 days agoHandshake completed144 ms
28 days agoHandshake completed115 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 28 responding of 28.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with HairDora Salon Scheduling and makes no claim about it beyond what these checks measured.