# io.github.theluckystrike/work-order (remote · mcp.zovo.one)

Job orders for trades and field work: parts, labour, status, completion report, invoice payload.

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.zovo.one`: 83/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-work-order/mcp-work-order.md), [page](https://verifymcp.io/servers/theluckystrike-work-order/mcp-work-order)
- mcpb · `work-order.mcpb`: 47/100, [markdown](https://verifymcp.io/servers/theluckystrike-work-order/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-work-order.md), [page](https://verifymcp.io/servers/theluckystrike-work-order/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-work-order)

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/work-order`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.22.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 86/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 90% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http theluckystrike-work-order 'https://mcp.zovo.one/mcp/work-order'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-work-order": {
      "url": "https://mcp.zovo.one/mcp/work-order"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-work-order": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/work-order"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-work-order]
url = "https://mcp.zovo.one/mcp/work-order"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-work-order": {
      "type": "remote",
      "url": "https://mcp.zovo.one/mcp/work-order",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-work-order --url 'https://mcp.zovo.one/mcp/work-order' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-work-order:
    url: "https://mcp.zovo.one/mcp/work-order"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-work-order": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/work-order"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-work-order -t streamable-http -u 'https://mcp.zovo.one/mcp/work-order'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 83, +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.

### 2026-09-17 (score 82, +1)

- [functional] Server version: 0.21.0 → 0.22.0

### 2026-09-15 (score 81, +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.

### 2026-09-13 (score 80, +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.

### 2026-09-11 (score 79, +1)

- [security] Tool “license_activate” rewrote its description, which is the text the model reads
- [functional] New prompt “upgrade_to_pro”
- [functional] New resource “pricing”

### 2026-09-09 (score 78, +1)

- [security] 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
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “license_activate” reworded the description of “key”

### 2026-09-08 (score 77, +41)

- [security improvement] Transport: unverified → pass
- [security improvement] 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.
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] 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

### 2026-09-06 (score 36)

First indexed and scored.

## MCP tools (12)

### `work_order_create` (~267 tokens)

Raise a work order

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.

Input parameters:

- `client` (string, required): 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, required): 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, required): The date the work was asked for, YYYY-MM-DD
- `site_address` (string, required): Where the work happens. This is the site, not the billing address

### `work_order_add_line` (~283 tokens)

Add a parts or labour line

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.

Input parameters:

- `date` (string): The day this line was worked or fitted, YYYY-MM-DD
- `description` (string, required): 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, required): 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, required): The work order id, e.g. WO-2026-0001, or the client name when only one job is theirs

### `work_order_status` (~150 tokens)

Move a work order along

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.

Input parameters:

- `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, required): The status to move to. It must be the next one along
- `work_order` (string, required): The work order id, e.g. WO-2026-0001, or the client name when only one job is theirs

### `work_order_get` (~86 tokens)

Show one work order

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.

Input parameters:

- `work_order` (string, required): The work order id, e.g. WO-2026-0001, or the client name when only one job is theirs

### `work_order_list` (~130 tokens)

List work orders

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.

Input parameters:

- `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

### `work_order_delete` (~93 tokens)

Delete a draft work order

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.

Input parameters:

- `work_order` (string, required): The work order id, e.g. WO-2026-0001, or the client name when only one job is theirs

### `completion_report_text` (~102 tokens)

Completion report as plain text

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.

Input parameters:

- `work_order` (string, required): The work order id, e.g. WO-2026-0001, or the client name when only one job is theirs

### `completion_report_pdf` (~127 tokens)

Completion report as a PDF

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.

Input parameters:

- `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, required): The work order id, e.g. WO-2026-0001, or the client name when only one job is theirs

### `work_order_invoice_payload` (~125 tokens)

Invoice payload for a work order

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.

Input parameters:

- `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, required): The work order id, e.g. WO-2026-0001, or the client name when only one job is theirs

### `work_orders_report` (~87 tokens)

Report the board

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.

Input parameters:

- `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

### `license_status` (~55 tokens)

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.

### `license_activate` (~76 tokens)

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.

Input parameters:

- `key` (string, required): License key from checkout, MCPL1.<payload>.<signature>

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-work-order/mcp-work-order#diagnostics

## Score history

- 2026-09-20: 83
- 2026-09-19: 83
- 2026-09-18: 82
- 2026-09-17: 82
- 2026-09-16: 81
- 2026-09-15: 81
- 2026-09-14: 80
- 2026-09-13: 80
- 2026-09-12: 79
- 2026-09-11: 79
- 2026-09-10: 78
- 2026-09-09: 78
- 2026-09-08: 77
- 2026-09-07: 36
- 2026-09-06: 36

## Common questions

### 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.

## Links

- Remote endpoint: https://mcp.zovo.one/mcp/work-order
- Authorisation metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/work-order
- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/work-order
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-work-order/mcp-work-order.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-work-order/mcp-work-order.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-work-order/mcp-work-order