io.github.theluckystrike/delivery-schedule
MCPB · DELIVERY-SCHEDULE.MCPB · SCANNED SEP 21
Dated deliverables against a quote or work order: due dates, sign-off, what is late, milestones.
Available components
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. How we score → Why this is hard to score →
Supply Chain Security22
- Malware scan not yet available for this package.Unverified
- Known CVEs were checked across the 157 of 157 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 63 of 157 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 14 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1716 tokens (~132/item across 13 items; 12 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 Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 13 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
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
mcpb · delivery-schedule.mcpb
Download bundleEvery 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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
- 7 Sept 26 47
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 21 Sept 2026 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/delivery-schedule.mcpb@0.21.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
Background: How many MCP packages publish verified provenance →
Dependencies 157 packages
| Packages resolved | 157 |
|---|---|
| Deprecated | 2 |
| Stale | 63 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
deliverable_add Add a dated deliverable ~259
Add one deliverable to a schedule: what it is, the day it is due, and its value in whole minor units when it is separately priced. It starts as planned. Free on every tier.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | What is being handed over, as the client would recognise it, e.g. Wireframes for the five main pages |
| due_date | string | yes | 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 | yes | 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 |
No output schema declared.
No examples provided.
deliverable_delete Delete a planned deliverable ~115
Delete a deliverable added by mistake. Only one still planned with nothing recorded against it can go: once it has been started or handed over it has a history. Free on every tier.
| Name | Type | Req | Description |
|---|---|---|---|
| deliverable | string | yes | The deliverable id, e.g. D01, or its description when only one carries it |
| schedule | string | yes | The schedule id, e.g. DS-2026-0001, the reference it delivers, e.g. WO-2026-0001, or its title |
No output schema declared.
No examples provided.
deliverable_status Move a deliverable along ~194
Record a dated move on one deliverable: planned to in progress, to delivered, and delivered to accepted with the acceptance note. Accepting something never delivered is refused. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | The schedule id, e.g. DS-2026-0001, the reference it delivers, e.g. WO-2026-0001, or its title |
| status | string | yes | The status to move to |
No output schema declared.
No examples provided.
delivery_schedule_create Open a delivery schedule ~249
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | yes | 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 | yes | 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 | yes | 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 | yes | What the job is, in one line, e.g. Website rebuild, phase one |
No output schema declared.
No examples provided.
delivery_schedule_delete Delete an empty schedule ~86
Delete a delivery schedule opened by mistake. Only one with no deliverables can go: once it carries one, it carries a record of what was owed. Free on every tier.
| Name | Type | Req | Description |
|---|---|---|---|
| schedule | string | yes | The schedule id, e.g. DS-2026-0001, the reference it delivers, e.g. WO-2026-0001, or its title |
No output schema declared.
No examples provided.
delivery_schedule_document Delivery schedule document ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Read the schedule as at this date, YYYY-MM-DD. Defaults to today |
| schedule | string | yes | The schedule id, e.g. DS-2026-0001, the reference it delivers, e.g. WO-2026-0001, or its title |
No output schema declared.
No examples provided.
delivery_schedule_get Show one delivery schedule ~114
Show one schedule in full as at a date: every deliverable with its due date, status, delivered and accepted dates, acceptance note and value, plus what is late as at that date. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Read the schedule as at this date, YYYY-MM-DD. Defaults to today |
| schedule | string | yes | The schedule id, e.g. DS-2026-0001, the reference it delivers, e.g. WO-2026-0001, or its title |
No output schema declared.
No examples provided.
delivery_schedule_list List delivery schedules ~152
List delivery schedules with their counts as at a date: what is late, what is still owed and what has been accepted. Filter by client, by reference and by whether the job is complete. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
late_report What is late as at a date ~167
What has slipped as at a date you name: every deliverable still owed whose due date has passed, worst first, with the value at risk per currency and what was delivered late for the record. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
license_activate Activate license ~42
Activate a Pro license key (format MCPL1.xxx.yyy). Verified offline and saved locally.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from the checkout confirmation page |
No output schema declared.
No examples provided.
license_status License status ~23
Show whether this server runs in free or Pro mode and where to upgrade.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
milestone_payload Invoice payload for accepted milestones ~159
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 |
No output schema declared.
No examples provided.
What is the io.github.theluckystrike/delivery-schedule MCP server?
io.github.theluckystrike/delivery-schedule is an MCP server listed in the public MCP registry as io.github.theluckystrike/delivery-schedule. Dated deliverables against a quote or work order: due dates, sign-off, what is late, milestones. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/delivery-schedule.mcpb).
Is the io.github.theluckystrike/delivery-schedule MCP server safe to use?
io.github.theluckystrike/delivery-schedule scores 54 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/delivery-schedule MCP server expose?
io.github.theluckystrike/delivery-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,677 tokens of context every time the server is loaded.
What licence is the io.github.theluckystrike/delivery-schedule MCP server under?
io.github.theluckystrike/delivery-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.