# io.github.theluckystrike/timezone-world-clock-meeting-slots-overlap-ics (remote · mcp.zovo.one)

Time zone conversion, meeting-slot finding across countries, DST checks and .ics invites. All.

- Trust score: 85/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.zovo.one`: 85/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-timezone-world-clock-meeting-slots-overlap-ics/mcp-timezone.md), [page](https://verifymcp.io/servers/theluckystrike-timezone-world-clock-meeting-slots-overlap-ics/mcp-timezone)
- mcpb · `timezone.mcpb`: 49/100, [markdown](https://verifymcp.io/servers/theluckystrike-timezone-world-clock-meeting-slots-overlap-ics/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-timezone-m.md), [page](https://verifymcp.io/servers/theluckystrike-timezone-world-clock-meeting-slots-overlap-ics/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-timezone-m)

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/timezone`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.22.0`

## Trust breakdown

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. 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.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **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 1634 tokens (~125/item across 13 items; 11 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 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

### How do I install the io.github.theluckystrike/timezone-world-clock-meeting-slots… MCP server?

io.github.theluckystrike/timezone-world-clock-meeting-slots… is a hosted endpoint at https://mcp.zovo.one/mcp/timezone, 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.

### Claude

```bash
claude mcp add --transport http theluckystrike-timezone-world-clock-meeting-slot 'https://mcp.zovo.one/mcp/timezone'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-timezone-world-clock-meeting-slot": {
      "url": "https://mcp.zovo.one/mcp/timezone"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-timezone-world-clock-meeting-slot": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/timezone"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-timezone-world-clock-meeting-slot]
url = "https://mcp.zovo.one/mcp/timezone"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-timezone-world-clock-meeting-slot": {
      "type": "remote",
      "url": "https://mcp.zovo.one/mcp/timezone",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-timezone-world-clock-meeting-slot --url 'https://mcp.zovo.one/mcp/timezone' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-timezone-world-clock-meeting-slot:
    url: "https://mcp.zovo.one/mcp/timezone"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-timezone-world-clock-meeting-slot": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/timezone"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-timezone-world-clock-meeting-slot -t streamable-http -u 'https://mcp.zovo.one/mcp/timezone'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-timezone-world-clock-meeting-slot": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/timezone"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-20 (score 85, +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-18 (score 84, +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-17 (score 83, 0)

- [functional] Server version: 0.21.0 → 0.22.0

### 2026-09-16 (score 83, +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 82, +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.

### 2026-09-12 (score 81, +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.

### 2026-09-11 (score 80, 0)

- [security] Tool “license_activate” rewrote its description, which is the text the model reads
- [security] Tool “convert_time” rewrote its description, which is the text the model reads
- [functional] New prompt “upgrade_to_pro”
- [functional] New resource “pricing”

### 2026-09-10 (score 80, +1)

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

## MCP tools (11)

### `license_status` (~55 tokens)

License status

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.

### `license_activate` (~76 tokens)

Activate license

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.

Input parameters:

- `key` (string, required): License key from checkout, MCPL1.<payload>.<signature>

### `now` (~74 tokens)

Current time in zones

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.

Input parameters:

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

### `convert_time` (~213 tokens)

Convert a time between zones

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.

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

Count business days

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.

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

Save a contact's zone

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.

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

List saved contacts

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.

### `ics_create` (~345 tokens)

Write a calendar invite

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.

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): Name for the downloaded file, default meeting.ics
- `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: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-timezone-world-clock-meeting-slots-overlap-ics/mcp-timezone#diagnostics

## Score history

- 2026-09-20: 85
- 2026-09-19: 84
- 2026-09-18: 84
- 2026-09-17: 83
- 2026-09-16: 83
- 2026-09-15: 82
- 2026-09-14: 82
- 2026-09-13: 81
- 2026-09-12: 81
- 2026-09-11: 80
- 2026-09-10: 80
- 2026-09-09: 79
- 2026-09-08: 79
- 2026-09-07: 36
- 2026-09-06: 36
- 2026-09-05: 36
- 2026-09-04: 36
- 2026-09-03: 36

## Common questions

### What is the io.github.theluckystrike/timezone-world-clock-meeting-slots… MCP server?

io.github.theluckystrike/timezone-world-clock-meeting-slots… is an MCP server listed in the public MCP registry as io.github.theluckystrike/timezone-world-clock-meeting-slots…. Time zone conversion, meeting-slot finding across countries, DST checks and .ics invites. All. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/timezone).

### Is the io.github.theluckystrike/timezone-world-clock-meeting-slots… MCP server safe to use?

io.github.theluckystrike/timezone-world-clock-meeting-slots… scores 85 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/timezone-world-clock-meeting-slots… MCP server expose?

io.github.theluckystrike/timezone-world-clock-meeting-slots… exposes 11 tools: license_status, license_activate, now, convert_time, overlap, and 6 more. Their descriptions and schemas cost roughly 1,566 tokens of context every time the server is loaded.

### Does the io.github.theluckystrike/timezone-world-clock-meeting-slots… MCP server require authentication?

Yes. io.github.theluckystrike/timezone-world-clock-meeting-slots… 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/timezone-world-clock-meeting-slots… MCP server still maintained?

io.github.theluckystrike/timezone-world-clock-meeting-slots… 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.

## Links

- Remote endpoint: https://mcp.zovo.one/mcp/timezone
- Authorisation metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/timezone
- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/timezone
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-timezone-world-clock-meeting-slots-overlap-ics/mcp-timezone.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-timezone-world-clock-meeting-slots-overlap-ics/mcp-timezone.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-timezone-world-clock-meeting-slots-overlap-ics/mcp-timezone