# io.github.theluckystrike/deliverable-tracker (remote · mcp.zovo.one)

Deliverables with a due date and a sign-off: what has slipped, and what is ready to bill.

- Trust score: 80/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `mcp.zovo.one`: 80/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-deliverable-tracker/mcp-delivery-schedule.md), [page](https://verifymcp.io/servers/theluckystrike-deliverable-tracker/mcp-delivery-schedule)
- mcpb · `delivery-schedule.mcpb`: 47/100, [markdown](https://verifymcp.io/servers/theluckystrike-deliverable-tracker/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-delivery-s.md), [page](https://verifymcp.io/servers/theluckystrike-deliverable-tracker/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-delivery-s)

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/delivery-schedule`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.22.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-09-21.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - 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**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1856 tokens (~132/item across 14 items; 12 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 95% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 13 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.

## Install

### How do I install the io.github.theluckystrike/deliverable-tracker MCP server?

io.github.theluckystrike/deliverable-tracker is a hosted endpoint at https://mcp.zovo.one/mcp/delivery-schedule, 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-deliverable-tracker 'https://mcp.zovo.one/mcp/delivery-schedule'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-deliverable-tracker": {
      "url": "https://mcp.zovo.one/mcp/delivery-schedule"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-deliverable-tracker": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/delivery-schedule"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-deliverable-tracker]
url = "https://mcp.zovo.one/mcp/delivery-schedule"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add theluckystrike-deliverable-tracker --url 'https://mcp.zovo.one/mcp/delivery-schedule' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-deliverable-tracker:
    url: "https://mcp.zovo.one/mcp/delivery-schedule"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-deliverable-tracker": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/delivery-schedule"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-deliverable-tracker -t streamable-http -u 'https://mcp.zovo.one/mcp/delivery-schedule'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-deliverable-tracker": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/delivery-schedule"
    }
  }
}
```

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-09-21 (score 80, +2)

- [security] Tool “deliverable_delete” is now declared destructive
- [security] Tool “delivery_schedule_delete” is now declared destructive
- [functional] Destructive annotations: All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.

### 2026-09-19 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 77, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-17 (score 77)

First indexed and scored.

## MCP tools (12)

### `delivery_schedule_create` (~249 tokens)

Open a delivery schedule

Open a delivery schedule against a quote, work order or change order and return its DS-YYYY-NNNN number: the reference, its own date, the client, a title and the currency. Free tier: 3 open.

Input parameters:

- `client` (string, required): The client the work is delivered to, as named on the reference document
- `currency` (string): ISO code the deliverables are priced in. Defaults to the shared business profile's currency
- `note` (string)
- `reference` (string, required): The quote, work order or change order this schedule delivers, by its id, e.g. WO-2026-0001, Q-2026-0003 or CO-2026-0001
- `reference_date` (string, required): The date on the reference document itself, YYYY-MM-DD. No due date and no delivery may fall before it
- `reference_kind` (string): What the reference is. Inferred from the id when omitted: WO- is a work order, CO- a change order, anything else a quote
- `title` (string, required): What the job is, in one line, e.g. Website rebuild, phase one

### `deliverable_add` (~263 tokens)

Add a dated deliverable

Add one dated deliverable and return its D number and the new counts. value_minor is NET of VAT in whole MINOR units. A due date before the reference document's own date is refused. It starts as planned.

Input parameters:

- `description` (string, required): What is being handed over, as the client would recognise it, e.g. Wireframes for the five main pages
- `due_date` (string, required): The day it is due, YYYY-MM-DD. It cannot fall before the reference document's own date
- `duplicate_ok` (boolean): Add it even though this schedule already carries the same description due on the same day. Default false
- `note` (string)
- `schedule` (string, required): The schedule id, e.g. DS-2026-0001, the reference it delivers, e.g. WO-2026-0001, or its title
- `tax_rate` (number): VAT percent for this deliverable, overriding the shared business profile's default
- `value_minor` (integer): What this deliverable is worth, net of VAT, in whole minor units. 90000 is EUR 900.00. Leave it out when the job is a lump sum and this deliverable carries no price of its own

### `deliverable_status` (~203 tokens)

Move a deliverable along

Record a dated move on one deliverable: planned, in_progress, delivered, then accepted with a note. An out-of-order move, or a date before the reference document, is refused. The date drives lateness.

Input parameters:

- `date` (string): The day it happened, YYYY-MM-DD. Default today. This is the date every late reading is taken against, not the day you type it
- `deliverable` (string, required): The deliverable id, e.g. D01, or its description when only one carries it
- `note` (string): What happened. On accepted this is the acceptance note, e.g. Signed off by the client on the call, no snags
- `schedule` (string, required): The schedule id, e.g. DS-2026-0001, the reference it delivers, e.g. WO-2026-0001, or its title
- `status` (string, required): The status to move to

### `deliverable_delete` (~117 tokens)

Delete a planned deliverable

Delete one deliverable still planned with no history. One started, delivered or accepted is refused, naming when: add a corrected deliverable instead. The D number on a schedule is never reissued.

Input parameters:

- `deliverable` (string, required): The deliverable id, e.g. D01, or its description when only one carries it
- `schedule` (string, required): The schedule id, e.g. DS-2026-0001, the reference it delivers, e.g. WO-2026-0001, or its title

### `delivery_schedule_get` (~118 tokens)

Show one delivery schedule

Return one schedule in full as at a date: every deliverable with due date, status, delivered and accepted dates, note and value, plus what is late and the totals. The answer names the as_of it used.

Input parameters:

- `as_of` (string): Read the schedule as at this date, YYYY-MM-DD. Defaults to today
- `schedule` (string, required): The schedule id, e.g. DS-2026-0001, the reference it delivers, e.g. WO-2026-0001, or its title

### `delivery_schedule_list` (~147 tokens)

List delivery schedules

List schedules oldest reference first with client, currency and counts as at a date: late, still owed, accepted. Filter by client, reference and state open or complete. Free.

Input parameters:

- `as_of` (string): Read the schedule as at this date, YYYY-MM-DD. Defaults to today
- `client` (string): Only schedules whose client name contains this text
- `limit` (integer): Maximum schedules returned, default and ceiling 500
- `reference` (string): Only the schedule against this quote, work order or change order
- `state` (string): open for a job with a deliverable that is not yet accepted, complete for one where every deliverable is

### `delivery_schedule_delete` (~92 tokens)

Delete an empty schedule

Delete a schedule carrying no deliverables, freeing an open slot. One holding any is refused, naming them, since they record what was owed. The DS number is never reissued. Free on every tier.

Input parameters:

- `schedule` (string, required): The schedule id, e.g. DS-2026-0001, the reference it delivers, e.g. WO-2026-0001, or its title

### `late_report` (~169 tokens)

What is late as at a date

What has slipped as at a date: every deliverable still owed past its due date, worst first, with value at risk per currency, and what was delivered late kept apart. A reference with no schedule is refused.

Input parameters:

- `as_of` (string): Read lateness as at this date, YYYY-MM-DD. Defaults to today. Everything in the answer is as at this date, not as at now
- `client` (string): Only schedules whose client name contains this text
- `include_delivered_late` (boolean): Include what was handed over after its due date but is no longer outstanding. Default true
- `limit` (integer): Maximum rows per section, default and ceiling 500
- `reference` (string): Only the schedule against this quote, work order or change order

### `delivery_schedule_document` (~117 tokens)

Delivery schedule document

Render one schedule as a plain-text document for the client: every deliverable with its due date, status, delivered and accepted dates and value, the counts as at a date, and a sign-off block. Pro.

Input parameters:

- `as_of` (string): Read the schedule as at this date, YYYY-MM-DD. Defaults to today
- `schedule` (string, required): The schedule id, e.g. DS-2026-0001, the reference it delivers, e.g. WO-2026-0001, or its title

### `milestone_payload` (~159 tokens)

Invoice payload for accepted milestones

Build the delivered-and-accepted deliverables as invoice_create-ready items in MAJOR units and quote_create-ready items in MINOR units, with VAT at the shared profile rate. Writes nothing. Pro.

Input parameters:

- `as_of` (string): Bill what had been accepted by this date, YYYY-MM-DD. Defaults to today
- `issue_date` (string): The invoice issue date, YYYY-MM-DD. Default today
- `schedule` (string, required): The schedule id, e.g. DS-2026-0001, the reference it delivers, e.g. WO-2026-0001, or its title
- `tax_rate` (number): VAT percent for deliverables with no rate of their own, overriding the shared business profile's default

### `license_status` (~55 tokens)

License status

Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.

### `license_activate` (~76 tokens)

Activate license

Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.

Input parameters:

- `key` (string, required): License key from checkout, MCPL1.<payload>.<signature>

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-deliverable-tracker/mcp-delivery-schedule#diagnostics

## Score history

- 2026-09-21: 80
- 2026-09-20: 78
- 2026-09-19: 78
- 2026-09-18: 77
- 2026-09-17: 77

## Common questions

### What is the io.github.theluckystrike/deliverable-tracker MCP server?

io.github.theluckystrike/deliverable-tracker is an MCP server listed in the public MCP registry as io.github.theluckystrike/deliverable-tracker. Deliverables with a due date and a sign-off: what has slipped, and what is ready to bill. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/delivery-schedule).

### Is the io.github.theluckystrike/deliverable-tracker MCP server safe to use?

io.github.theluckystrike/deliverable-tracker scores 80 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 io.github.theluckystrike/deliverable-tracker MCP server expose?

io.github.theluckystrike/deliverable-tracker exposes 12 tools: delivery_schedule_create, deliverable_add, deliverable_status, deliverable_delete, delivery_schedule_get, and 7 more. Their descriptions and schemas cost roughly 1,765 tokens of context every time the server is loaded.

### Does the io.github.theluckystrike/deliverable-tracker MCP server require authentication?

Yes. io.github.theluckystrike/deliverable-tracker asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the io.github.theluckystrike/deliverable-tracker MCP server still maintained?

io.github.theluckystrike/deliverable-tracker is still listed as active in the MCP registry. We last reached this channel on 21 September 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://mcp.zovo.one/mcp/delivery-schedule
- Authorisation metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/delivery-schedule
- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/delivery-schedule
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-deliverable-tracker/mcp-delivery-schedule.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-deliverable-tracker/mcp-delivery-schedule.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-deliverable-tracker/mcp-delivery-schedule