mcpbeat Sign in

Delivery Schedule MCP Server

by theluckystrike Your server? Claim it
answering

Delivery Schedule is answering right now. Last checked 14 min ago. It exposes 12 tools. Last commit 22 Oct 2026.

Dated deliverables against a quote or work order: due dates, sign-off, what is late, milestones.

Uptime history 29 days of history
29 days agonow
100.0%
Uptime 24h
89 of 89 checks
12
Tools
read from the server
214 ms
Response time
average over 24h
2
Stars
last commit 22 Oct 2026

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 15 October 2026. No other catalogue keeps this.

15 Oct a tool changed version

Nothing serious here today

Today is the operative word: we check Delivery Schedule every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add delivery-schedule --transport http https://mcp.zovo.one/mcp/delivery-milestones
Settings → Connectors → Add custom connector, then paste this address
https://mcp.zovo.one/mcp/delivery-milestones
~/.codex/config.toml
[mcp_servers.delivery-schedule]
url = "https://mcp.zovo.one/mcp/delivery-milestones"
.cursor/mcp.json
{
  "mcpServers": {
    "delivery-schedule": {
      "url": "https://mcp.zovo.one/mcp/delivery-milestones"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "delivery-schedule": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/delivery-milestones"
    }
  }
}

Available tools 12

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

delivery
delivery_schedule_create
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.
delivery_schedule_delete
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.
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.
delivery_schedule_get
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.
delivery_schedule_list
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.
deliverable
deliverable_add
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.
deliverable_delete
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.
deliverable_status
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.
license
license_activate
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.
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.
late
late_report
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.
milestone
milestone_payload
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.

Endpoints

URLTransportStateLatencyChecked
https://mcp.zovo.one/mcp/delivery-milestones streamable-http answering 76 ms 14 min ago

Alternatives to Delivery Schedule

same job, measured the same way
Delivery Note
by theluckystrike

Delivery notes vs a quote or work order: dated deliverables, due dates, sign-off.

local only
Delivery Schedule Milestones Late Report
by bestremotetools

Dated deliverables against a quote or work order. late_report says what has slipped as at any date y

local only
Deliverable Tracker
by theluckystrike

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

12 tools local only
Milestone Schedule
by theluckystrike

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

12 tools local only
Change Order
by theluckystrike

Change orders against a quote or work order: deltas, approval, running contract value.

11 tools answering
X402 Receipt Verifier
by nexus-mcp-infra

Audits NEXUS's own x402 payment logs against its own delivery logs and issues a signed proof-of-deli

2 tools answering
Scope Change
by theluckystrike

Scope changes against a work order, each with a reason, a date and the client's approval on record.

11 tools local only
Vepathos
by vepathos

Import orders, manage your fleet, and generate optimized last-mile delivery routes at scale.

answering

Delivery Schedule — questions

Answers built from our own checks of this server.

What can Delivery Schedule do?
It exposes 12 tools, read directly from the server on our last check. Among them: deliverable_add, deliverable_delete, deliverable_status, delivery_schedule_create, delivery_schedule_delete, delivery_schedule_document and 6 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Delivery Schedule mostly used for?
Its tools cluster around delivery, deliverable and license. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Delivery Schedule working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 89 of 89 checks got a reply (100.0%), average response time 214 ms. The bar chart above shows every period we have measured.
How do I connect Delivery Schedule?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Delivery Schedule need an API key?
No. Delivery Schedule completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Delivery Schedule?
It answers our handshake in 214 ms on average, which is faster than 69% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Delivery Schedule open source?
The code is open source: it is published under the MIT licence, written in JavaScript and 2 stars on GitHub. The licence covers the code in the repository, not the hosted service at mcp.zovo.one, which runs on its operator's own terms.