# io.github.theluckystrike/variation-order (mcpb · change-order.mcpb)

Variation orders on a quoted job: what was added, removed or changed, and what it is now worth.

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

## Components

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

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/change-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-20.

- **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**: 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 1450 tokens (~120/item across 12 items; 11 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 95% 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; "change_order_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 12 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/change-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-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-14 (score 51, +4)

- [functional improvement] Stability: unverified → 0.23

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

First indexed and scored.

## MCP tools (11)

### `change_order_create` (~295 tokens)

Raise a change order

Raise a change order against a quote or work order and return its CO-YYYY-NNNN number: the reference, the client, a title, the date, and the original contract value in minor units. Free tier: 5 open.

Input parameters:

- `client` (string, required): The client the change is agreed with, as named on the quote or work order
- `currency` (string): ISO code the contract is priced in. Defaults to the shared business profile's currency
- `date` (string): The day the change was raised, YYYY-MM-DD. Default today
- `duplicate_ok` (boolean): Raise it even though an identical change order exists on this reference. Default false
- `note` (string)
- `original_value_minor` (integer): The contract value BEFORE any change order, net of VAT, in whole minor units. Required on the first change order against a reference; inherited by every later one
- `reference` (string, required): The quote or work order this change order is against, by its id, e.g. Q-2026-0003 or WO-2026-0001
- `reference_kind` (string): What the reference is. Inferred from the id when omitted: WO-... is a work order, anything else a quote
- `title` (string, required): What the change is, in one line, e.g. Add a second landing page and drop hosting

### `change_order_add_line` (~316 tokens)

Add a changed line

Add one line to a draft change order: added or removed with a quantity and a unit price in minor units, or changed with the old and the new quantity and price, each with a reason and a date. Free.

Input parameters:

- `change_order` (string, required): The change order id, e.g. CO-2026-0001, or its title when only one carries it
- `date` (string): The day the change was asked for, YYYY-MM-DD. Default the change order's date
- `description` (string, required): The line as it reads on the quote or work order, e.g. Website audit
- `kind` (string, required): added for new work, removed for work taken out, changed for a line whose quantity or price moves
- `note` (string)
- `quantity` (number, required): added or removed: how many. changed: the NEW quantity
- `reason` (string, required): Why, in the client's words if you have them, e.g. Client asked for a second page after the kickoff
- `tax_rate` (number): VAT percent for this line, overriding the shared profile's default
- `unit_price_minor` (integer, required): added or removed: the unit price in whole minor units. changed: the NEW unit price. 45000 is EUR 450.00
- `was_quantity` (number): changed only: the quantity before the change
- `was_unit_price_minor` (integer): changed only: the unit price before the change, in whole minor units

### `change_order_status` (~146 tokens)

Move a change order along

Move a change order: draft to sent, sent to approved or rejected, draft or sent to void, stamping the date and a note. Approved, rejected and void are final, and a draft cannot be approved unsent. Free.

Input parameters:

- `change_order` (string, required): The change order id, e.g. CO-2026-0001, or its title when only one carries it
- `date` (string): The day it happened, YYYY-MM-DD. Default today
- `note` (string): What happened, e.g. Emailed to the client, or Approved by phone, confirmed in writing
- `status` (string, required): The status to move to

### `change_order_get` (~81 tokens)

Show one change order

Show one change order in full: every added, removed and changed line with its reason and delta, the VAT, the delta gross, the status history and the running value of the reference. Free.

Input parameters:

- `change_order` (string, required): The change order id, e.g. CO-2026-0001, or its title when only one carries it

### `change_order_list` (~128 tokens)

List change orders

List change orders with their status and delta. Filter by reference, by status, by client, and by a date range. Free.

Input parameters:

- `client` (string): Only change orders whose client name contains this text
- `from` (string): Earliest date, YYYY-MM-DD
- `limit` (integer): Maximum rows returned, default and ceiling 500
- `reference` (string): Only change orders against this quote or work order
- `status` (string): One status, or open for draft and sent together
- `to` (string): Latest date, YYYY-MM-DD

### `change_order_delete` (~86 tokens)

Delete an empty draft

Delete a change order raised by mistake. Only a draft with no lines can go: once there is a line or it has been sent, it has a history and is voided, not erased. Free on every tier.

Input parameters:

- `change_order` (string, required): The change order id, e.g. CO-2026-0001, or its title when only one carries it

### `contract_value` (~89 tokens)

Running contract value

The running value of one quote or work order: the original, the approved deltas and the current value, with pending draft and sent deltas shown separately and never added in. Free on every tier.

Input parameters:

- `reference` (string, required): The quote or work order this change order is against, by its id, e.g. Q-2026-0003 or WO-2026-0001

### `change_order_document` (~82 tokens)

Change order document

Render one change order as a plain-text document for the client to approve: every line with its reason, the delta net and gross, the contract value before and after, and an approval block. Pro.

Input parameters:

- `change_order` (string, required): The change order id, e.g. CO-2026-0001, or its title when only one carries it

### `change_order_invoice_payload` (~126 tokens)

Invoice payload for an approved delta

Build the approved delta 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 and creates nothing. Pro.

Input parameters:

- `change_order` (string, required): The change order id, e.g. CO-2026-0001, or its title when only one carries it
- `issue_date` (string): The invoice issue date, YYYY-MM-DD. Default today
- `tax_rate` (number): VAT percent for lines with no rate of their own, overriding the shared business profile's default

### `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-variation-order/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-change-ord#diagnostics

## Score history

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

## Common questions

### What is the io.github.theluckystrike/variation-order MCP server?

io.github.theluckystrike/variation-order is an MCP server listed in the public MCP registry as io.github.theluckystrike/variation-order. Variation orders on a quoted job: what was added, removed or changed, and what it is now worth. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/change-order.mcpb).

### Is the io.github.theluckystrike/variation-order MCP server safe to use?

io.github.theluckystrike/variation-order scores 53 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/variation-order MCP server expose?

io.github.theluckystrike/variation-order exposes 11 tools: change_order_create, change_order_add_line, change_order_status, change_order_get, change_order_list, and 6 more. Their descriptions and schemas cost roughly 1,414 tokens of context every time the server is loaded.

### What licence is the io.github.theluckystrike/variation-order MCP server under?

io.github.theluckystrike/variation-order 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/change-order
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-variation-order/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-change-ord.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-variation-order/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-change-ord.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-variation-order/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-change-ord