Remote MCP · Endpoint

io.github.theluckystrike/itinerary-travel-plan-schedule-events MCP server

No. io.github.theluckystrike/itinerary-travel-plan-schedule-events answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.zovo.one/mcp/itinerary-travel-plan-schedule-events

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/itinerary-travel-plan-schedule-events
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
51 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Trip itinerary planner: events, free-busy, double bookings, schedule export.
Website
https://mcp.zovo.one/s/calendar
Repository
https://github.com/theluckystrike/mcp-servers
Listing
From the official MCP registry (active).
Recent checks of io.github.theluckystrike/itinerary-travel-plan-schedule-events
CheckedResultHandshake
1 hour agoHandshake completed51 ms
2 days agoHandshake completed52 ms
4 days agoHandshake completed97 ms
6 days agoHandshake completed44 ms
7 days agoHandshake completed35 ms
9 days agoHandshake completed32 ms
10 days agoHandshake completed119 ms
11 days agoHandshake completed33 ms
14 days agoHandshake completed33 ms
16 days agoHandshake completed27 ms
17 days agoHandshake completed29 ms
19 days agoHandshake completed24 ms
20 days agoHandshake completed33 ms
21 days agoHandshake completed28 ms
22 days agoHandshake completed26 ms
22 days agoHandshake completed25 ms
24 days agoHandshake completed26 ms

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

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 io.github.theluckystrike/itinerary-travel-plan-schedule-events and makes no claim about it beyond what these checks measured.