# Zovo Date Poll (remote · date-poll.zovo.one)

Helps a group schedule a time that works for everyone.

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

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

## Channel facts

- Endpoint: `https://date-poll.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-11-21.

- **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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 77/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 1026 tokens (~205/item across 5 items; 4 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.
  - 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the Zovo Date Poll MCP server?

Zovo Date Poll is a hosted endpoint at https://date-poll.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-date-poll 'https://date-poll.zovo.one/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  theluckystrike-date-poll:
    url: "https://date-poll.zovo.one/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "theluckystrike-date-poll": {
      "type": "http",
      "url": "https://date-poll.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-11-21 (score 80, +1)

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

### 2026-11-19 (score 79, +1)

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

### 2026-11-18 (score 78, 0)

- [security] Resource “date-poll-widget” now points somewhere else: ui://widget/date-poll-v1-1.0.0-f7b28e59e60d266cabeb32b8bb6f2fd9282418073295dfd2dd3f1fdd915d2f30.html → ui://widget/date-poll-v2-1.0.1-f7b28e59e60d266cabeb32b8bb6f2fd9282418073295dfd2dd3f1fdd915d2f30.html
- [security] Tool “show_date_poll_results” rewrote its description, which is the text the model reads
- [functional] Server version: 1.0.0 → 1.0.1
- [cosmetic] “show_date_poll_results” added an optional parameter “include_names”

### 2026-11-16 (score 78, +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-11-14 (score 77, +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-11-12 (score 76, +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-11-10 (score 75, +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.

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

- [functional improvement] Stability: unverified → 0.03

## MCP tools (4)

### `create_date_poll` (~384 tokens)

Create date poll

Use this when someone wants to find a date or time that works for a group (a dinner, meeting, call, game night, class). Publishes a shared web page where people answer yes, if need be or no for each proposed time. Returns a public link to share and a private organizer link. Takes 2-30 options as date + start time in one IANA time zone; refuses times that do not exist because of a daylight-saving change. Does not send invitations, emails or reminders. Do not use for a single fixed event that needs no vote.

Input parameters:

- `allow_if_need_be` (boolean): Offer an 'if need be' answer besides yes and no, e.g. true. Default true.
- `duration_minutes` (integer): Default length of each option in minutes (5-1440), e.g. 120. Default 60.
- `hide_names` (boolean): true to show only counts publicly, so only the organizer sees who answered what, e.g. false. Default false.
- `location` (string): Place or call details in words, e.g. Luigi's, Main Street. No links.
- `note` (string): Short note shown on the page, e.g. We will book a table for whoever can come.
- `organizer_name` (string): Organizer's first name shown on the page, e.g. Sam.
- `slots` (array, required): The 2-30 proposed times, e.g. [{"date":"2026-11-14","start":"19:00"},{"date":"2026-11-15","start":"19:00"}].
- `time_zone` (string, required): IANA time zone of the proposed times, e.g. Europe/Berlin or America/New_York.
- `title` (string, required): What the group is meeting for, e.g. Team dinner.

Output parameters:

- `allow_if_need_be` (boolean)
- `best`
- `best_rule` (string)
- `changes` (array)
- `closed` (boolean)
- `expires_at` (string)
- `final`
- `manageUrl` (string)
- `names` (array)
- `names_count` (object)
- `participants` (number)
- `publicUrl` (string)
- `slots` (array)
- `slots_count` (object)
- `time_zone` (string)
- `title` (string)
- `warnings` (array)

### `show_date_poll_results` (~162 tokens)

Show date poll results

Use this when the organizer wants to see who answered a date poll and which time works for the most people. Needs the private organizer link (contains /m/). Returns counts per time and the top time by the stated rule (most yes, then most yes + if need be, then earliest). Only set include_names when the user explicitly asks who answered or requests participant names. Does not change the poll.

Input parameters:

- `include_names` (boolean): Return participant first names only when the user explicitly asks who answered or requests names, e.g. true. Default false returns aggregate counts only.
- `manage_link` (string, required): The private organizer link returned when the poll was made, e.g. https://date-poll.zovo.one/m/<id>/<key>.

Output parameters:

- `allow_if_need_be` (boolean)
- `best`
- `best_rule` (string)
- `changes` (array)
- `closed` (boolean)
- `expires_at` (string)
- `final`
- `manageUrl` (string)
- `names` (array)
- `names_count` (object)
- `participants` (number)
- `publicUrl` (string)
- `slots` (array)
- `slots_count` (object)
- `time_zone` (string)
- `title` (string)
- `warnings` (array)

### `finalize_date_poll` (~154 tokens)

Finalize date poll

Use this when the organizer has decided on the final time of a date poll. Needs the private organizer link. Sets the chosen slot (or the top-ranked slot when slot_number is omitted), stops new answers, and the public page then shows the final time with an Add to calendar file (.ics). Does not notify anyone; share the public link again.

Input parameters:

- `manage_link` (string, required): The private organizer link returned when the poll was made, e.g. https://date-poll.zovo.one/m/<id>/<key>.
- `slot_number` (integer): The number of the chosen time as listed in the results (1 = first option), e.g. 2. Omit to pick the top-ranked time.

Output parameters:

- `allow_if_need_be` (boolean)
- `best`
- `best_rule` (string)
- `changes` (array)
- `closed` (boolean)
- `expires_at` (string)
- `final`
- `manageUrl` (string)
- `names` (array)
- `names_count` (object)
- `participants` (number)
- `publicUrl` (string)
- `slots` (array)
- `slots_count` (object)
- `time_zone` (string)
- `title` (string)
- `warnings` (array)

### `update_date_poll` (~233 tokens)

Update date poll

Use this when the organizer wants to change an existing date poll: add time options, close or reopen voting, or change the title, place or note. Needs the private organizer link. Reopening also clears a final time. Existing answers are kept; people can answer new options with their edit link. Does not remove options or answers.

Input parameters:

- `add_slots` (array): New time options in the poll's time zone, e.g. [{"date":"2026-11-22","start":"19:00"}].
- `location` (string): New place in words, e.g. Luigi's, Main Street.
- `manage_link` (string, required): The private organizer link returned when the poll was made, e.g. https://date-poll.zovo.one/m/<id>/<key>.
- `note` (string): New note shown on the page, e.g. Please answer by Friday.
- `title` (string): New title, e.g. Team dinner (moved).
- `voting` (string): close stops new answers; reopen accepts answers again and clears a final time, e.g. close.

Output parameters:

- `allow_if_need_be` (boolean)
- `best`
- `best_rule` (string)
- `changes` (array)
- `closed` (boolean)
- `expires_at` (string)
- `final`
- `manageUrl` (string)
- `names` (array)
- `names_count` (object)
- `participants` (number)
- `publicUrl` (string)
- `slots` (array)
- `slots_count` (object)
- `time_zone` (string)
- `title` (string)
- `warnings` (array)

## Diagnostics

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

## Score history

- 2026-11-21: 80
- 2026-11-20: 79
- 2026-11-19: 79
- 2026-11-18: 78
- 2026-11-17: 78
- 2026-11-16: 78
- 2026-11-15: 77
- 2026-11-14: 77
- 2026-11-13: 76
- 2026-11-12: 76
- 2026-11-11: 75
- 2026-11-10: 75
- 2026-11-09: 74
- 2026-11-08: 74

## Common questions

### What is the Zovo Date Poll MCP server?

Zovo Date Poll is an MCP server listed in the public MCP registry as io.github.theluckystrike/date-poll. Helps a group schedule a time that works for everyone. This page covers its hosted endpoint (https://date-poll.zovo.one/mcp).

### Is the Zovo Date Poll MCP server safe to use?

Zovo Date Poll scores 80 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 Date Poll MCP server expose?

Zovo Date Poll exposes 4 tools: create_date_poll, show_date_poll_results, finalize_date_poll, update_date_poll. Their descriptions and schemas cost roughly 933 tokens of context every time the server is loaded.

### Does the Zovo Date Poll MCP server require authentication?

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

### Is the Zovo Date Poll MCP server still maintained?

Zovo Date Poll is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Zovo Date Poll MCP server?

VerifyMCP ran 14 checks on Zovo Date Poll, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://date-poll.zovo.one/mcp
- Website: https://date-poll.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-date-poll/date-poll.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-date-poll/date-poll/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-date-poll/date-poll.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-date-poll/date-poll
