io.github.theluckystrike/deliverable-tracker
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS · SCANNED SEP 20
Deliverables with a due date and a sign-off: what has slipped, and what is ready to bill.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 1856 tokens (~132/item across 14 items; 12 tools + 2 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 Management10
- Stability observed for 3 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
How do I install the io.github.theluckystrike/deliverable-tracker MCP server?
io.github.theluckystrike/deliverable-tracker is a hosted endpoint at https://mcp.zovo.one/mcp/delivery-schedule, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.zovo.one
claude mcp add --transport http theluckystrike-deliverable-tracker 'https://mcp.zovo.one/mcp/delivery-schedule'
{
"mcpServers": {
"theluckystrike-deliverable-tracker": {
"url": "https://mcp.zovo.one/mcp/delivery-schedule"
}
}
} {
"servers": {
"theluckystrike-deliverable-tracker": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/delivery-schedule"
}
}
} [mcp_servers.theluckystrike-deliverable-tracker] url = "https://mcp.zovo.one/mcp/delivery-schedule"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theluckystrike-deliverable-tracker": {
"type": "remote",
"url": "https://mcp.zovo.one/mcp/delivery-schedule",
"enabled": true
}
}
} openclaw mcp add theluckystrike-deliverable-tracker --url 'https://mcp.zovo.one/mcp/delivery-schedule' --transport streamable-http
mcp_servers:
theluckystrike-deliverable-tracker:
url: "https://mcp.zovo.one/mcp/delivery-schedule" {
"McpServers": {
"theluckystrike-deliverable-tracker": {
"Transport": "http",
"Url": "https://mcp.zovo.one/mcp/delivery-schedule"
}
}
} assistant mcp add theluckystrike-deliverable-tracker -t streamable-http -u 'https://mcp.zovo.one/mcp/delivery-schedule'
{
"mcpServers": {
"theluckystrike-deliverable-tracker": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/delivery-schedule"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Sept 26 77
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 20 Sept 2026 · Probed https://mcp.zovo.one/mcp/delivery-schedule
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ef74739bd6e575bb13db69661e215324 |
| SANs: zovo.one, mcp.zovo.one, *.mcp.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", error="invalid_token"
Bearer realm="mcp.zovo.one", error="invalid_token"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zovo.one/mcp/delivery-schedule | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/delivery-schedule | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/delivery-schedule |
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 ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from checkout, MCPL1.<payload>.<signature> |
No output schema declared.
No examples provided.
license_status License status ~55
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.
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/deliverable-tracker MCP server?
io.github.theluckystrike/deliverable-tracker is an MCP server listed in the public MCP registry as io.github.theluckystrike/deliverable-tracker. Deliverables with a due date and a sign-off: what has slipped, and what is ready to bill. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/delivery-schedule).
Is the io.github.theluckystrike/deliverable-tracker MCP server safe to use?
io.github.theluckystrike/deliverable-tracker scores 78 out of 100 on VerifyMCP. 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/deliverable-tracker MCP server expose?
io.github.theluckystrike/deliverable-tracker 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,765 tokens of context every time the server is loaded.
Does the io.github.theluckystrike/deliverable-tracker MCP server require authentication?
Yes. io.github.theluckystrike/deliverable-tracker asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.theluckystrike/deliverable-tracker MCP server still maintained?
io.github.theluckystrike/deliverable-tracker is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.