Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Zovo Date Poll

REMOTE · DATE-POLL.ZOVO.ONE

Helps a group schedule a time that works for everyone.

+3 this week 80 Trust /100

Last scanned (19 hours ago)

Scores higher than 77% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Productivity and Notes

Trust breakdown (7 categories)

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. 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. 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
Schema Quality & AI Usability77
  • 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 1026 tokens (~205/item across 5 items; 4 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 Management43
  • Stability observed for 13 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 18 Nov 26 0
    • 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 security
    • Server version: 1.0.0 → 1.0.1 functional
    • “show_date_poll_results” added an optional parameter “include_names” cosmetic
  • 16 Nov 26 +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.

  • 14 Nov 26 +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.

  • 12 Nov 26 +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.

  • 10 Nov 26 +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.

  • 9 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

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 21 Nov 2026 · Probed https://date-poll.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 3 Oct 2026 1 Jan 2027 ECDSA 256 ECDSA-SHA256 1a6be51dae225a780e14b5b59cd24fa3
SANs: zovo.one, *.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 date-poll.zovo.one. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
one. DS published 64939 8 Verified
zovo.one. No DS 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://date-poll.zovo.one/mcp Verified 200
http (plaintext) http://date-poll.zovo.one/mcp HTTPS enforced 301 https://date-poll.zovo.one/mcp
MCP tools · 4 exposed · ~933 tokens

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 →

Tool Tokens
create_date_poll ~384

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.

NameTypeReqDescription
allow_if_need_beboolean–Offer an 'if need be' answer besides yes and no, e.g. true. Default true.
duration_minutesinteger–Default length of each option in minutes (5-1440), e.g. 120. Default 60.
hide_namesboolean–true to show only counts publicly, so only the organizer sees who answered what, e.g. false. Default false.
locationstring–Place or call details in words, e.g. Luigi's, Main Street. No links.
notestring–Short note shown on the page, e.g. We will book a table for whoever can come.
organizer_namestring–Organizer's first name shown on the page, e.g. Sam.
slotsarrayyesThe 2-30 proposed times, e.g. [{"date":"2026-11-14","start":"19:00"},{"date":"2026-11-15","start":"19:00"}].
time_zonestringyesIANA time zone of the proposed times, e.g. Europe/Berlin or America/New_York.
titlestringyesWhat the group is meeting for, e.g. Team dinner.
NameTypeReqDescription
allow_if_need_bebooleanyes–
best–yes–
best_rulestringyes–
changesarrayyes–
closedbooleanyes–
expires_atstringyes–
final–yes–
manageUrlstringyes–
namesarray––
names_countobject––
participantsnumberyes–
publicUrlstringyes–
slotsarrayyes–
slots_countobject––
time_zonestringyes–
titlestringyes–
warningsarrayyes–

No examples provided.

finalize_date_poll ~154

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.

NameTypeReqDescription
manage_linkstringyesThe private organizer link returned when the poll was made, e.g. https://date-poll.zovo.one/m/<id>/<key>.
slot_numberinteger–The number of the chosen time as listed in the results (1 = first option), e.g. 2. Omit to pick the top-ranked time.
NameTypeReqDescription
allow_if_need_bebooleanyes–
best–yes–
best_rulestringyes–
changesarrayyes–
closedbooleanyes–
expires_atstringyes–
final–yes–
manageUrlstringyes–
namesarray––
names_countobject––
participantsnumberyes–
publicUrlstringyes–
slotsarrayyes–
slots_countobject––
time_zonestringyes–
titlestringyes–
warningsarrayyes–

No examples provided.

show_date_poll_results ~162

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.

NameTypeReqDescription
include_namesboolean–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_linkstringyesThe private organizer link returned when the poll was made, e.g. https://date-poll.zovo.one/m/<id>/<key>.
NameTypeReqDescription
allow_if_need_bebooleanyes–
best–yes–
best_rulestringyes–
changesarrayyes–
closedbooleanyes–
expires_atstringyes–
final–yes–
manageUrlstringyes–
namesarray––
names_countobject––
participantsnumberyes–
publicUrlstringyes–
slotsarrayyes–
slots_countobject––
time_zonestringyes–
titlestringyes–
warningsarrayyes–

No examples provided.

update_date_poll ~233

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.

NameTypeReqDescription
add_slotsarray–New time options in the poll's time zone, e.g. [{"date":"2026-11-22","start":"19:00"}].
locationstring–New place in words, e.g. Luigi's, Main Street.
manage_linkstringyesThe private organizer link returned when the poll was made, e.g. https://date-poll.zovo.one/m/<id>/<key>.
notestring–New note shown on the page, e.g. Please answer by Friday.
titlestring–New title, e.g. Team dinner (moved).
votingstring–close stops new answers; reopen accepts answers again and clears a final time, e.g. close.
NameTypeReqDescription
allow_if_need_bebooleanyes–
best–yes–
best_rulestringyes–
changesarrayyes–
closedbooleanyes–
expires_atstringyes–
final–yes–
manageUrlstringyes–
namesarray––
names_countobject––
participantsnumberyes–
publicUrlstringyes–
slotsarrayyes–
slots_countobject––
time_zonestringyes–
titlestringyes–
warningsarrayyes–

No examples provided.

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.

remote · date-poll.zovo.one

# add to Claude Code
claude mcp add --transport http theluckystrike-date-poll 'https://date-poll.zovo.one/mcp'
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.