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 12 minutes ago.

UpLast checked 12 minutes 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
25 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 14 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
12 minutes agoHandshake completed25 ms
9 days agoHandshake completed218 ms
9 days agoHandshake completed19 ms
11 days agoHandshake completed95 ms
12 days agoHandshake completed75 ms
13 days agoHandshake completed48 ms
14 days agoHandshake completed81 ms
15 days agoHandshake completed112 ms
16 days agoHandshake completed1.05 s
19 days agoHandshake completed813 ms
21 days agoHandshake completed138 ms
24 days agoHandshake completed955 ms
26 days agoHandshake completed663 ms
28 days agoHandshake completed51 ms

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

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.