Remote MCP · Endpoint

chucho — Book Direct MCP server

No. chucho — Book Direct answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://chucho.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.chucho/chucho
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
171 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Find vacation rentals worldwide by describing the trip, check host prices and book direct.
Listing
From the official MCP registry (active).
Recent checks of chucho — Book Direct
CheckedResultHandshake
34 minutes agoHandshake completed171 ms
3 days agoHandshake completed214 ms
13 days agoHandshake completed263 ms
13 days agoHandshake completed202 ms
15 days agoHandshake completed183 ms
16 days agoHandshake completed170 ms
17 days agoHandshake completed182 ms
18 days agoHandshake completed187 ms
18 days agoHandshake completed186 ms
20 days agoHandshake completed336 ms
22 days agoHandshake completed344 ms
25 days agoHandshake completed277 ms
27 days agoHandshake completed1.37 s

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