Remote MCP · Endpoint

Pickrate direct-booking hotels MCP server

No. Pickrate direct-booking hotels answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://pick-rate.com/mcp

The last check completed an MCP handshake.

Registry name
com.pick-rate/hotels
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
502 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Hotels that book direct: search, live-availability links, and AI-agent readiness checks.
Listing
From the official MCP registry (active).
Recent checks of Pickrate direct-booking hotels
CheckedResultHandshake
1 hour agoHandshake completed502 ms
3 days agoHandshake completed783 ms
12 days agoHandshake completed743 ms
12 days agoHandshake completed708 ms
14 days agoHandshake completed794 ms
15 days agoHandshake completed829 ms
16 days agoHandshake completed754 ms
17 days agoHandshake completed683 ms
18 days agoHandshake completed833 ms
19 days agoHandshake completed842 ms
22 days agoHandshake completed835 ms
25 days agoHandshake completed685 ms
27 days agoHandshake completed838 ms

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

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