io.github.theluckystrike/scheduling
MCPB · TIMEZONE.MCPB · 2 COMPONENTS · SCANNED SEP 30
Meeting scheduling across time zones: slot finding, DST checks, .ics invites.
Available components
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. How we score → Why this is hard to score →
Supply Chain Security23
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs were checked across the 92 of 92 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency39
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Maintenance history not yet determined.Unverified
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- 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
- Context-footprint check failed: tool/resource definitions use about 1613 tokens (~134/item across 12 items; 11 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the io.github.theluckystrike/scheduling MCP server?
io.github.theluckystrike/scheduling ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check the download against.
mcpb · timezone.mcpb
Download bundleThe MCP registry declares no SHA-256 for this bundle, so there is no published digest to check it against. Open it with an MCPB-capable host such as Claude Desktop.
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.
- 30 Sept 26 −1
- Maintenance: pass → unverified ▼ functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 49
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 30 Sept 2026 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/timezone.mcpb@0.22.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
business_days Count business days ~159
Count business days between two dates in a place, inclusive, with the calendar total and the weekend and holiday counts. It has NO holiday calendar: without holidays, only weekends are excluded.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | 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 | yes | End date, YYYY-MM-DD (inclusive) |
| zone | string | yes | Place whose calendar to use |
No output schema declared.
No examples provided.
contacts_list List saved contacts ~44
List saved contacts with their zone, local time now, working hours and whether they are inside them; weekends count as outside. It also prints YOUR zone from the shared business profile.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
contacts_set Save a contact's zone ~107
Save one person's zone and working hours so later calls can name them. Returns the resolved zone and their local time now. Saving the same name REPLACES that contact and says so. Free: 5 contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Their name |
| work_end | string | – | Local day end, default 17:00 |
| work_start | string | – | Local day start, default 09:00 |
| zone | string | yes | Their place or IANA zone |
No output schema declared.
No examples provided.
convert_time Convert a time between zones ~213
Convert one time from from_zone into every zone in to_zones, marking any day change, plus the UTC instant. The time is wall-clock in from_zone unless it carries an offset or a trailing Z. '3pm tomorrow' works.
| Name | Type | Req | Description |
|---|---|---|---|
| fold | string | – | Which occurrence of a time that happens twice because the clocks went back. Default 'first'. |
| from_zone | string | yes | 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 | yes | '2026-09-10 15:00', '2026-09-10T15:00:00Z', '3pm tomorrow', 'now' |
| to_zones | array | yes | Places to convert into |
No output schema declared.
No examples provided.
dst_changes Daylight-saving changes ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| year | integer | – | Calendar year, default this year |
| zone | string | yes | Place or IANA zone |
No output schema declared.
No examples provided.
find_meeting_slots Find meeting slots ~303
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 |
No output schema declared.
No examples provided.
ics_create Write a calendar invite ~380
Call this tool to write a .ics for one meeting and return the path plus the start in UTC and in your zone. Times are stored in UTC so it lands correctly in any client. Free: 3 files a month.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | Start time, read in `zone` unless it carries an offset |
| title | string | yes | Event title |
| zone | string | yes | Place the start time is given in |
No output schema declared.
No examples provided.
license_activate Activate license ~71
Activate a Pro key (MCPL1.xxx.yyy) from checkout: verified offline against a built-in public key, saved to your config file. A wrong, malformed or expired key is refused, unsaved. license_status reads it back.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from the checkout confirmation page |
No output schema declared.
No examples provided.
license_status License status ~54
Report this server's licence state: product, tier free or pro, licence id, expiry, the key source and the upgrade URL. No arguments, no network. Explains a free-tier refusal; license_activate installs a key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
now Current time in zones ~74
The current time in one or more places, each with the zone it resolved to and the local date, time and offset, under one UTC instant. Accepts IANA zones, cities, countries and abbreviations.
| Name | Type | Req | Description |
|---|---|---|---|
| zones | array | – | Places or IANA zones, e.g. ['Warsaw','New York','India'] |
No output schema declared.
No examples provided.
overlap Daily working-hours overlap ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Places, e.g. ['Warsaw','New York','Bangalore'] |
No output schema declared.
No examples provided.
What is the io.github.theluckystrike/scheduling MCP server?
io.github.theluckystrike/scheduling is an MCP server listed in the public MCP registry as io.github.theluckystrike/scheduling. Meeting scheduling across time zones: slot finding, DST checks, .ics invites. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/timezone.mcpb).
Is the io.github.theluckystrike/scheduling MCP server safe to use?
io.github.theluckystrike/scheduling scores 48 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/scheduling MCP server expose?
io.github.theluckystrike/scheduling exposes 11 tools: license_status, license_activate, now, convert_time, overlap, and 6 more. Their descriptions and schemas cost roughly 1,595 tokens of context every time the server is loaded.
What licence is the io.github.theluckystrike/scheduling MCP server under?
io.github.theluckystrike/scheduling declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.