Remote MCP · Endpoint

HolidayFox MCP server

No. HolidayFox answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.holidayfox.com/mcp

The last check completed an MCP handshake.

Registry name
com.holidayfox/booking
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
359 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Search independent UK holiday stays, check live availability and exact prices, then open checkout.
Website
https://www.holidayfox.com/mcp
Listing
From the official MCP registry (active).
Recent checks of HolidayFox
CheckedResultHandshake
1 hour agoHandshake completed359 ms
2 days agoHandshake completed312 ms
5 days agoHandshake completed348 ms
7 days agoHandshake completed368 ms
9 days agoHandshake completed393 ms
11 days agoHandshake completed289 ms
13 days agoHandshake completed349 ms
15 days agoHandshake completed364 ms
17 days agoHandshake completed277 ms
19 days agoHandshake completed366 ms
20 days agoHandshake completed439 ms
21 days agoHandshake completed298 ms
23 days agoHandshake completed376 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with HolidayFox and makes no claim about it beyond what these checks measured.