Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.theluckystrike/scope-change

MCPB · CHANGE-ORDER.MCPB · 2 COMPONENTS · SCANNED SEP 30

Scope changes against a work order, each with a reason, a date and the client's approval on record.

+3 this week 50 Trust /100
Trust breakdown (7 categories)

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
Schema Quality & AI Usability84
  • 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 1532 tokens (~127/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 Management23
  • Stability observed for 7 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
Install

How do I install the io.github.theluckystrike/scope-change MCP server?

io.github.theluckystrike/scope-change 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 · change-order.mcpb

Download bundle

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

Changelog

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.

  • 30 Sept 26 +3
    • Stability: unverified → 0.23 ▲ functional
  • 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.

Diagnostics

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/change-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 →

MCP tools · 11 exposed · ~1,496 tokens

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 →

Tool Tokens
change_order_add_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.

NameTypeReqDescription
change_orderstringyesThe change order id, e.g. CO-2026-0001, or its title when only one carries it
datestring–The day the change was asked for, YYYY-MM-DD. Default the change order's date
descriptionstringyesThe line as it reads on the quote or work order, e.g. Website audit
kindstringyesadded for new work, removed for work taken out, changed for a line whose quantity or price moves
notestring––
quantitynumberyesadded or removed: how many. changed: the NEW quantity
reasonstringyesWhy, in the client's words if you have them, e.g. Client asked for a second page after the kickoff
tax_ratenumber–VAT percent for this line, overriding the shared profile's default
unit_price_minorintegeryesadded or removed: the unit price in whole minor units. changed: the NEW unit price. 45000 is EUR 450.00
was_quantitynumber–changed only: the quantity before the change
was_unit_price_minorinteger–changed only: the unit price before the change, in whole minor units

No output schema declared.

No examples provided.

change_order_create ~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.

NameTypeReqDescription
clientstringyesThe client the change is agreed with, as named on the quote or work order
currencystring–ISO code the contract is priced in. Defaults to the shared business profile's currency
datestring–The day the change was raised, YYYY-MM-DD. Default today
duplicate_okboolean–Raise it even though an identical change order exists on this reference. Default false
notestring––
original_value_minorinteger–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
referencestringyesThe quote or work order this change order is against, by its id, e.g. Q-2026-0003 or WO-2026-0001
reference_kindstring–What the reference is. Inferred from the id when omitted: WO-... is a work order, anything else a quote
titlestringyesWhat 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 ~90

Delete a DRAFT change order with no lines, freeing an open slot. One sent, approved, rejected or voided is refused, and so is one carrying lines: void it with change_order_status instead. The number is not reissued.

NameTypeReqDescription
change_orderstringyesThe 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 ~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.

NameTypeReqDescription
change_orderstringyesThe 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 ~86

Return one change order in full by CO number or client: every added, removed and changed line with its reason and delta, VAT, delta gross, the status history and the running value. change_order_list finds the id.

NameTypeReqDescription
change_orderstringyesThe 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 ~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.

NameTypeReqDescription
change_orderstringyesThe change order id, e.g. CO-2026-0001, or its title when only one carries it
issue_datestring–The invoice issue date, YYYY-MM-DD. Default today
tax_ratenumber–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 ~144

List change orders newest first with status, reference, client, currency and net delta, and above them the APPROVED and the pending delta per currency, kept apart. Filter by reference, status, client, date.

NameTypeReqDescription
clientstring–Only change orders whose client name contains this text
fromstring–Earliest date, YYYY-MM-DD
limitinteger–Maximum rows returned, default and ceiling 500
referencestring–Only change orders against this quote or work order
statusstring–One status, or open for draft and sent together
tostring–Latest date, YYYY-MM-DD

No output schema declared.

No examples provided.

change_order_status ~142

Move one change order along and stamp the date and note: draft to sent, sent to approved or rejected, either to void. Backwards steps, an unsent approval and a backdated move are all refused.

NameTypeReqDescription
change_orderstringyesThe change order id, e.g. CO-2026-0001, or its title when only one carries it
datestring–The day it happened, YYYY-MM-DD. Default today
notestring–What happened, e.g. Emailed to the client, or Approved by phone, confirmed in writing
statusstringyesThe status to move to

No output schema declared.

No examples provided.

contract_value ~90

The running value of one quote or work order: original, approved deltas and current value, with pending draft and sent deltas kept apart. Net of VAT. A reference with no change order is refused.

NameTypeReqDescription
referencestringyesThe 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 ~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.

NameTypeReqDescription
keystringyesLicense key from the checkout confirmation page

No output schema declared.

No examples provided.

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.

Common questions

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.22.0/change-order.mcpb).

Is the io.github.theluckystrike/scope-change MCP server safe to use?

io.github.theluckystrike/scope-change scores 50 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,496 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.