io.github.theluckystrike/calendar-ics-reader-events-freebusy-conflicts
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS · SCANNED SEP 20
Read the .ics your calendar exports: events in a window, free-busy, double bookings, export.
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- 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 Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1297 tokens (~92/item across 14 items; 12 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 13 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
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.
remote · mcp.zovo.one
claude mcp add --transport http theluckystrike-calendar-ics-reader-events-freebu 'https://mcp.zovo.one/mcp/calendar'
{
"mcpServers": {
"theluckystrike-calendar-ics-reader-events-freebu": {
"url": "https://mcp.zovo.one/mcp/calendar"
}
}
} {
"servers": {
"theluckystrike-calendar-ics-reader-events-freebu": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/calendar"
}
}
} [mcp_servers.theluckystrike-calendar-ics-reader-events-freebu] url = "https://mcp.zovo.one/mcp/calendar"
{
"$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 mcp add theluckystrike-calendar-ics-reader-events-freebu --url 'https://mcp.zovo.one/mcp/calendar' --transport streamable-http
mcp_servers:
theluckystrike-calendar-ics-reader-events-freebu:
url: "https://mcp.zovo.one/mcp/calendar" {
"McpServers": {
"theluckystrike-calendar-ics-reader-events-freebu": {
"Transport": "http",
"Url": "https://mcp.zovo.one/mcp/calendar"
}
}
} assistant mcp add theluckystrike-calendar-ics-reader-events-freebu -t streamable-http -u 'https://mcp.zovo.one/mcp/calendar'
{
"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.
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.
- 20 Sept 26 +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.
- 17 Sept 26 +1
- Server version: 0.21.0 → 0.22.0 functional
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +1
- Tool “license_activate” rewrote its description, which is the text the model reads security
- New prompt “upgrade_to_pro” functional
- New resource “pricing” functional
- 10 Sept 26 0
- 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 security
- Schema quality: 86 → 95 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- “license_activate” reworded the description of “key” cosmetic
- 9 Sept 26 +42
- Transport: unverified → pass ▲ security
- 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. security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 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 functional
- 3 Sept 26 36
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 20 Sept 2026 · Probed https://mcp.zovo.one/mcp/calendar
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 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ef74739bd6e575bb13db69661e215324 |
| SANs: zovo.one, mcp.zovo.one, *.mcp.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 mcp.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 Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", error="invalid_token"
Bearer realm="mcp.zovo.one", error="invalid_token"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zovo.one/mcp/calendar | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/calendar | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/calendar |
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 →
calendars_list List imported calendars ~54
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
conflicts Find double bookings ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| calendar | string | – | One calendar name; default every imported calendar |
| from | string | yes | First day, YYYY-MM-DD |
| to | string | yes | Last day, YYYY-MM-DD, included |
No output schema declared.
No examples provided.
event_export Export events to a .ics file ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Name for the downloaded .ics file, e.g. week.ics |
| to | string | – | Last day, YYYY-MM-DD, included |
No output schema declared.
No examples provided.
event_to_time_entry Turn a meeting into a time entry ~155
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Event id from events_list, events_search or next_event |
| project | string | yes | 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') |
No output schema declared.
No examples provided.
events_list List events in a window ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| calendar | string | – | One calendar name; default every imported calendar |
| from | string | yes | First day, YYYY-MM-DD |
| to | string | yes | Last day, YYYY-MM-DD, included |
| zone | string | – | Show local times in this zone or city instead of your own |
No output schema declared.
No examples provided.
events_search Search events ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | First day, YYYY-MM-DD |
| query | string | yes | Words to look for, case-insensitive |
| to | string | – | Last day, YYYY-MM-DD, included |
No output schema declared.
No examples provided.
free_busy Busy blocks and free windows ~159
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.
| Name | Type | Req | Description |
|---|---|---|---|
| calendars | array | – | Calendar names; default all of them |
| from | string | yes | First day, YYYY-MM-DD |
| to | string | yes | 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 |
No output schema declared.
No examples provided.
ics_forget Forget a calendar ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The calendar name from calendars_list |
No output schema declared.
No examples provided.
ics_import Import a calendar (.ics) ~152
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | 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 |
No output schema declared.
No examples provided.
license_activate Activate license ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from checkout, MCPL1.<payload>.<signature> |
No output schema declared.
No examples provided.
license_status License status ~55
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
next_event Next event ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| calendar | string | – | One calendar name; default every imported calendar |
No output schema declared.
No examples provided.
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.