# io.github.theluckystrike/milestone-schedule (mcpb · delivery-schedule.mcpb)

Milestone billing from accepted deliverables: due dates, sign-off dates, invoice-ready items.

- Trust score: 47/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-30

## Components

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

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/delivery-schedule.mcpb`
- Version: `0.22.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-30.

- **Supply Chain Security**: 22/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs were checked across the 153 of 153 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - 63 of 153 dependencies flagged as unhealthy (2 deprecated).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 12 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 83/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 1798 tokens (~138/item across 13 items; 12 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "deliverable_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - 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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the io.github.theluckystrike/milestone-schedule MCP server?

io.github.theluckystrike/milestone-schedule ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check the download against.

- Download bundle: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/delivery-schedule.mcpb`

## 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-28 (score 47, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 47, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 47)

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` (~54 tokens)

License status

Report this server's licence state: product, tier free or pro, licence id, expiry, the key source and the upgrade URL. No arguments, no network. Explains a free-tier refusal; license_activate installs a key.

### `license_activate` (~71 tokens)

Activate license

Activate a Pro key (MCPL1.xxx.yyy) from checkout: verified offline against a built-in public key, saved to your config file. A wrong, malformed or expired key is refused, unsaved. license_status reads it back.

Input parameters:

- `key` (string, required): License key from the checkout confirmation page

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/theluckystrike-milestone-schedule/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-delivery-s#diagnostics

## Score history

- 2026-09-30: 47
- 2026-09-29: 47
- 2026-09-28: 47
- 2026-09-27: 47
- 2026-09-26: 47
- 2026-09-25: 47
- 2026-09-24: 47
- 2026-09-23: 47

## Common questions

### What is the io.github.theluckystrike/milestone-schedule MCP server?

io.github.theluckystrike/milestone-schedule is an MCP server listed in the public MCP registry as io.github.theluckystrike/milestone-schedule. Milestone billing from accepted deliverables: due dates, sign-off dates, invoice-ready items. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/delivery-schedule.mcpb).

### Is the io.github.theluckystrike/milestone-schedule MCP server safe to use?

io.github.theluckystrike/milestone-schedule scores 47 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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/milestone-schedule MCP server expose?

io.github.theluckystrike/milestone-schedule 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,759 tokens of context every time the server is loaded.

### What licence is the io.github.theluckystrike/milestone-schedule MCP server under?

io.github.theluckystrike/milestone-schedule declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/delivery-schedule
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-milestone-schedule/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-delivery-s.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-milestone-schedule/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-delivery-s.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-milestone-schedule/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-delivery-s