Remote MCP · Endpoint

Belcome MCP server

No. Belcome answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://belcome.app/mcp

The last check completed an MCP handshake.

Registry name
app.belcome/booking
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
38 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Find salons, barbershops, spas and med spas on Belcome, see services, prices and open times.
Listing
From the official MCP registry (active).
Recent checks of Belcome
CheckedResultHandshake
1 hour agoHandshake completed38 ms
1 day agoHandshake completed40 ms
2 days agoHandshake completed32 ms
3 days agoHandshake completed48 ms
4 days agoHandshake completed41 ms
5 days agoHandshake completed42 ms
7 days agoHandshake completed47 ms
10 days agoHandshake completed32 ms
12 days agoHandshake completed39 ms
14 days agoHandshake completed37 ms
17 days agoHandshake completed44 ms
19 days agoHandshake completed47 ms
21 days agoHandshake completed35 ms
23 days agoHandshake completed40 ms
25 days agoHandshake completed81 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 Belcome and makes no claim about it beyond what these checks measured.