# Zovo Meeting Planner (remote · meeting-planner.zovo.one)

Find meeting times across TZs

- Trust score: 73/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `meeting-planner.zovo.one`: 73/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-meeting-planner/meeting-planner.md), [page](https://verifymcp.io/servers/theluckystrike-meeting-planner/meeting-planner)

## Channel facts

- Endpoint: `https://meeting-planner.zovo.one/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-10-23.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 71/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1131 tokens (~377/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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.
  - Supports UI / widget rendering.

## Install

### How do I install the Zovo Meeting Planner MCP server?

Zovo Meeting Planner is a hosted endpoint at https://meeting-planner.zovo.one/mcp, 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-meeting-planner 'https://meeting-planner.zovo.one/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-meeting-planner": {
      "url": "https://meeting-planner.zovo.one/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.theluckystrike-meeting-planner]
url = "https://meeting-planner.zovo.one/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add theluckystrike-meeting-planner --url 'https://meeting-planner.zovo.one/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-meeting-planner:
    url: "https://meeting-planner.zovo.one/mcp"
```

### Netclaw

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

### Vellum

```bash
assistant mcp add theluckystrike-meeting-planner -t streamable-http -u 'https://meeting-planner.zovo.one/mcp'
```

### Other

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

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-10-23 (score 73, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-22 (score 73)

First indexed and scored.

## MCP tools (2)

### `convert_time` (~397 tokens)

Convert time between time zones

Use this when the user wants to convert a time between time zones or cities (time zone converter, e.g. 'convert 3pm PST to IST', 'time zone converter New York to London', 'what time is 9am EST in Warsaw on Nov 3'). Takes a date, a time, a source place (city, IANA zone, US state, country, UTC offset, or abbreviation) and up to 20 target places; returns the same instant in each place with UTC offset, abbreviation, +1/-1 day shift, the hour difference, and a note when a daylight saving change happens within 7 days. Explains times that are skipped or repeated by DST changes. Does not plan meetings (find_meeting_time covers that), look up flight times, or convert units.

Input parameters:

- `date` (string): Local date at the source place as YYYY-MM-DD, e.g. 2026-11-03. Defaults to today at the source. Always pass it when the user names a day, because DST depends on the date.
- `from` (string, required): Source place: a city ("New York", "Portland, Oregon"), an IANA zone ("Europe/Warsaw"), a US state, a country, a UTC offset ("UTC+5:30"), or an abbreviation ("PST", "CET", "IST"). Abbreviations mean t…
- `time` (string): Local time at the source place, 24-hour or 12-hour, e.g. "15:00", "3pm", "9:30 am". Omit (with date) to convert the current moment.
- `to` (array, required): Target places in the same formats, e.g. ["London", "Asia/Kolkata", "Sydney"].

Output parameters:

- `alternate`
- `kind` (string)
- `notes` (array)
- `primary` (object)
- `status` (string)
- `status_note` (string|null)

### `find_meeting_time` (~613 tokens)

Find a meeting time across time zones

Use this when the user wants to plan a meeting across time zones (meeting planner, 'find a 1-hour slot for New York, London and Bangalore on 2026-11-10', working-hour overlap for a distributed team). Takes 2-8 participants' places with optional working hours and work days, a date or date range of up to 14 days, and a duration. Returns up to 10 distinct ranked slots (default 5), ordered by a fairness cost: 2 hours per person outside working hours plus the time outside working hours of the worst-off person, with night (22:00-07:00) and days off weighing more. Each slot lists every participant's local time and status, a calendar (.ics) download link, the flexible window of meeting times when everyone is inside working hours, and other dates with the same local times. If nobody can meet inside working hours in the range, it also returns the closest time within 7 days after the range that works for everyone. Pass selected_start_utc to get the .ics for one specific slot. Does not read calendars, check availability, issue invitations, support overnight working hours, or account for public holidays.

Input parameters:

- `date_from` (string): First day to search, YYYY-MM-DD in the first participant's time zone, e.g. 2026-10-06. Defaults to today there.
- `date_to` (string): Last day to search (inclusive), YYYY-MM-DD, at most 14 days after date_from, e.g. 2026-10-09. Defaults to date_from.
- `duration_minutes` (integer): Meeting length in minutes, e.g. 30 or 60 (default 60).
- `include_weekends` (boolean): Treat every day of the week as a working day for participants without work_days, e.g. true for weekend events (default false).
- `max_results` (integer): How many ranked non-overlapping slots to return, e.g. 5 (default).
- `participants` (array, required): 2-8 participants in order; the first one is the reference whose dates define the range, e.g. [{"place":"New York"},{"place":"London"},{"place":"Bangalore"}].
- `selected_start_utc` (string): Optional chosen start in UTC, e.g. 2026-10-06T14:00:00Z, to get that exact slot's local times and its .ics calendar link.
- `step_minutes` (integer): Slot start granularity in minutes: 15, 30 (default), or 60.
- `title` (string): Meeting title for the calendar file, e.g. "Q4 planning sync".
- `work_end` (string): Default local working-day end for everyone, e.g. "17:00" (default).
- `work_start` (string): Default local working-day start for everyone, e.g. "09:00" (default).

Output parameters:

- `days` (array)
- `downloads` (object)
- `has_full_overlap` (boolean)
- `kind` (string)
- `next_full_overlap`
- `notes` (array)
- `overlap_windows` (array)
- `participants` (array)
- `reference` (string)
- `request` (object)
- `selected`
- `slots` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-meeting-planner/meeting-planner#diagnostics

## Score history

- 2026-10-23: 73
- 2026-10-22: 73

## Common questions

### What is the Zovo Meeting Planner MCP server?

Zovo Meeting Planner is an MCP server listed in the public MCP registry as io.github.theluckystrike/meeting-planner. Find meeting times across TZs. This page covers its hosted endpoint (https://meeting-planner.zovo.one/mcp).

### Is the Zovo Meeting Planner MCP server safe to use?

Zovo Meeting Planner scores 73 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 Zovo Meeting Planner MCP server expose?

Zovo Meeting Planner exposes 2 tools: convert_time, find_meeting_time. Their descriptions and schemas cost roughly 1,010 tokens of context every time the server is loaded.

### Does the Zovo Meeting Planner MCP server require authentication?

No. We connected to Zovo Meeting Planner without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Zovo Meeting Planner MCP server still maintained?

Zovo Meeting Planner is still listed as active in the MCP registry. We last reached this channel on 23 October 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://meeting-planner.zovo.one/mcp
- Website: https://meeting-planner.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-meeting-planner/meeting-planner.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-meeting-planner/meeting-planner.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-meeting-planner/meeting-planner