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

Time zone and calendar helper: meeting slots across countries, DST checks, .ics invites.

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

## Components

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

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/timezone.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**: 85/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).
  - Context-footprint check failed: tool/resource definitions use about 1531 tokens (~127/item across 12 items; 11 tools + 1 resources), over budget; trim descriptions and params.
  - 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**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 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/timezone.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 55, +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 54, +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 53, +1)

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

### 2026-09-14 (score 52, +3)

- [functional improvement] Stability: unverified → 0.23

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

First indexed and scored.

## MCP tools (11)

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

### `now` (~85 tokens)

Current time in zones

The current time in one or more places. Accepts IANA zones (Europe/Warsaw), city names (Warsaw), country names (Poland) or abbreviations (PST, IST). With no zones it reports this machine's local zone and UTC.

Input parameters:

- `zones` (array): Places or IANA zones, e.g. ['Warsaw','New York','India']

### `convert_time` (~222 tokens)

Convert a time between zones

Convert a time from one place to others. The input time is read as wall-clock time in from_zone unless it carries an offset or a trailing Z. Accepts '2026-09-10 15:00', an ISO timestamp, or a phrase like '3pm tomorrow'.

Input parameters:

- `fold` (string): Which occurrence of a time that happens twice because the clocks went back. Default 'first'.
- `from_zone` (string, required): Place the time is given in, e.g. 'Warsaw' or 'Europe/Warsaw'
- `gap` (string): What to do with a time that does not exist because the clocks jumped forward: 'forward' takes the time after the jump, 'backward' the time before it. Without this, such a time is refused.
- `time` (string, required): '2026-09-10 15:00', '2026-09-10T15:00:00Z', '3pm tomorrow', 'now'
- `to_zones` (array, required): Places to convert into

### `overlap` (~117 tokens)

Daily working-hours overlap

The window each day when every listed place is inside working hours. Computed on a real date, so a DST week that widens or narrows the overlap is reflected.

Input parameters:

- `date` (string): Date to compute on, YYYY-MM-DD, default today
- `work_end` (string): Local working day end, default 17:00
- `work_start` (string): Local working day start, default 09:00
- `zones` (array, required): Places, e.g. ['Warsaw','New York','Bangalore']

### `find_meeting_slots` (~303 tokens)

Find meeting slots

Rank the times when every participant is inside their own working hours. Returns each slot as a UTC instant with the local time for every participant and a fairness score, best first.

Input parameters:

- `days` (integer): How many days ahead to search, default 5, at most 366. Free tier: a search longer than 5 days is shortened to 5, not refused
- `duration_minutes` (integer): Meeting length in minutes, default 60, at most 1440
- `earliest_date` (string): First date to consider, YYYY-MM-DD, default today
- `limit` (integer): How many slots to return, default 8. Slots are ranked by fairness: the score is the WORST participant's distance in hours from 13:00 local, so a slot that is 07:00 for one person never outranks one t…
- `participants` (array, required): Who has to attend. A zone is OPTIONAL per person: a saved contact supplies their own, and anyone left without one (you, typically) takes the timezone on your shared business profile, so never ask the…
- `recurring` (boolean): Pro: also report the weekly recurring times that work on every searched weekday

### `dst_changes` (~73 tokens)

Daylight-saving changes

The clock changes in a place for a year, with the exact UTC instant and the offset before and after. Use it to check whether a recurring call moves for one of you in March or October.

Input parameters:

- `year` (integer): Calendar year, default this year
- `zone` (string, required): Place or IANA zone

### `business_days` (~165 tokens)

Count business days

Count the business days between two dates in a place, for delivery dates and payment terms. Returns the business-day count, the calendar total, and how many days fell on a weekend or on a holiday you passed.

Input parameters:

- `from` (string, required): Start date, YYYY-MM-DD (inclusive). A date that does not exist, such as 2026-02-30, is refused, never rolled forward
- `holidays` (array): Dates to exclude, strict YYYY-MM-DD. This tool has no national holiday calendar: unless you pass holidays here only weekends are excluded, so do not report the answer as a public-holiday-adjusted cou…
- `to` (string, required): End date, YYYY-MM-DD (inclusive)
- `zone` (string, required): Place whose calendar to use

### `contacts_set` (~90 tokens)

Save a contact's zone

Remember a client or teammate's time zone and working hours so you can say 'find a slot with Maria and Raj' later.

Input parameters:

- `name` (string, required): Their name
- `work_end` (string): Local day end, default 17:00
- `work_start` (string): Local day start, default 09:00
- `zone` (string, required): Their place or IANA zone

### `contacts_list` (~28 tokens)

List saved contacts

Everyone you have saved, with their current local time and whether they are inside working hours right now.

### `ics_create` (~365 tokens)

Write a calendar invite

Call this tool to write a .ics calendar file for one meeting. Returns the path written and the meeting time in UTC and in the zone you gave.

Input parameters:

- `attendees` (array): Attendees. An entry with an email is invited (ATTENDEE:mailto:...); a name with no email is listed in the description instead, because a calendar cannot invite a name.
- `description` (string): Body text
- `duration_minutes` (integer, required): Length in minutes, at most 1440
- `fold` (string): Which occurrence of a time that happens twice because the clocks went back. Default 'first'.
- `gap` (string): What to do with a time that does not exist because the clocks jumped forward: 'forward' takes the time after the jump, 'backward' the time before it. Without this, such a time is refused.
- `location` (string): Where, or a meeting link
- `organizer_email` (string): Your email address, written as the ORGANIZER so replies have somewhere to go. Leave it out and your shared business profile's email is used; with neither, the ORGANIZER line is omitted rather than fi…
- `organizer_name` (string): Your display name for the ORGANIZER line
- `out_path` (string): Where to write the .ics file; default meeting.ics in the data dir. Times are stored in UTC, so the invite lands at the right local time in every attendee's calendar with no time zone block to go stale
- `start` (string, required): Start time, read in `zone` unless it carries an offset
- `title` (string, required): Event title
- `zone` (string, required): Place the start time is given in

## Diagnostics

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

## Score history

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

## Common questions

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

io.github.theluckystrike/calendar is an MCP server listed in the public MCP registry as io.github.theluckystrike/calendar. Time zone and calendar helper: meeting slots across countries, DST checks, .ics invites. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/timezone.mcpb).

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

io.github.theluckystrike/calendar scores 55 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/calendar MCP server expose?

io.github.theluckystrike/calendar exposes 11 tools: license_status, license_activate, now, convert_time, overlap, and 6 more. Their descriptions and schemas cost roughly 1,513 tokens of context every time the server is loaded.

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

io.github.theluckystrike/calendar 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/timezone
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-calendar/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-timezone-m.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-calendar/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-timezone-m.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-calendar/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-timezone-m