io.github.theluckystrike/scope-change
MCPB · CHANGE-ORDER.MCPB · SCANNED SEP 20
Scope changes against a work order, each with a reason, a date and the client's approval on record.
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
- Malware scan not yet available for this package.Unverified
- Known CVEs were checked across the 157 of 157 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 157 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 13 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 1450 tokens (~120/item across 12 items; 11 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 Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% 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; "change_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 12 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
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
mcpb · change-order.mcpb
Download bundleEvery 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.
- 18 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.
- 16 Sept 26 +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.
- 14 Sept 26 +4
- Stability: unverified → 0.23 ▲ functional
- 7 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 20 Sept 2026 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/change-order.mcpb@0.21.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
Background: How many MCP packages publish verified provenance →
Dependencies 157 packages
| Packages resolved | 157 |
|---|---|
| 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 →
change_order_add_line Add a changed line ~316
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.
| Name | Type | Req | Description |
|---|---|---|---|
| change_order | string | yes | 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 | yes | The line as it reads on the quote or work order, e.g. Website audit |
| kind | string | yes | added for new work, removed for work taken out, changed for a line whose quantity or price moves |
| note | string | – | – |
| quantity | number | yes | added or removed: how many. changed: the NEW quantity |
| reason | string | yes | 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 | yes | 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 |
No output schema declared.
No examples provided.
change_order_create Raise a change order ~295
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | yes | 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 | yes | 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 | yes | What the change is, in one line, e.g. Add a second landing page and drop hosting |
No output schema declared.
No examples provided.
change_order_delete Delete an empty draft ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| change_order | string | yes | The change order id, e.g. CO-2026-0001, or its title when only one carries it |
No output schema declared.
No examples provided.
change_order_document Change order document ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| change_order | string | yes | The change order id, e.g. CO-2026-0001, or its title when only one carries it |
No output schema declared.
No examples provided.
change_order_get Show one change order ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| change_order | string | yes | The change order id, e.g. CO-2026-0001, or its title when only one carries it |
No output schema declared.
No examples provided.
change_order_invoice_payload Invoice payload for an approved delta ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| change_order | string | yes | 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 |
No output schema declared.
No examples provided.
change_order_list List change orders ~128
List change orders with their status and delta. Filter by reference, by status, by client, and by a date range. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
change_order_status Move a change order along ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| change_order | string | yes | 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 | yes | The status to move to |
No output schema declared.
No examples provided.
contract_value Running contract value ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| reference | string | yes | The quote or work order this change order is against, by its id, e.g. Q-2026-0003 or WO-2026-0001 |
No output schema declared.
No examples provided.
license_activate Activate license ~42
Activate a Pro license key (format MCPL1.xxx.yyy). Verified offline and saved locally.
| 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 ~23
Show whether this server runs in free or Pro mode and where to upgrade.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.theluckystrike/scope-change MCP server?
io.github.theluckystrike/scope-change is an MCP server listed in the public MCP registry as io.github.theluckystrike/scope-change. Scope changes against a work order, each with a reason, a date and the client's approval on record. 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/scope-change MCP server safe to use?
io.github.theluckystrike/scope-change 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/scope-change MCP server expose?
io.github.theluckystrike/scope-change 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/scope-change MCP server under?
io.github.theluckystrike/scope-change declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.