Remote MCP · Endpoint

chucho — Book Direct MCP server

No. chucho — Book Direct answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://chucho.ai/chatgpt/mcp

The last check completed an MCP handshake.

Registry name
io.github.chucho-ai/chucho
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
468 ms
Tools exposed
18 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find vacation rentals, explore photos and property details, and open direct host booking links.
Listing
From the official MCP registry (active).
Recent checks of chucho — Book Direct
CheckedResultHandshake
1 hour agoHandshake completed468 ms
2 days agoHandshake completed281 ms
5 days agoHandshake completed302 ms
7 days agoHandshake completed296 ms
9 days agoHandshake completed1.72 s
11 days agoHandshake completed291 ms
13 days agoHandshake completed344 ms
15 days agoHandshake completed128 ms
17 days agoHandshake completed382 ms
19 days agoHandshake completed261 ms
20 days agoHandshake completed335 ms
21 days agoHandshake completed279 ms
23 days agoHandshake completed166 ms
25 days agoHandshake completed320 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 chucho — Book Direct and makes no claim about it beyond what these checks measured.