Remote MCP · Endpoint

Veabird: ski & beach trip planner MCP server

No. Veabird: ski & beach trip planner answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://veabird.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.alexchouck-hash/veabird
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
144 ms
Tools exposed
19 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Ski & beach trip planning: resort matching, snow and sargassum forecasts, lodging and flights.
Listing
From the official MCP registry (active).
Recent checks of Veabird: ski & beach trip planner
CheckedResultHandshake
1 hour agoHandshake completed144 ms
2 days agoHandshake completed333 ms
5 days agoHandshake completed482 ms
7 days agoHandshake completed148 ms
9 days agoHandshake completed55 ms
11 days agoHandshake completed46 ms
13 days agoHandshake completed143 ms
15 days agoHandshake completed116 ms
16 days agoHandshake completed60 ms
18 days agoHandshake completed171 ms
19 days agoHandshake completed389 ms
20 days agoHandshake completed231 ms
23 days agoHandshake completed86 ms
24 days agoHandshake completed168 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 Veabird: ski & beach trip planner and makes no claim about it beyond what these checks measured.