# Zovo Date Poll

> Helps a group schedule a time that works for everyone.

- name: io.github.theluckystrike/date-poll
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 80/100 flags: no-repository
- quality: 94/100 (new)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.theluckystrike%2Fdate-poll
- tools: https://api.protogrid.dev/v1/servers/io.github.theluckystrike%2Fdate-poll/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 80
- liveness: 100
- freshness: 100
- provenance: 45
- drivers: +website +reachable +uptime-100% +updated-6d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 94/100 (new)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list declares ttlMs 0, so clients re-fetch it on every use

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 4 of 4 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 1,527 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump
- pass `tools.hidden_text`: no hidden text in tool names, descriptions, schemas or annotations

### stability: n/a (weight 15)

- n/a `stability.changes`, `stability.rug_pull`, `stability.new_links`: tool history recorded for 6 of the 7 days needed

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 4, about 1,527 tokens to load them all
- tool set hash: f394499092a6f5797ca0775c477c7083
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.theluckystrike/date-poll.svg)](https://protogrid.dev/servers/io.github.theluckystrike/date-poll)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://date-poll.zovo.one/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (4)

- `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.
- `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.
- `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, names, and the top time by the stated rule (most yes, then most yes + if need be, then earliest). Does not change the poll.
- `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.