Zovo Meeting Planner
REMOTE · MEETING-PLANNER.ZOVO.ONE
Find meeting times across TZs
Available components
Last scanned (8 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Productivity and Notes
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
- Supports UI / widget rendering.Pass
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.
- 23 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 22 Oct 26 73
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 23 Oct 2026 · Probed https://meeting-planner.zovo.one/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | fcd646954518fe4a13f1ed1316347e04 |
| SANs: zovo.one, meeting-planner.zovo.one, *.meeting-planner.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of meeting-planner.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://meeting-planner.zovo.one/mcp | Verified | 200 | |
| http (plaintext) | http://meeting-planner.zovo.one/mcp | HTTPS enforced | 301 | https://meeting-planner.zovo.one/mcp |
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 →
convert_time Convert time between time zones ~397
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | Target places in the same formats, e.g. ["London", "Asia/Kolkata", "Sydney"]. |
| Name | Type | Req | Description |
|---|---|---|---|
| alternate | – | yes | – |
| kind | string | yes | – |
| notes | array | yes | – |
| primary | object | yes | – |
| status | string | yes | – |
| status_note | string|null | yes | – |
No examples provided.
find_meeting_time Find a meeting time across time zones ~613
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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). |
| Name | Type | Req | Description |
|---|---|---|---|
| days | array | yes | – |
| downloads | object | yes | – |
| has_full_overlap | boolean | yes | – |
| kind | string | yes | – |
| next_full_overlap | – | yes | – |
| notes | array | yes | – |
| overlap_windows | array | yes | – |
| participants | array | yes | – |
| reference | string | yes | – |
| request | object | yes | – |
| selected | – | yes | – |
| slots | array | yes | – |
No examples provided.
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.
remote · meeting-planner.zovo.one
claude mcp add --transport http theluckystrike-meeting-planner 'https://meeting-planner.zovo.one/mcp'
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.