io.github.theluckystrikePublished by GitHub account theluckystrikev0.23.0Updated Nov 3, 2026
Dated deliverables for client work: status, late items with value at risk, sign-off documents.
McpStamp Delivery Schedule's hosted MCP server (mcp.zovo.one); no sign-in required; Streamable HTTP; 12 tools.
No AI overview yet: these facts come from the registry entry and the server itself.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.theluckystrike%2Fdeliverable-tracker/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"mcpstamp-delivery-schedule": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/delivery-schedule"
}
}
}In the official MCP Registry (io.github.theluckystrike/delivery-schedule).
Dated deliverables against a quote, a work order or a change order. Each one carries what
is being handed over, the day it is due, its value in minor units, and a status that moves
planned to in progress to delivered to accepted, every step with the day it actually
happened. late_report then answers the only question anybody asks about a schedule: what
has slipped, as at a date you name. Once the client has signed something off, the accepted
milestones come back as invoice_create-ready items in MAJOR units and quote_create-ready
items in MINOR units, in one call, with the scale printed against each.
Late is not a status here, it is a reading. A stored "late" flag is a fact about the afternoon somebody last ran the report, and it keeps being reported long after the work lands. So nothing derived is stored: a deliverable holds its due date, its value and its dated history, and the current status, the delivered date, the acceptance note, the lateness and every total are worked out on the call, against the date you passed.
One-click (.mcpb): download delivery-schedule.mcpb from the latest release and double-click it in Claude Desktop:
https://github.com/theluckystrike/mcp-servers/releases/latest
Hosted, no install: point a URL-based client at https://mcp.zovo.one/mcp/delivery-schedule. GET https://mcp.zovo.one/mcp/connect mints a token and prints a ready URL.
npm publish for @theluckystrike/mcp-delivery-schedule is pending, so the npx line below returns 404 today.
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or
%APPDATA%\Claude\claude_desktop_config.json (Windows):
~/.cursor/mcp.json (global) or .cursor/mcp.json (project), same entry as Claude Desktop.
The cap counts OPEN schedules, the jobs that still owe something, not the jobs you have
ever run. Accepting the last deliverable completes a schedule and frees its slot without
deleting the record, and delivery_schedule_delete clears an empty one; both are free on
every tier, because a way back that only a Pro key can reach is not a way back.
Get Pro: https://mcp.zovo.one/buy/delivery-schedule (one-time $19, lifetime), or all servers for $39: https://mcp.zovo.one/buy/bundle
planned to in_progress or straight to delivered; delivered to accepted. Accepted
is final, and nothing moves back: work the client sent back is a new deliverable with its
own due date, so the record keeps both the miss and the fix. Accepting something that was
never delivered is refused by name, because acceptance is the client's answer to a
handover and a deliverable accepted on a day nothing was handed over has no delivered date
to bill from. Every move carries the day it actually happened, and a move dated before the
reference document's own date, or before the previous move, is refused so the history reads
as a timeline.
A deliverable is late once as_of is PAST its due date and it has not been delivered by
then. One due on as_of itself is due_today, not late, which is the same rule the
statement server ages an invoice by. A deliverable that was delivered is delivered_late
or delivered_on_time by comparing its delivered date with its due date, which is a fact
that no longer moves. Every comparison is between two YYYY-MM-DD strings and every day
count is the difference of two UTC midnights, so the answer is the same on a laptop in
Warsaw and a server in Auckland.
Two readings of the same store, four days apart, differ on purpose:
A deliverable with no value_minor is not worth zero. It is one whose price was never
stated here, usually because the job is a lump sum, and adding it in as zero would
understate every total with nothing on the page to say so. It is counted apart wherever a
total is printed, and milestone_payload lists it under excluded.accepted_but_unpriced
rather than billing it. Nothing here invents a price.
This server keeps no arithmetic of its own. computeTotals, currencyDecimals,
formatMoney and daysBetween are imported from @theluckystrike/mcp-invoice/lib, the
corrupt-store quarantine from @theluckystrike/mcp-timezone/lib, the timezone-aware
"today" from @theluckystrike/mcp-quotes/lib. The VAT rate, the currency and the business
name come from the shared business profile that business_set in the invoice server writes.
Nothing is written outside this server's own directory, and no sibling store is opened.
The same deliverable is late, on time and not yet due depending only on the date you ask about, so storing the answer is storing the day somebody asked. D02 in the worked example is due 2026-04-20 and was delivered 2026-04-24. Read at 2026-04-22 it is late by two days with no delivered date at all, even though the store already holds one dated 04-24. Read at 2026-05-01 it is delivered late by four days. Read at 2026-04-19 it is not yet due. One store, three answers, all correct. The unit suite asserts all three from one unchanged sandbox, and a separate suite replays every call under four timezones fourteen hours apart and asserts the responses are byte-identical, so the day somebody reads the report on a laptop that travelled cannot move a client's deadline.
All data stays on your machine, in
${XDG_DATA_HOME:-~/.local/share}/mcp-servers/delivery-schedule/. Nothing is sent
anywhere. There is no account and no API key. License keys are verified offline. This
server reads one file it does not own, the shared business profile, and writes into no
store but its own.
Built by theluckystrike. https://github.com/theluckystrike
Any MCP client (Claude, Cursor, Windsurf, VS Code) can read this repository's documentation directly via GitMCP - no install:
Source: servers/delivery-schedule/README.md at commit 6535b33
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.
notetitlerequiredclientrequiredcurrencyreferencerequiredreference_daterequiredreference_kindAdd 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.
notedue_daterequiredschedulerequiredtax_ratedescriptionrequiredvalue_minorduplicate_okMove 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.
datenotestatusrequiredschedulerequireddeliverablerequiredDelete 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.
schedulerequireddeliverablerequiredShow 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.
as_ofschedulerequiredList 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.
as_oflimitstateclientreferenceDelete 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.
schedulerequiredWhat 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.
as_oflimitclientreferenceinclude_delivered_lateDelivery 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.
as_ofschedulerequiredInvoice 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.
as_ofschedulerequiredtax_rateissue_dateLicense 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.
Takes no parameters.
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.
keyrequired100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
{ "mcpServers": { "delivery-schedule": { "command": "npx", "args": ["-y", "@theluckystrike/mcp-delivery-schedule"] } }}claude mcp add delivery-schedule -- npx -y @theluckystrike/mcp-delivery-schedulelate_report as_of 2026-04-22 D02 is LATE by 2 days, nothing has been delivered latelate_report as_of 2026-05-05 D02 was DELIVERED LATE by 4 days, D03 is now LATE by 4 days