# io.github.theluckystrike/appointment (mcpb · calendar.mcpb)

Read your .ics calendar for appointments, free-busy windows and conflicts.

- Trust score: 54/100 (low)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- mcpb · `calendar.mcpb`: 54/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-appointment/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-calendar-m.md), [page](https://verifymcp.io/servers/theluckystrike-appointment/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-calendar-m)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/calendar.mcpb`
- Version: `0.21.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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.

- **Supply Chain Security**: 23/100
  - Malware scan not yet available for this package.
  - Known CVEs were checked across the 96 of 96 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 13 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 88/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 1106 tokens (~85/item across 13 items; 12 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 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

- Download bundle: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/calendar.mcpb`

## 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-19 (score 54, +1)

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

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

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

### 2026-09-15 (score 52, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-07 (score 48)

First indexed and scored.

## MCP tools (12)

### `license_status` (~23 tokens)

License status

Show whether this server runs in free or Pro mode and where to upgrade.

### `license_activate` (~42 tokens)

Activate license

Activate a Pro license key (format MCPL1.xxx.yyy). Verified offline and saved locally.

Input parameters:

- `key` (string, required): License key from the checkout confirmation page

### `ics_import` (~143 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): Path to a .ics file on this machine
- `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` (~35 tokens)

List imported calendars

Every calendar imported into this server: its name, where it came from, how many event definitions it holds and when it was imported.

### `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

Where the time actually went: merged busy blocks from the calendars named, and the gaps in your working hours where nothing is booked. Free/transparent events do not count as busy; whole-day events block the day.

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` (~98 tokens)

Find double bookings

Every pair of events overlapping in time, with minutes they collide. Across all calendars unless one named, so a clashing work/family event is caught. Whole-day events reported separately. Free: 31 days; Pro: any window.

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` (~46 tokens)

Next event

The next event that has not started yet, with how long until it begins. Looks ahead up to a year.

Input parameters:

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

### `event_export` (~136 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): Where to write the .ics file
- `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` (~42 tokens)

Forget a calendar

Remove one imported calendar and the local copy of its .ics file. Nothing else is touched.

Input parameters:

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

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/theluckystrike-appointment/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-calendar-m#diagnostics

## Score history

- 2026-09-20: 54
- 2026-09-19: 54
- 2026-09-18: 53
- 2026-09-17: 53
- 2026-09-16: 52
- 2026-09-15: 52
- 2026-09-14: 48
- 2026-09-13: 48
- 2026-09-12: 48
- 2026-09-11: 48
- 2026-09-10: 48
- 2026-09-09: 48
- 2026-09-08: 48
- 2026-09-07: 48

## Common questions

### What is the io.github.theluckystrike/appointment MCP server?

io.github.theluckystrike/appointment is an MCP server listed in the public MCP registry as io.github.theluckystrike/appointment. Read your .ics calendar for appointments, free-busy windows and conflicts. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/calendar.mcpb).

### Is the io.github.theluckystrike/appointment MCP server safe to use?

io.github.theluckystrike/appointment scores 54 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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/appointment MCP server expose?

io.github.theluckystrike/appointment exposes 12 tools: license_status, license_activate, ics_import, calendars_list, events_list, and 7 more. Their descriptions and schemas cost roughly 1,088 tokens of context every time the server is loaded.

### What licence is the io.github.theluckystrike/appointment MCP server under?

io.github.theluckystrike/appointment declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/calendar
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-appointment/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-calendar-m.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-appointment/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-calendar-m.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-appointment/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-calendar-m