# io.github.theluckystrike/service-report (mcpb · work-order.mcpb)

Field service reports: hours, materials, sign-off, and the invoice the visit turns into.

- Trust score: 54/100 (low)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- mcpb · `work-order.mcpb`: 54/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-service-report/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-work-order.md), [page](https://verifymcp.io/servers/theluckystrike-service-report/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-work-order)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/work-order.mcpb`
- Version: `0.21.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-21.

- **Supply Chain Security**: 22/100
  - Malware scan not yet available for this package.
  - Known CVEs were checked across the 157 of 157 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - 63 of 157 dependencies flagged as unhealthy (2 deprecated).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 13 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 87/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 1471 tokens (~113/item across 13 items; 12 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 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

- Download bundle: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/work-order.mcpb`

## 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-20 (score 54, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 53, +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-16 (score 52, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 51, +3)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-07 (score 48)

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` (~274 tokens)

Add a parts or labour line

Add one line to a work order: parts with a quantity and a unit cost in minor units and an optional markup percent, or labour with hours and an hourly rate. Free.

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` (~146 tokens)

Move a work order along

Move a work order one step: draft to scheduled to in_progress to done to invoiced, stamping the date and a note. A skipped or backwards step is refused by name. 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` (~84 tokens)

Show one work order

Show one work order in full: the client and the site, every parts and labour line with its billed unit, the hours, the materials, the net and VAT, and the status history. 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` (~116 tokens)

List work orders

List work orders with their status, hours and value. Filter by status, by client, and by a 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` (~88 tokens)

Delete a draft work order

Delete a work order raised by mistake. Only a draft with no lines can go: once there is a line or a status past draft, the job has a history and is corrected, not erased. 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_text` (~85 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. 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` (~105 tokens)

Completion report as a PDF

Call this tool to write the A4 completion report of one work order and return the file path: the lines, the hours, the materials, the totals and the sign-off block. Pro.

Input parameters:

- `out_path` (string): Where to write the file. Defaults to the work-order data directory under pdf/
- `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` (~23 tokens)

License status

Show whether this server runs in free or Pro mode and where to upgrade.

### `license_activate` (~42 tokens)

Activate license

Activate a Pro license key (format MCPL1.xxx.yyy). Verified offline and saved locally.

Input parameters:

- `key` (string, required): License key from the checkout confirmation page

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/theluckystrike-service-report/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-work-order#diagnostics

## Score history

- 2026-09-21: 54
- 2026-09-20: 54
- 2026-09-19: 53
- 2026-09-18: 53
- 2026-09-17: 52
- 2026-09-16: 52
- 2026-09-15: 51
- 2026-09-14: 48
- 2026-09-13: 48
- 2026-09-12: 48
- 2026-09-11: 48
- 2026-09-10: 48
- 2026-09-09: 48
- 2026-09-08: 48
- 2026-09-07: 48

## Common questions

### What is the io.github.theluckystrike/service-report MCP server?

io.github.theluckystrike/service-report is an MCP server listed in the public MCP registry as io.github.theluckystrike/service-report. Field service reports: hours, materials, sign-off, and the invoice the visit turns into. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/work-order.mcpb).

### Is the io.github.theluckystrike/service-report MCP server safe to use?

io.github.theluckystrike/service-report scores 54 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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/service-report MCP server expose?

io.github.theluckystrike/service-report 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,442 tokens of context every time the server is loaded.

### What licence is the io.github.theluckystrike/service-report MCP server under?

io.github.theluckystrike/service-report declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/work-order
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-service-report/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-work-order.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-service-report/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-work-order.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-service-report/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-work-order