Remote MCP · Endpoint

io.github.theluckystrike/calendar-ics-reader-events-freebusy-conflicts MCP server

No. io.github.theluckystrike/calendar-ics-reader-events-freebusy-conflicts answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.zovo.one/mcp/calendar

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/calendar-ics-reader-events-freebusy-conflicts
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
163 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Read the .ics your calendar exports: events in a window, free-busy, double bookings, export.
Listing
From the official MCP registry (active).
Recent checks of io.github.theluckystrike/calendar-ics-reader-events-freebusy-conflicts
CheckedResultHandshake
1 hour agoHandshake completed163 ms
2 days agoHandshake completed968 ms
4 days agoHandshake completed886 ms
6 days agoHandshake completed820 ms
7 days agoHandshake completed521 ms
9 days agoHandshake completed188 ms
10 days agoHandshake completed691 ms
11 days agoHandshake completed524 ms
14 days agoHandshake completed203 ms
15 days agoHandshake completed826 ms
17 days agoHandshake completed587 ms
18 days agoHandshake completed37 ms
19 days agoHandshake completed27 ms
20 days agoHandshake completed28 ms
21 days agoHandshake completed32 ms
22 days agoHandshake completed47 ms
23 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.

Listing data comes from the official MCP registry. Glide is not affiliated with io.github.theluckystrike/calendar-ics-reader-events-freebusy-conflicts and makes no claim about it beyond what these checks measured.