Remote MCP · Endpoint

MyService Hotels MCP server

No. MyService Hotels answered an MCP handshake 52 minutes ago.

UpLast checked 52 minutes ago

Server URL

https://mcp.myservice.pk/mcp

The last check completed an MCP handshake.

Registry name
pk.myservice/hotels
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
451 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
AI hotel search and booking: millions of properties, 85,000+ cities, live rates.
Listing
From the official MCP registry (active).
Recent checks of MyService Hotels
CheckedResultHandshake
52 minutes agoHandshake completed451 ms
3 days agoHandshake completed319 ms
12 days agoHandshake completed350 ms
13 days agoHandshake completed614 ms
14 days agoHandshake completed440 ms
15 days agoHandshake completed706 ms
17 days agoHandshake completed340 ms
18 days agoHandshake completed347 ms
18 days agoHandshake completed378 ms
20 days agoHandshake completed439 ms
22 days agoHandshake completed232 ms
25 days agoHandshake completed578 ms
27 days agoHandshake completed1.10 s
29 days agoHandshake completed483 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 MyService Hotels and makes no claim about it beyond what these checks measured.