# io.github.theluckystrike/calendar-ics-reader-events-freebusy-conflicts (remote · mcp.zovo.one)

Read the .ics your calendar exports: events in a window, free-busy, double bookings, export.

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.zovo.one`: 83/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-calendar-ics-reader-events-freebusy-conflicts/mcp-calendar.md), [page](https://verifymcp.io/servers/theluckystrike-calendar-ics-reader-events-freebusy-conflicts/mcp-calendar)
- mcpb · `calendar.mcpb`: 48/100, [markdown](https://verifymcp.io/servers/theluckystrike-calendar-ics-reader-events-freebusy-conflicts/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-calendar-m.md), [page](https://verifymcp.io/servers/theluckystrike-calendar-ics-reader-events-freebusy-conflicts/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-calendar-m)

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/calendar`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.22.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 87/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1297 tokens (~92/item across 14 items; 12 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "ics_forget" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.theluckystrike/calendar-ics-reader-events-freebus… MCP server?

io.github.theluckystrike/calendar-ics-reader-events-freebus… is a hosted endpoint at https://mcp.zovo.one/mcp/calendar, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http theluckystrike-calendar-ics-reader-events-freebu 'https://mcp.zovo.one/mcp/calendar'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-calendar-ics-reader-events-freebu": {
      "url": "https://mcp.zovo.one/mcp/calendar"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-calendar-ics-reader-events-freebu": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/calendar"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-calendar-ics-reader-events-freebu]
url = "https://mcp.zovo.one/mcp/calendar"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-calendar-ics-reader-events-freebu": {
      "type": "remote",
      "url": "https://mcp.zovo.one/mcp/calendar",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-calendar-ics-reader-events-freebu --url 'https://mcp.zovo.one/mcp/calendar' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-calendar-ics-reader-events-freebu:
    url: "https://mcp.zovo.one/mcp/calendar"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-calendar-ics-reader-events-freebu": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/calendar"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-calendar-ics-reader-events-freebu -t streamable-http -u 'https://mcp.zovo.one/mcp/calendar'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-calendar-ics-reader-events-freebu": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/calendar"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 82, +1)

- [functional] Server version: 0.21.0 → 0.22.0

### 2026-09-15 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 79, +1)

- [security] Tool “license_activate” rewrote its description, which is the text the model reads
- [functional] New prompt “upgrade_to_pro”
- [functional] New resource “pricing”

### 2026-09-10 (score 78, 0)

- [security] Tool “license_activate” rewrote its description, which is the text the model reads
- [security] Tool “ics_forget” rewrote its description, which is the text the model reads
- [security] Tool “free_busy” rewrote its description, which is the text the model reads
- [security] Tool “conflicts” rewrote its description, which is the text the model reads
- [security] Tool “calendars_list” rewrote its description, which is the text the model reads
- [security] Tool “license_status” rewrote its description, which is the text the model reads
- [security] Tool “next_event” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 86 → 95
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “license_activate” reworded the description of “key”

### 2026-09-09 (score 78, +42)

- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Schema quality: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: 0
- [functional] First check of Schema quality: pass
- [functional] First check of Tool coverage: 100

### 2026-09-03 (score 36)

First indexed and scored.

## MCP tools (12)

### `license_status` (~55 tokens)

License status

Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.

### `license_activate` (~76 tokens)

Activate license

Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.

Input parameters:

- `key` (string, required): License key from checkout, MCPL1.<payload>.<signature>

### `ics_import` (~152 tokens)

Import a calendar (.ics)

Call this tool to read a calendar export and keep it under a name. Give path (.ics file), text (contents), or url (public .ics/webcal feed; Pro). Google, Apple, Outlook exports read. Re-importing a name replaces it.

Input parameters:

- `name` (string, required): What to call this calendar, e.g. "work" or "family"
- `path` (string): Not available on this hosted endpoint, which has no filesystem: paste the file as text instead
- `text` (string): The .ics file contents, pasted
- `url` (string): Public https:// or webcal:// .ics feed. Fetched once, only because you asked; Pro feature

### `calendars_list` (~54 tokens)

List imported calendars

List imported calendars: name, event-definition count, size, source, import time and free-tier use of the 2 slots. It also names stored .ics files with no calendar row. With none it prints the export steps.

### `events_list` (~115 tokens)

List events in a window

Every event between two dates, recurring expanded to occurrences, sorted by start. Times shown in your zone (profile's, else this machine's) unless zone passed. Each id works for event_export or event_to_time_entry.

Input parameters:

- `calendar` (string): One calendar name; default every imported calendar
- `from` (string, required): First day, YYYY-MM-DD
- `to` (string, required): Last day, YYYY-MM-DD, included
- `zone` (string): Show local times in this zone or city instead of your own

### `events_search` (~94 tokens)

Search events

Find events whose title, description, location or attendees contain a phrase. Searches every imported calendar. Without from/to it looks a year back and a year forward on Pro, and the free window either side of today.

Input parameters:

- `from` (string): First day, YYYY-MM-DD
- `query` (string, required): Words to look for, case-insensitive
- `to` (string): Last day, YYYY-MM-DD, included

### `free_busy` (~159 tokens)

Busy blocks and free windows

Merged busy blocks and the free gaps inside your working hours over a day range. Events marked free do not count; whole-day events block the day. Free: 31 days. Use conflicts for overlapping pairs.

Input parameters:

- `calendars` (array): Calendar names; default all of them
- `from` (string, required): First day, YYYY-MM-DD
- `to` (string, required): Last day, YYYY-MM-DD, included
- `work_end` (string): End of your working day, HH:MM, default 17:00
- `work_start` (string): Start of your working day, HH:MM, default 09:00
- `zone` (string): Zone the working hours and the output are in; default your own

### `conflicts` (~95 tokens)

Find double bookings

Find double bookings: every PAIR of timed events that overlap, with the minutes they collide, across all calendars unless you name one. Whole-day events are reported apart. Free: 31 days. free_busy shows gaps.

Input parameters:

- `calendar` (string): One calendar name; default every imported calendar
- `from` (string, required): First day, YYYY-MM-DD
- `to` (string, required): Last day, YYYY-MM-DD, included

### `next_event` (~67 tokens)

Next event

The first event not yet started, within the next 366 days, across every imported calendar or one you name. Returns title, times in your zone, how long until it starts, location, attendees and its id.

Input parameters:

- `calendar` (string): One calendar name; default every imported calendar

### `event_export` (~143 tokens)

Export events to a .ics file

Call this tool to write chosen events to a new .ics file you can send or import elsewhere. Pass either ids (from events_list) or a from/to window. Times are written in UTC so the file lands correctly in any client.

Input parameters:

- `calendar` (string): With from/to: limit to one calendar
- `from` (string): First day, YYYY-MM-DD (alternative to ids)
- `ids` (array): Event ids from events_list, events_search or next_event
- `out_path` (string, required): Name for the downloaded .ics file, e.g. week.ics
- `to` (string): Last day, YYYY-MM-DD, included

### `event_to_time_entry` (~155 tokens)

Turn a meeting into a time entry

Take one event and return the exact arguments for the time-tracker's entry_add, so a meeting that already happened becomes billable time without retyping it. Writes nothing: pass the JSON straight to entry_add.

Input parameters:

- `currency` (string): Currency of the rate: EUR, USD, GBP, PLN, or the word the user said ('euros'). Without it the time-tracker falls back to USD.
- `event_id` (string, required): Event id from events_list, events_search or next_event
- `project` (string, required): Project or client the meeting is billed to
- `rate`: Hourly rate for this entry; a number (120) or the words the user said ('120 euros an hour')

### `ics_forget` (~64 tokens)

Forget a calendar

Remove one imported calendar by name and delete this server's local copy of its .ics, freeing a slot. Your own calendar and the source file are untouched. ics_import replaces a name in place.

Input parameters:

- `name` (string, required): The calendar name from calendars_list

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-calendar-ics-reader-events-freebusy-conflicts/mcp-calendar#diagnostics

## Score history

- 2026-09-20: 83
- 2026-09-19: 82
- 2026-09-18: 82
- 2026-09-17: 82
- 2026-09-16: 81
- 2026-09-15: 81
- 2026-09-14: 80
- 2026-09-13: 80
- 2026-09-12: 79
- 2026-09-11: 79
- 2026-09-10: 78
- 2026-09-09: 78
- 2026-09-08: 36
- 2026-09-07: 36
- 2026-09-06: 36
- 2026-09-05: 36
- 2026-09-04: 36
- 2026-09-03: 36

## Common questions

### What is the io.github.theluckystrike/calendar-ics-reader-events-freebus… MCP server?

io.github.theluckystrike/calendar-ics-reader-events-freebus… is an MCP server listed in the public MCP registry as io.github.theluckystrike/calendar-ics-reader-events-freebus…. Read the .ics your calendar exports: events in a window, free-busy, double bookings, export. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/calendar).

### Is the io.github.theluckystrike/calendar-ics-reader-events-freebus… MCP server safe to use?

io.github.theluckystrike/calendar-ics-reader-events-freebus… scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.theluckystrike/calendar-ics-reader-events-freebus… MCP server expose?

io.github.theluckystrike/calendar-ics-reader-events-freebus… exposes 12 tools: license_status, license_activate, ics_import, calendars_list, events_list, and 7 more. Their descriptions and schemas cost roughly 1,229 tokens of context every time the server is loaded.

### Does the io.github.theluckystrike/calendar-ics-reader-events-freebus… MCP server require authentication?

Yes. io.github.theluckystrike/calendar-ics-reader-events-freebus… asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the io.github.theluckystrike/calendar-ics-reader-events-freebus… MCP server still maintained?

io.github.theluckystrike/calendar-ics-reader-events-freebus… is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.zovo.one/mcp/calendar
- Authorisation metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/calendar
- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/calendar
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-calendar-ics-reader-events-freebusy-conflicts/mcp-calendar.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-calendar-ics-reader-events-freebusy-conflicts/mcp-calendar.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-calendar-ics-reader-events-freebusy-conflicts/mcp-calendar