io.github.theluckystrike/change-order
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS · SCANNED SEP 21
Change orders against a quote or work order: deltas, approval, running contract value.
Available components
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. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 1606 tokens (~123/item across 13 items; 11 tools + 2 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 Management40
- Stability observed for 12 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- 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
How do I install the io.github.theluckystrike/change-order MCP server?
io.github.theluckystrike/change-order is a hosted endpoint at https://mcp.zovo.one/mcp/change-order, 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.
remote · mcp.zovo.one
claude mcp add --transport http theluckystrike-change-order 'https://mcp.zovo.one/mcp/change-order'
{
"mcpServers": {
"theluckystrike-change-order": {
"url": "https://mcp.zovo.one/mcp/change-order"
}
}
} {
"servers": {
"theluckystrike-change-order": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/change-order"
}
}
} [mcp_servers.theluckystrike-change-order] url = "https://mcp.zovo.one/mcp/change-order"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theluckystrike-change-order": {
"type": "remote",
"url": "https://mcp.zovo.one/mcp/change-order",
"enabled": true
}
}
} openclaw mcp add theluckystrike-change-order --url 'https://mcp.zovo.one/mcp/change-order' --transport streamable-http
mcp_servers:
theluckystrike-change-order:
url: "https://mcp.zovo.one/mcp/change-order" {
"McpServers": {
"theluckystrike-change-order": {
"Transport": "http",
"Url": "https://mcp.zovo.one/mcp/change-order"
}
}
} assistant mcp add theluckystrike-change-order -t streamable-http -u 'https://mcp.zovo.one/mcp/change-order'
{
"mcpServers": {
"theluckystrike-change-order": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/change-order"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 21 Sept 26 +2
- Tool “change_order_delete” is now declared destructive security
- Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
- Server version: 0.21.0 → 0.22.0 functional
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
- Tool “license_activate” rewrote its description, which is the text the model reads security
- New prompt “upgrade_to_pro” functional
- New resource “pricing” functional
- 10 Sept 26 0
- Tool “change_order_delete” rewrote its description, which is the text the model reads security
- Tool “change_order_get” rewrote its description, which is the text the model reads security
- Tool “change_order_list” rewrote its description, which is the text the model reads security
- Tool “change_order_status” rewrote its description, which is the text the model reads security
- Tool “contract_value” rewrote its description, which is the text the model reads security
- Tool “license_activate” rewrote its description, which is the text the model reads security
- Tool “license_status” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- “license_activate” reworded the description of “key” cosmetic
- 9 Sept 26 +41
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 95 functional
- First check of Destructive annotations: 0 functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
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 21 Sept 2026 · Probed https://mcp.zovo.one/mcp/change-order
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ef74739bd6e575bb13db69661e215324 |
| SANs: zovo.one, mcp.zovo.one, *.mcp.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", error="invalid_token"
Bearer realm="mcp.zovo.one", error="invalid_token"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zovo.one/mcp/change-order | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/change-order | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/change-order |
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 ~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.
| 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 ~99
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.
| 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 ~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.
| 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 ~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.
| 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 ~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.
| 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 ~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.
| 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 ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from checkout, MCPL1.<payload>.<signature> |
No output schema declared.
No examples provided.
license_status License status ~55
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.theluckystrike/change-order MCP server?
io.github.theluckystrike/change-order is an MCP server listed in the public MCP registry as io.github.theluckystrike/change-order. Change orders against a quote or work order: deltas, approval, running contract value. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/change-order).
Is the io.github.theluckystrike/change-order MCP server safe to use?
io.github.theluckystrike/change-order 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/change-order MCP server expose?
io.github.theluckystrike/change-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,519 tokens of context every time the server is loaded.
Does the io.github.theluckystrike/change-order MCP server require authentication?
Yes. io.github.theluckystrike/change-order 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/change-order MCP server still maintained?
io.github.theluckystrike/change-order is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.