io.github.theluckystrike/work-order
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS · SCANNED SEP 20
Job orders for trades and field work: parts, labour, status, completion report, invoice payload.
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 Usability86
- 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 1661 tokens (~118/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 Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% 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 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "work_order_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/work-order MCP server?
io.github.theluckystrike/work-order is a hosted endpoint at https://mcp.zovo.one/mcp/work-order, 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-work-order 'https://mcp.zovo.one/mcp/work-order'
{
"mcpServers": {
"theluckystrike-work-order": {
"url": "https://mcp.zovo.one/mcp/work-order"
}
}
} {
"servers": {
"theluckystrike-work-order": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/work-order"
}
}
} [mcp_servers.theluckystrike-work-order] url = "https://mcp.zovo.one/mcp/work-order"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theluckystrike-work-order": {
"type": "remote",
"url": "https://mcp.zovo.one/mcp/work-order",
"enabled": true
}
}
} openclaw mcp add theluckystrike-work-order --url 'https://mcp.zovo.one/mcp/work-order' --transport streamable-http
mcp_servers:
theluckystrike-work-order:
url: "https://mcp.zovo.one/mcp/work-order" {
"McpServers": {
"theluckystrike-work-order": {
"Transport": "http",
"Url": "https://mcp.zovo.one/mcp/work-order"
}
}
} assistant mcp add theluckystrike-work-order -t streamable-http -u 'https://mcp.zovo.one/mcp/work-order'
{
"mcpServers": {
"theluckystrike-work-order": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/work-order"
}
}
} 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 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
- Server version: 0.21.0 → 0.22.0 functional
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
- Tool “license_activate” rewrote its description, which is the text the model reads security
- New prompt “upgrade_to_pro” functional
- New resource “pricing” functional
- 9 Sept 26 +1
- Tool “work_order_status” rewrote its description, which is the text the model reads security
- Tool “license_activate” rewrote its description, which is the text the model reads security
- Tool “license_status” rewrote its description, which is the text the model reads security
- Tool “work_order_add_line” rewrote its description, which is the text the model reads security
- Tool “work_order_delete” rewrote its description, which is the text the model reads security
- Tool “work_order_get” rewrote its description, which is the text the model reads security
- Tool “work_order_list” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- “license_activate” reworded the description of “key” cosmetic
- 8 Sept 26 +41
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: 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. security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- First check of Destructive annotations: 0 functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 90 functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- 6 Sept 26 36
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/work-order
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/work-order | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/work-order | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/work-order |
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 →
completion_report_pdf Completion report as a PDF ~127
Call this tool to render the A4 completion report of one work order and return a download link valid for one hour: the lines, the hours, the materials, the totals and the sign-off block. Pro.
| Name | Type | Req | Description |
|---|---|---|---|
| out_path | string | – | Name for the downloaded file, e.g. harbour-cafe-report. Defaults to the work order id; the report comes back as a download link valid for one hour |
| work_order | string | yes | The work order id, e.g. WO-2026-0001, or the client name when only one job is theirs |
No output schema declared.
No examples provided.
completion_report_text Completion report as plain text ~102
Turn a work order into a plain-text completion report: what was done, the labour hours, the materials, the totals and a sign-off block, ready to paste into an email. The same text also comes back as a .txt download link valid for one hour. Free on every tier.
| Name | Type | Req | Description |
|---|---|---|---|
| work_order | string | yes | The work order id, e.g. WO-2026-0001, or the client name when only one job is theirs |
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.
work_order_add_line Add a parts or labour line ~283
Add one line: parts with quantity, unit_cost_minor in whole MINOR units and optional markup, or labour with hours and rate_minor. A line on an invoiced order, or dated before the request, is refused.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | The day this line was worked or fitted, YYYY-MM-DD |
| description | string | yes | What it is, e.g. 3kW immersion element, or Second fix and test |
| hours | number | – | labour only: hours worked, e.g. 3.5 |
| kind | string | yes | parts for materials, labour for time on the job |
| markup_percent | number | – | parts only: percent added to the UNIT cost before billing. Default 0 |
| note | string | – | – |
| quantity | number | – | parts only: how many. A negative or zero quantity is refused |
| rate_minor | integer | – | labour only: the hourly rate in whole minor units. Omit only once the shared business profile carries a default rate |
| unit_cost_minor | integer | – | parts only: what one costs YOU, in whole minor units. 1299 is EUR 12.99 |
| work_order | string | yes | The work order id, e.g. WO-2026-0001, or the client name when only one job is theirs |
No output schema declared.
No examples provided.
work_order_create Raise a work order ~267
Raise a job order and return its WO-YYYY-NNNN number: the client, the site address, the date it was asked for, what the job is and how urgent. Free tier: 5 open orders.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | yes | A client name or id from the invoice server's client records. An unknown name needs client_address as well, so a typo is not filed as a new customer |
| client_address | string | – | The client's billing address, for a client that is not in the invoice records yet |
| client_email | string | – | – |
| client_vat_id | string | – | – |
| currency | string | – | ISO code the job is priced in. Defaults to the shared business profile's currency |
| description | string | yes | What the job is, e.g. Replace immersion heater and test |
| duplicate_ok | boolean | – | Raise it even though an identical work order exists, for a genuinely repeated visit. Default false |
| note | string | – | – |
| priority | string | – | How urgent the job is. Default normal |
| requested_date | string | yes | The date the work was asked for, YYYY-MM-DD |
| site_address | string | yes | Where the work happens. This is the site, not the billing address |
No output schema declared.
No examples provided.
work_order_delete Delete a draft work order ~93
Delete a DRAFT work order with no lines, freeing an open slot. One past draft is refused, naming the date it got there, and so is one carrying lines. The WO number is never reissued. work_order_status moves it on.
| Name | Type | Req | Description |
|---|---|---|---|
| work_order | string | yes | The work order id, e.g. WO-2026-0001, or the client name when only one job is theirs |
No output schema declared.
No examples provided.
work_order_get Show one work order ~86
Return one work order in full by WO number or client: the site, every parts and labour line with the unit billed, hours, materials, net and VAT, and the status history. Reads only. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| work_order | string | yes | The work order id, e.g. WO-2026-0001, or the client name when only one job is theirs |
No output schema declared.
No examples provided.
work_order_invoice_payload Invoice payload for a work order ~125
Build an invoice_create-ready payload from the lines, with VAT at the shared profile rate. Writes nothing and marks nothing: raise the invoice in the invoice server, then set this order invoiced. Pro.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_date | string | – | The invoice issue date, YYYY-MM-DD. Default today |
| tax_rate | number | – | VAT percent per line, overriding the shared business profile's default rate |
| work_order | string | yes | The work order id, e.g. WO-2026-0001, or the client name when only one job is theirs |
No output schema declared.
No examples provided.
work_order_list List work orders ~130
List work orders newest requested first: status, priority, client, site, hours, labour, materials and net value, with totals per currency. Filter by status, client and requested-date range. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | Only jobs whose client name contains this text |
| from | string | – | Earliest requested_date, YYYY-MM-DD |
| limit | integer | – | Maximum rows returned, default and ceiling 500 |
| status | string | – | One status, or open for draft, scheduled and in_progress together |
| to | string | – | Latest requested_date, YYYY-MM-DD |
No output schema declared.
No examples provided.
work_order_status Move a work order along ~150
Move one work order exactly one step: draft, scheduled, in_progress, done, invoiced, stamping date and note. A skipped, backwards or backdated step is refused and nothing is written. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | The day it reached this status, YYYY-MM-DD. Default today |
| note | string | – | What happened, e.g. Booked for Tuesday morning, or Signed off by the tenant |
| status | string | yes | The status to move to. It must be the next one along |
| work_order | string | yes | The work order id, e.g. WO-2026-0001, or the client name when only one job is theirs |
No output schema declared.
No examples provided.
work_orders_report Report the board ~87
Report the whole board: how many work orders sit at each status, the hours logged this month, and the value not yet invoiced per currency, with the oldest open jobs named. Pro.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum oldest-open rows listed, default and ceiling 500 |
| month | string | – | The month for the hours figure, YYYY-MM. Default the current month |
No output schema declared.
No examples provided.
What is the io.github.theluckystrike/work-order MCP server?
io.github.theluckystrike/work-order is an MCP server listed in the public MCP registry as io.github.theluckystrike/work-order. Job orders for trades and field work: parts, labour, status, completion report, invoice payload. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/work-order).
Is the io.github.theluckystrike/work-order MCP server safe to use?
io.github.theluckystrike/work-order scores 83 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/work-order MCP server expose?
io.github.theluckystrike/work-order exposes 12 tools: work_order_create, work_order_add_line, work_order_status, work_order_get, work_order_list, and 7 more. Their descriptions and schemas cost roughly 1,581 tokens of context every time the server is loaded.
Does the io.github.theluckystrike/work-order MCP server require authentication?
Yes. io.github.theluckystrike/work-order 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/work-order MCP server still maintained?
io.github.theluckystrike/work-order 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.