# InviteKit Calendar Files (remote · calendar-invite.zovo.one)

.ics files & calendar links

- Trust score: 73/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

## Components

- remote · `calendar-invite.zovo.one`: 73/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-calendar-invite/calendar-invite.md), [page](https://verifymcp.io/servers/theluckystrike-calendar-invite/calendar-invite)

## Channel facts

- Endpoint: `https://calendar-invite.zovo.one/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-10-22.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 70/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1136 tokens (~378/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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.
  - Supports UI / widget rendering.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the InviteKit Calendar Files MCP server?

InviteKit Calendar Files is a hosted endpoint at https://calendar-invite.zovo.one/mcp, 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-invite 'https://calendar-invite.zovo.one/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-calendar-invite": {
      "url": "https://calendar-invite.zovo.one/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.theluckystrike-calendar-invite]
url = "https://calendar-invite.zovo.one/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add theluckystrike-calendar-invite --url 'https://calendar-invite.zovo.one/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-calendar-invite:
    url: "https://calendar-invite.zovo.one/mcp"
```

### Netclaw

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

### Vellum

```bash
assistant mcp add theluckystrike-calendar-invite -t streamable-http -u 'https://calendar-invite.zovo.one/mcp'
```

### Other

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

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-10-22 (score 73)

First indexed and scored.

## MCP tools (2)

### `generate_calendar_event` (~670 tokens)

Generate calendar event file and links

Use this when the user wants a calendar invite, an .ics file, or an add-to-calendar link (Google Calendar, Outlook, Office 365, Yahoo) for one event or one repeating event: a webinar, class, meeting, party, deadline, or launch. Takes the title, local start/end and the event's time zone (city or IANA zone), or dates only for all-day events, plus optional location, description, link, organizer name, reminders, and a repeat rule (daily, weekly on chosen weekdays, monthly by date, nth weekday such as the last Friday, or the first/last weekday of the month, yearly; with count, until date, and skipped dates). Returns a downloadable RFC 5545 .ics file with time zone data, four add-to-calendar links, and the first 5 dates in the event's zone and optional attendee zones, with daylight saving changes flagged. Does not send invitations, read or change anyone's calendar, or track RSVPs. Do not use for a list of different sessions (use generate_event_series) or for finding a meeting time across zones.

Input parameters:

- `all_day` (boolean): true for an all-day event (dates only), e.g. a conference day or a deadline. Automatic when start has no time.
- `description` (string): Event details or agenda (plain text; line breaks allowed), e.g. Bring a laptop.
- `duration_minutes` (integer): Length in minutes instead of end, e.g. 90.
- `end` (string): Local end YYYY-MM-DDTHH:MM, or just a time HH:MM on the start day, e.g. 21:00. For all-day events, the last day YYYY-MM-DD (inclusive). Default: 1 hour, or 1 day for all-day.
- `location` (string): Venue, address, or meeting room shown in the calendar, e.g. Pier 39, San Francisco.
- `organizer_name` (string): Optional organizer name shown in the details, e.g. Acme Events. No email needed.
- `recurrence` (object): Optional repeat rule, e.g. {"frequency":"weekly","weekdays":["TU","TH"],"count":10}.
- `reminders_minutes_before` (array): Up to 3 reminders in minutes before the start, e.g. [15, 1440] for 15 minutes and 1 day before.
- `start` (string, required): Local start YYYY-MM-DDTHH:MM in the event's time zone, e.g. 2026-11-05T18:30, or a date YYYY-MM-DD for an all-day event. No UTC offset.
- `time_zone` (string): Time zone of the start/end: IANA zone (Europe/Warsaw), city (Chicago, Sydney), or UTC. Required for timed events; not used for all-day events.
- `title` (string, required): Event title, e.g. Product launch webinar.
- `url` (string): Optional event page or video-call link, e.g. https://example.com/webinar.
- `viewer_time_zones` (array): Optional places or zones of attendees to show local times for, e.g. ["New York", "Tokyo"].

Output parameters:

- `all_day` (boolean)
- `description` (string|null)
- `downloads` (object)
- `duration` (string)
- `end` (object)
- `links` (object)
- `location` (string|null)
- `notes` (array)
- `occurrences` (array)
- `organizer` (string|null)
- `recurrence`
- `reminders` (array)
- `start` (object)
- `time_zone` (string|null)
- `title` (string)
- `url` (string|null)
- `viewer_zones` (array)
- `when` (string)
- `zone_label` (string|null)

### `generate_event_series` (~379 tokens)

Generate calendar file for a schedule

Use this when the user wants one calendar file (.ics) that adds several different events at once: a course or class schedule, a training program, a conference agenda, match fixtures, or a list of webinars on irregular dates. Takes 1-40 sessions (each with its own start, end or duration, optional title, location and note) plus a shared time zone, location, details, link, organizer name and reminders. Returns one .ics file with one event per session and a dated list of the sessions. Does not make add-to-calendar web links per session, send invitations, or change anyone's calendar. Do not use for an event that repeats on a regular pattern (use generate_calendar_event with recurrence).

Input parameters:

- `calendar_name` (string): Name for the schedule, e.g. Spanish A1 evening course. Shown as the calendar name and default title.
- `description` (string): Shared details added to every session, e.g. Bring your workbook.
- `events` (array, required): 1-40 distinct sessions with their own dates, e.g. [{"title":"Week 1","start":"2027-01-12T18:00","end":"19:30"}].
- `location` (string): Default location for every session, e.g. Community Center, Room 2.
- `organizer_name` (string): Optional organizer or teacher name, e.g. Ms. Rivera.
- `reminders_minutes_before` (array): Up to 3 reminders for every session, minutes before, e.g. [60].
- `time_zone` (string): Time zone for all sessions: IANA zone or city, e.g. America/Chicago. Required when sessions have times.
- `url` (string): Optional shared link, e.g. a course page or video-call link: https://example.com/course.

Output parameters:

- `calendar_name` (string|null)
- `downloads` (object)
- `event_count` (number)
- `events` (array)
- `first_date` (string)
- `last_date` (string)
- `location` (string|null)
- `notes` (array)
- `reminders` (array)
- `time_zone` (string|null)
- `zone_label` (string|null)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-calendar-invite/calendar-invite#diagnostics

## Score history

- 2026-10-22: 73

## Common questions

### What is the InviteKit Calendar Files MCP server?

InviteKit Calendar Files is an MCP server listed in the public MCP registry as io.github.theluckystrike/calendar-invite. .ics files & calendar links. This page covers its hosted endpoint (https://calendar-invite.zovo.one/mcp).

### Is the InviteKit Calendar Files MCP server safe to use?

InviteKit Calendar Files scores 73 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 InviteKit Calendar Files MCP server expose?

InviteKit Calendar Files exposes 2 tools: generate_calendar_event, generate_event_series. Their descriptions and schemas cost roughly 1,049 tokens of context every time the server is loaded.

### Does the InviteKit Calendar Files MCP server require authentication?

No. We connected to InviteKit Calendar Files without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the InviteKit Calendar Files MCP server still maintained?

InviteKit Calendar Files is still listed as active in the MCP registry. We last reached this channel on 22 October 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://calendar-invite.zovo.one/mcp
- Website: https://calendar-invite.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-calendar-invite/calendar-invite.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-calendar-invite/calendar-invite.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-calendar-invite/calendar-invite