Remote MCP · Endpoint

HairDora Salon Scheduling MCP server

No. HairDora Salon Scheduling answered an MCP handshake 2 hours ago.

UpLast checked 2 hours 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
115 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 15 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
2 hours agoHandshake completed115 ms
2 days agoHandshake completed221 ms
4 days agoHandshake completed252 ms
6 days agoHandshake completed200 ms
8 days agoHandshake completed157 ms
9 days agoHandshake completed486 ms
11 days agoHandshake completed381 ms
11 days agoHandshake completed205 ms
14 days agoHandshake completed120 ms
15 days agoHandshake completed1.38 s
17 days agoHandshake completed155 ms
19 days agoHandshake completed165 ms
20 days agoHandshake completed475 ms
21 days agoHandshake completed481 ms
22 days agoHandshake completed191 ms

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

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.