Zovo Project Timeline
REMOTE · GANTT-TIMELINE.ZOVO.ONE
A Gantt chart maker and project timeline planner that works inside the chat.
Available components
Last scanned (7 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Project Management
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 Usability70
- 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 1058 tokens (~352/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 0
- Stability: unverified → 0.03 ▲ functional
- 22 Oct 26 73
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://gantt-timeline.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 | fdf929cafda921a213e37489325b9864 |
| SANs: zovo.one, gantt-timeline.zovo.one, *.gantt-timeline.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 gantt-timeline.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://gantt-timeline.zovo.one/mcp | Verified | 200 | |
| http (plaintext) | http://gantt-timeline.zovo.one/mcp | HTTPS enforced | 301 | https://gantt-timeline.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 →
compare_timeline_scenarios Compare timeline what-ifs ~481
Use this when the user asks what happens to a project schedule if a task slips, takes longer or shorter, or starts later: for example "if Design slips 5 days, when do we finish?" or "does the critical path change?". Takes the same task list and calendar as plan_project_timeline plus 1 to 4 scenarios, each with changes (extra_days, a new duration, or a new start-no-earlier-than date). Returns the baseline and each scenario's end date, the delay in working and calendar days, the new critical path, tasks that became or stopped being critical, and how much of each slip was absorbed by float. Does not change or save the plan. Do not use for the first schedule of a project (use plan_project_timeline).
| Name | Type | Req | Description |
|---|---|---|---|
| calendar | string | – | business_days (default) counts Monday to Friday and skips public holidays of country; calendar_days counts every day. |
| country | string | – | Country whose public holidays are skipped in business_days mode, as a 2-letter code or name, e.g. US, GB, DE, PL. |
| duration_unit | string | – | Default unit for every task duration: days (default) or weeks. |
| non_working_dates | array | – | Extra days off such as a company shutdown, YYYY-MM-DD, e.g. ["2026-12-28", "2026-12-29"]. |
| project_name | string | – | Project title for the chart and files, e.g. "Website relaunch". |
| scenarios | array | yes | 1 to 4 what-if scenarios compared with the baseline plan, e.g. [{"label":"Design +5","changes":[{"task":"Design","extra_days":5}]}]. |
| start_date | string | – | Project start date YYYY-MM-DD, e.g. 2026-11-02. Defaults to today. Convert relative dates ("next Monday") to a date first. |
| subdivision | string | – | State or region code for regional holidays, e.g. CA for California or BY for Bavaria. |
| tasks | array | yes | Tasks in any order (1 to 150), e.g. [{"id":"A","name":"Design","duration":5},{"id":"B","name":"Build","duration":10,"depends_on":["A"]}]. |
| Name | Type | Req | Description |
|---|---|---|---|
| baseline | object | yes | – |
| latest_finish | string | yes | – |
| project_name | string | yes | – |
| scenarios | array | yes | – |
| warnings | array | yes | – |
No examples provided.
plan_project_timeline Plan project timeline ~460
Use this when the user wants a Gantt chart, project timeline, project schedule or project plan with milestones from a task list, wants to find the critical path and project duration, or asks for early start, early finish, late start, late finish, total float or free float (critical path method). Takes tasks with durations (days or weeks), finish-to-start dependencies with optional lags, optional start-no-earlier-than dates, owners and milestones, plus a start date and a business-day calendar with country public holidays or calendar days. Returns every task's dates and float, the critical path, milestones and the end date, an interactive Gantt chart, and CSV, .ics and SVG downloads. Detects dependency loops and unknown task names. Does not save projects, sync with project tools, track progress, or level resources. Do not use for a single date difference or for daily to-do planning.
| Name | Type | Req | Description |
|---|---|---|---|
| calendar | string | – | business_days (default) counts Monday to Friday and skips public holidays of country; calendar_days counts every day. |
| country | string | – | Country whose public holidays are skipped in business_days mode, as a 2-letter code or name, e.g. US, GB, DE, PL. |
| duration_unit | string | – | Default unit for every task duration: days (default) or weeks. |
| non_working_dates | array | – | Extra days off such as a company shutdown, YYYY-MM-DD, e.g. ["2026-12-28", "2026-12-29"]. |
| project_name | string | – | Project title for the chart and files, e.g. "Website relaunch". |
| start_date | string | – | Project start date YYYY-MM-DD, e.g. 2026-11-02. Defaults to today. Convert relative dates ("next Monday") to a date first. |
| subdivision | string | – | State or region code for regional holidays, e.g. CA for California or BY for Bavaria. |
| tasks | array | yes | Tasks in any order (1 to 150), e.g. [{"id":"A","name":"Design","duration":5},{"id":"B","name":"Build","duration":10,"depends_on":["A"]}]. |
| Name | Type | Req | Description |
|---|---|---|---|
| calendar | object | yes | – |
| calendar_days | number | yes | – |
| critical_path | array | yes | – |
| downloads | object | yes | – |
| end_date | string | yes | – |
| milestones | array | yes | – |
| project_name | string | yes | – |
| request | object | yes | – |
| start_date | string | yes | – |
| tasks | array | yes | – |
| warnings | array | yes | – |
| working_days | number | yes | – |
No examples provided.
How do I install the Zovo Project Timeline MCP server?
Zovo Project Timeline is a hosted endpoint at https://gantt-timeline.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 · gantt-timeline.zovo.one
claude mcp add --transport http theluckystrike-gantt-timeline 'https://gantt-timeline.zovo.one/mcp'
What is the Zovo Project Timeline MCP server?
Zovo Project Timeline is an MCP server listed in the public MCP registry as io.github.theluckystrike/gantt-timeline. A Gantt chart maker and project timeline planner that works inside the chat. This page covers its hosted endpoint (https://gantt-timeline.zovo.one/mcp).
Is the Zovo Project Timeline MCP server safe to use?
Zovo Project Timeline 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 Project Timeline MCP server expose?
Zovo Project Timeline exposes 2 tools: plan_project_timeline, compare_timeline_scenarios. Their descriptions and schemas cost roughly 941 tokens of context every time the server is loaded.
Does the Zovo Project Timeline MCP server require authentication?
No. We connected to Zovo Project Timeline without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Zovo Project Timeline MCP server still maintained?
Zovo Project Timeline 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.