InviteKit Calendar Files
REMOTE · CALENDAR-INVITE.ZOVO.ONE
.ics files & calendar links
Available components
Last scanned (1 day ago)
Scores higher than 64% of remote servers
Reachable. Last reached 22 Oct 2026.
Category Productivity and Notes
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Oct 26 73
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Oct 2026 · Probed https://calendar-invite.zovo.one/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 532f1d6b62c65f8d13c62c00b572a77e |
| SANs: zovo.one, calendar-invite.zovo.one, *.calendar-invite.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of calendar-invite.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://calendar-invite.zovo.one/mcp | Verified | 200 | |
| http (plaintext) | http://calendar-invite.zovo.one/mcp | HTTPS enforced | 301 | https://calendar-invite.zovo.one/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
generate_calendar_event Generate calendar event file and links ~670
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | 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"]. |
| Name | Type | Req | Description |
|---|---|---|---|
| all_day | boolean | yes | – |
| description | string|null | yes | – |
| downloads | object | yes | – |
| duration | string | yes | – |
| end | object | yes | – |
| links | object | yes | – |
| location | string|null | yes | – |
| notes | array | yes | – |
| occurrences | array | yes | – |
| organizer | string|null | yes | – |
| recurrence | – | yes | – |
| reminders | array | yes | – |
| start | object | yes | – |
| time_zone | string|null | yes | – |
| title | string | yes | – |
| url | string|null | yes | – |
| viewer_zones | array | yes | – |
| when | string | yes | – |
| zone_label | string|null | yes | – |
No examples provided.
generate_event_series Generate calendar file for a schedule ~379
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| calendar_name | string|null | yes | – |
| downloads | object | yes | – |
| event_count | number | yes | – |
| events | array | yes | – |
| first_date | string | yes | – |
| last_date | string | yes | – |
| location | string|null | yes | – |
| notes | array | yes | – |
| reminders | array | yes | – |
| time_zone | string|null | yes | – |
| zone_label | string|null | yes | – |
No examples provided.
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.
remote · calendar-invite.zovo.one
claude mcp add --transport http theluckystrike-calendar-invite 'https://calendar-invite.zovo.one/mcp'
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.