Remote MCP · Endpoint

Best Western Hotels MCP server

No. Best Western Hotels answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp-hotel.bestwestern.fr/mcp

The last check completed an MCP handshake.

Registry name
fr.bestwestern.mcp-hotel/hotels
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
344 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search Best Western hotels worldwide: descriptions, addresses, contacts, amenities and photos.
Listing
From the official MCP registry (active).
Recent checks of Best Western Hotels
CheckedResultHandshake
1 hour agoHandshake completed344 ms
7 hours agoHandshake completed365 ms
2 days agoHandshake completed368 ms
4 days agoHandshake completed319 ms
6 days agoHandshake completed305 ms
9 days agoHandshake completed315 ms
11 days agoHandshake completed340 ms
13 days agoHandshake completed339 ms
15 days agoHandshake completed341 ms
17 days agoHandshake completed363 ms
19 days agoHandshake completed320 ms
21 days agoHandshake completed333 ms
23 days agoHandshake completed416 ms
24 days agoHandshake completed796 ms

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

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