# Zovo Project Timeline (remote · gantt-timeline.zovo.one)

A Gantt chart maker and project timeline planner that works inside the chat.

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

## Components

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

## Channel facts

- Endpoint: `https://gantt-timeline.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**: 70/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 1058 tokens (~352/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 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.

### Claude

```bash
claude mcp add --transport http theluckystrike-gantt-timeline 'https://gantt-timeline.zovo.one/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  theluckystrike-gantt-timeline:
    url: "https://gantt-timeline.zovo.one/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "theluckystrike-gantt-timeline": {
      "type": "http",
      "url": "https://gantt-timeline.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, 0)

- [functional improvement] Stability: unverified → 0.03

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

First indexed and scored.

## MCP tools (2)

### `plan_project_timeline` (~460 tokens)

Plan project timeline

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.

Input parameters:

- `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, required): Tasks in any order (1 to 150), e.g. [{"id":"A","name":"Design","duration":5},{"id":"B","name":"Build","duration":10,"depends_on":["A"]}].

Output parameters:

- `calendar` (object)
- `calendar_days` (number)
- `critical_path` (array)
- `downloads` (object)
- `end_date` (string)
- `milestones` (array)
- `project_name` (string)
- `request` (object)
- `start_date` (string)
- `tasks` (array)
- `warnings` (array)
- `working_days` (number)

### `compare_timeline_scenarios` (~481 tokens)

Compare timeline what-ifs

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).

Input parameters:

- `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, required): 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, required): Tasks in any order (1 to 150), e.g. [{"id":"A","name":"Design","duration":5},{"id":"B","name":"Build","duration":10,"depends_on":["A"]}].

Output parameters:

- `baseline` (object)
- `latest_finish` (string)
- `project_name` (string)
- `scenarios` (array)
- `warnings` (array)

## Diagnostics

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

## Score history

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

## Common questions

### 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.

## Links

- Remote endpoint: https://gantt-timeline.zovo.one/mcp
- Website: https://gantt-timeline.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-gantt-timeline/gantt-timeline.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-gantt-timeline/gantt-timeline.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-gantt-timeline/gantt-timeline