Zovo Focus Timer
REMOTE · FOCUS-TIMER.ZOVO.ONE
Plan work sessions and run pomodoro timers right in the conversation.
Available components
Last scanned (3 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 Usability68
- 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 1511 tokens (~503/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 +1
- Stability: unverified → 0.03 ▲ functional
- 22 Oct 26 72
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://focus-timer.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 | 9ffb3ccbccd76e1f0e220f1909f099de |
| SANs: zovo.one, focus-timer.zovo.one, *.focus-timer.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 focus-timer.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://focus-timer.zovo.one/mcp | Verified | 200 | |
| http (plaintext) | http://focus-timer.zovo.one/mcp | HTTPS enforced | 301 | https://focus-timer.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 →
plan_focus_session Plan focus session ~706
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| downloads | object | yes | – |
| label | string | yes | – |
| mode | string | yes | – |
| notes | array | yes | – |
| phase_count | number | – | – |
| phases | array | yes | – |
| phases_truncated | boolean | – | – |
| schedule | – | yes | – |
| settings | object | yes | – |
| spare_minutes | number|null | yes | – |
| summary | string | yes | – |
| totals | object | yes | – |
No examples provided.
show_focus_timer Show focus timer ~725
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| downloads | object | yes | – |
| label | string | yes | – |
| mode | string | yes | – |
| notes | array | yes | – |
| phase_count | number | – | – |
| phases | array | yes | – |
| phases_truncated | boolean | – | – |
| schedule | – | yes | – |
| settings | object | yes | – |
| spare_minutes | number|null | yes | – |
| summary | string | yes | – |
| totals | object | yes | – |
No examples provided.
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.
remote · focus-timer.zovo.one
claude mcp add --transport http theluckystrike-focus-timer 'https://focus-timer.zovo.one/mcp'
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.