Remote MCP · Endpoint

BestAsiaHotels MCP server

No. BestAsiaHotels answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://mcp.bestasiahotels.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.LightoninT/bestasiahotels
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
580 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read-only Asian hotel search and guides with canonical sources and non-live rates.
Listing
From the official MCP registry (active).
Recent checks of BestAsiaHotels
CheckedResultHandshake
43 minutes agoHandshake completed580 ms
9 days agoHandshake completed822 ms
10 days agoHandshake completed782 ms
11 days agoHandshake completed328 ms
12 days agoHandshake completed465 ms
14 days agoHandshake completed470 ms
14 days agoHandshake completed571 ms
15 days agoHandshake completed530 ms
17 days agoHandshake completed708 ms
19 days agoHandshake completed816 ms
21 days agoHandshake completed484 ms
24 days agoHandshake completed744 ms
26 days agoHandshake completed488 ms
28 days agoHandshake completed417 ms

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

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 BestAsiaHotels and makes no claim about it beyond what these checks measured.