io.github.theluckystrike/service-report
MCPB · WORK-ORDER.MCPB · 2 COMPONENTS · SCANNED SEP 30
Field service reports: hours, materials, sign-off, and the invoice the visit turns into.
Available components
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. How we score → Why this is hard to score →
Supply Chain Security22
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs were checked across the 153 of 153 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 63 of 153 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 12 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 1565 tokens (~120/item across 13 items; 12 tools + 1 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the io.github.theluckystrike/service-report MCP server?
io.github.theluckystrike/service-report ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check the download against.
mcpb · work-order.mcpb
Download bundleThe MCP registry declares no SHA-256 for this bundle, so there is no published digest to check it against. Open it with an MCPB-capable host such as Claude Desktop.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 47
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 30 Sept 2026 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/work-order.mcpb@0.22.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 153 packages
| Packages resolved | 153 |
|---|---|
| Deprecated | 2 |
| Stale | 63 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| out_path | string | – | Where to write the file. Defaults to the work-order data directory under pdf/ |
| 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 ~85
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.
| 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 ~71
Activate a Pro key (MCPL1.xxx.yyy) from checkout: verified offline against a built-in public key, saved to your config file. A wrong, malformed or expired key is refused, unsaved. license_status reads it back.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from the checkout confirmation page |
No output schema declared.
No examples provided.
license_status License status ~54
Report this server's licence state: product, tier free or pro, licence id, expiry, the key source and the upgrade URL. No arguments, no network. Explains a free-tier refusal; license_activate installs a key.
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/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.22.0/work-order.mcpb).
Is the io.github.theluckystrike/service-report MCP server safe to use?
io.github.theluckystrike/service-report scores 47 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,536 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.