McpStamp Delivery Schedule
MCPB · DELIVERY-SCHEDULE.MCPB · 2 COMPONENTS
Dated deliverables for client work: status, late items with value at risk, sign-off documents.
Available components
Last scanned (4 hours ago)
Scores higher than 95% of MCPB servers
Category Project Management
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 Security23
- 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.Unverified
- Known CVEs were checked across the 153 of 153 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 57 of 153 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 48 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- 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 1798 tokens (~138/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
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.
- 2 Nov 26 +56
- Provenance: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Install scripts: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Tool coverage: unverified → 100 ▲ functional
- Dependency health: unverified → 0.81 ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- License: unverified → pass ▲ functional
- Licence: MIT functional
- Package version: 0.22.5 → 0.21.0 functional
- 28 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 27 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 26 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 24 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 23 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 16 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 14 Oct 26 −54
- Tool safety: pass → unverified ▼ security
- Stability: 0.87 → unverified ▼ security
- Stability: 0.87 → unverified ▼ security
- Known CVEs: partial → unverified ▼ security
- Provenance: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Dependency health: 0.81 → unverified ▼ functional
- License: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Maintenance: pass → unverified ▼ functional
- Licence: MIT functional
- Package version: 0.22.0 → 0.22.5 functional
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 5 Nov 2026 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.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 |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 153 packages
| Packages resolved | 153 |
|---|---|
| Deprecated | 2 |
| Stale | 57 |
| 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 ~263
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.
| 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 ~117
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.
| 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 ~203
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.
| 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 ~92
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.
| 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 ~118
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.
| 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 ~147
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.
| 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 ~169
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.
| 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 ~71
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.
| 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 ~54
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.
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.
How do I install the McpStamp Delivery Schedule MCP server?
McpStamp Delivery 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. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 0c7c73303757908f0648f5525ffba858b8c856d06852235d438e22032670fb60; the commands to do that are on this page. If it does not match, do not open it.
mcpb · delivery-schedule.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
0c7c73303757908f0648f5525ffba858b8c856d06852235d438e22032670fb60
macOS / Linux
echo "0c7c73303757908f0648f5525ffba858b8c856d06852235d438e22032670fb60 delivery-schedule.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\delivery-schedule.mcpb).Hash -eq "0c7c73303757908f0648f5525ffba858b8c856d06852235d438e22032670fb60"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the McpStamp Delivery Schedule MCP server?
McpStamp Delivery Schedule is an MCP server listed in the public MCP registry as io.github.theluckystrike/deliverable-tracker. Dated deliverables for client work: status, late items with value at risk, sign-off documents. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/delivery-schedule.mcpb).
Is the McpStamp Delivery Schedule MCP server safe to use?
McpStamp Delivery Schedule scores 61 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 McpStamp Delivery Schedule MCP server expose?
McpStamp 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,759 tokens of context every time the server is loaded.
What licence is the McpStamp Delivery Schedule MCP server under?
McpStamp 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.