# io.github.theluckystrike/scope-change (remote · mcp.zovo.one)

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

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-30

## Components

- remote · `mcp.zovo.one`: 84/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-scope-change/mcp-scope-change.md), [page](https://verifymcp.io/servers/theluckystrike-scope-change/mcp-scope-change)
- mcpb · `change-order.mcpb`: 50/100, [markdown](https://verifymcp.io/servers/theluckystrike-scope-change/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-change-ord.md), [page](https://verifymcp.io/servers/theluckystrike-scope-change/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-change-ord)

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/scope-change`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.22.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-30.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 84/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 1606 tokens (~123/item across 13 items; 11 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - 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

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

io.github.theluckystrike/scope-change is a hosted endpoint at https://mcp.zovo.one/mcp/scope-change, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http theluckystrike-scope-change 'https://mcp.zovo.one/mcp/scope-change'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-scope-change": {
      "url": "https://mcp.zovo.one/mcp/scope-change"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-scope-change": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/scope-change"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-scope-change]
url = "https://mcp.zovo.one/mcp/scope-change"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-scope-change": {
      "type": "remote",
      "url": "https://mcp.zovo.one/mcp/scope-change",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-scope-change --url 'https://mcp.zovo.one/mcp/scope-change' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-scope-change:
    url: "https://mcp.zovo.one/mcp/scope-change"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-scope-change": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/scope-change"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-scope-change -t streamable-http -u 'https://mcp.zovo.one/mcp/scope-change'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-scope-change": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/scope-change"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-30 (score 84, +1)

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

### 2026-09-28 (score 83, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 82, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 81, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-23 (score 81)

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

Move a change order along

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.

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

Show one change order

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.

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

List change orders

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.

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

Delete an empty draft

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.

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

Running contract value

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.

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` (~99 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. The same text also comes back as a .txt download link valid for one hour. 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` (~55 tokens)

License status

Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.

### `license_activate` (~76 tokens)

Activate license

Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.

Input parameters:

- `key` (string, required): License key from checkout, MCPL1.<payload>.<signature>

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-scope-change/mcp-scope-change#diagnostics

## Score history

- 2026-09-30: 84
- 2026-09-29: 83
- 2026-09-28: 83
- 2026-09-27: 82
- 2026-09-26: 82
- 2026-09-25: 82
- 2026-09-24: 81
- 2026-09-23: 81

## 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 hosted endpoint (https://mcp.zovo.one/mcp/scope-change).

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

io.github.theluckystrike/scope-change scores 84 out of 100 on VerifyMCP. 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,519 tokens of context every time the server is loaded.

### Does the io.github.theluckystrike/scope-change MCP server require authentication?

Yes. io.github.theluckystrike/scope-change asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the io.github.theluckystrike/scope-change MCP server still maintained?

io.github.theluckystrike/scope-change is still listed as active in the MCP registry. We last reached this channel on 30 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.zovo.one/mcp/scope-change
- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/change-order
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-scope-change/mcp-scope-change.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-scope-change/mcp-scope-change.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-scope-change/mcp-scope-change