# Zovo Focus Timer (remote · focus-timer.zovo.one)

Plan work sessions and run pomodoro timers right in the conversation.

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

## Components

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

## Channel facts

- Endpoint: `https://focus-timer.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**: 68/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 1511 tokens (~503/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 Focus Timer MCP server?

Zovo Focus Timer is a hosted endpoint at https://focus-timer.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-focus-timer 'https://focus-timer.zovo.one/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  theluckystrike-focus-timer:
    url: "https://focus-timer.zovo.one/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "theluckystrike-focus-timer": {
      "type": "http",
      "url": "https://focus-timer.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, +1)

- [functional improvement] Stability: unverified → 0.03

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

First indexed and scored.

## MCP tools (2)

### `show_focus_timer` (~725 tokens)

Show focus timer

Use this when the user wants a timer now: a pomodoro timer (25/5, 50/10, pomodoro timer for studying), a countdown timer ("10-minute timer"), or an interval timer (work/rest repeats, e.g. 45 s on, 15 s off). Returns the full phase plan (focus blocks, short and long breaks, totals) and shows a live timer with a progress ring, play, pause, skip and reset controls, and an optional chime. With a clock time for the first block and a time zone (IANA name such as Europe/Warsaw, a city, or an abbreviation such as EST), each phase also gets wall-clock times that stay correct across daylight-saving changes. Limits: up to 24 hours and 96 rounds; no phone notifications, alarms when the chat is closed, or music. Do not use for reminders about future appointments, questions about how long something takes (e.g. boiling an egg), or unit conversions.

Input parameters:

- `auto_advance` (boolean): Start the next phase automatically when one ends. Default true; false pauses after each phase until the user presses Start.
- `date` (string): Optional date of start_time as YYYY-MM-DD, e.g. 2026-10-02. Defaults to today in time_zone.
- `label` (string): What the user is focusing on, shown on the timer, e.g. "Biology chapter 3" or "Presentation practice".
- `long_break_every` (integer): Take the long break after this many blocks, e.g. 4 (pomodoro default). 0 = never.
- `long_break_minutes` (number): Longer break taken after every long_break_every blocks, in minutes, e.g. 15 (pomodoro default).
- `mode` (string, required): Timer type: "pomodoro" (focus blocks with short and long breaks, e.g. 25/5), "countdown" (one countdown, e.g. 10 minutes), or "interval" (repeating work/rest, e.g. 45 s on, 15 s off).
- `rounds` (integer): Number of focus blocks, e.g. 4 (pomodoro default). Ignored for countdown.
- `short_break_minutes` (number): Break between blocks in minutes, e.g. 5 (pomodoro default) or 10 for 50/10. For interval mode this is the rest, e.g. 0.25 = 15 seconds. 0 = no break.
- `sound` (boolean): Play a short chime when each phase ends. Default true.
- `start_time` (string): Optional clock time the session starts, as HH:MM (24-hour) or 9:30 am, e.g. 14:00. When given, every phase gets wall-clock start and end times.
- `time_zone` (string): Optional time zone for start_time: an IANA name (e.g. Europe/Warsaw, America/New_York), a city (e.g. Warsaw), or an abbreviation (e.g. EST, CET). Makes the clock times correct across daylight-saving…
- `work_minutes` (number): Length of each focus or work block in minutes, e.g. 25 for a classic pomodoro or 50 for 50/10. For countdown this is the countdown length, e.g. 10. Decimals allowed: 0.5 = 30 seconds. Default 25 for…

Output parameters:

- `downloads` (object)
- `label` (string)
- `mode` (string)
- `notes` (array)
- `phase_count` (number)
- `phases` (array)
- `phases_truncated` (boolean)
- `schedule`
- `settings` (object)
- `spare_minutes` (number|null)
- `summary` (string)
- `totals` (object)

### `plan_focus_session` (~706 tokens)

Plan focus session

Use this when the user wants pomodoros fitted into a time window: "I have 3 hours to study until 5pm", "plan pomodoros from 9:00 to 12:30 with a lunch break", "how many 50/10 blocks fit before my 3pm meeting". Fits the most whole focus blocks between the start and end time around fixed breaks (if the standard long break would cost a block, it shortens or drops it and says so, unless the user gave long-break settings) and returns clock times for every block, total focus minutes, spare time, an .ics calendar file with one event per focus block, and a live timer for the plan. Limits: one window of up to 24 hours; it does not read or change the user's calendar and does not build multi-day study plans (e.g. finals week).

Input parameters:

- `available_minutes` (number): Total time available in minutes, e.g. 180 for "I have 3 hours". Used with start_time or end_time. Max 1440.
- `breaks` (array): Fixed breaks the plan must avoid, e.g. [{"start":"12:00","end":"12:45","label":"Lunch"}].
- `date` (string): Date of the session as YYYY-MM-DD, e.g. 2026-10-02. Defaults to today in time_zone.
- `end_time` (string): When the session must end, e.g. 17:00 or 5pm (for "until 5pm"). Earlier times mean the next day; equal start and end times are refused. A bare hour such as 5 after a 14:00 start is read as 5pm, with…
- `label` (string): Topic used for calendar event titles, e.g. "Study: organic chemistry". Default "Focus".
- `long_break_every` (integer): Long break after this many focus blocks, e.g. 4 (default). 0 = never. Leave unset unless the user asks.
- `long_break_minutes` (number): Long break in minutes, e.g. 15. Leave unset unless the user asks for one: by default it is 15 and may be shortened when that fits an extra focus block.
- `rounds` (integer): Maximum number of pomodoros to schedule, e.g. 6. Without an end time the plan runs until this many are done.
- `short_break_minutes` (number): Break between focus blocks in minutes, e.g. 5 (default) or 10.
- `start_time` (string): When the session starts, as HH:MM or 9:00 am, e.g. 09:00. Needed unless end_time is given with available_minutes or rounds.
- `time_zone` (string): Time zone of the clock times: an IANA name (e.g. Europe/Warsaw), a city (e.g. New York), or an abbreviation (e.g. EST). With a zone, calendar events use absolute timestamps. With an explicit date and…
- `work_minutes` (number): Focus block length in minutes, e.g. 25 (default) or 50.

Output parameters:

- `downloads` (object)
- `label` (string)
- `mode` (string)
- `notes` (array)
- `phase_count` (number)
- `phases` (array)
- `phases_truncated` (boolean)
- `schedule`
- `settings` (object)
- `spare_minutes` (number|null)
- `summary` (string)
- `totals` (object)

## Diagnostics

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

## Score history

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

## Common questions

### What is the Zovo Focus Timer MCP server?

Zovo Focus Timer is an MCP server listed in the public MCP registry as io.github.theluckystrike/focus-timer. Plan work sessions and run pomodoro timers right in the conversation. This page covers its hosted endpoint (https://focus-timer.zovo.one/mcp).

### Is the Zovo Focus Timer MCP server safe to use?

Zovo Focus Timer 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 Focus Timer MCP server expose?

Zovo Focus Timer exposes 2 tools: show_focus_timer, plan_focus_session. Their descriptions and schemas cost roughly 1,431 tokens of context every time the server is loaded.

### Does the Zovo Focus Timer MCP server require authentication?

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

### Is the Zovo Focus Timer MCP server still maintained?

Zovo Focus Timer 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://focus-timer.zovo.one/mcp
- Website: https://focus-timer.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-focus-timer/focus-timer.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-focus-timer/focus-timer.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-focus-timer/focus-timer