# io.github.theluckystrike/bill-of-sale (remote · mcp.zovo.one)

Bills of sale for equipment, vehicles and stock: draft, finalize, print with signature lines.

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

## Components

- remote · `mcp.zovo.one`: 82/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-bill-of-sale/mcp-bill-of-sale.md), [page](https://verifymcp.io/servers/theluckystrike-bill-of-sale/mcp-bill-of-sale)
- mcpb · `bill-of-sale.mcpb`: 45/100, [markdown](https://verifymcp.io/servers/theluckystrike-bill-of-sale/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-bill-of-sa.md), [page](https://verifymcp.io/servers/theluckystrike-bill-of-sale/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-bill-of-sa)

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/bill-of-sale`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.22.0`

## 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-21.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - 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.
- **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 1675 tokens (~152/item across 11 items; 10 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 89/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 68% 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 11 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/bill-of-sale MCP server?

io.github.theluckystrike/bill-of-sale is a hosted endpoint at https://mcp.zovo.one/mcp/bill-of-sale, 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-bill-of-sale 'https://mcp.zovo.one/mcp/bill-of-sale'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-bill-of-sale": {
      "url": "https://mcp.zovo.one/mcp/bill-of-sale"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-bill-of-sale": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/bill-of-sale"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-bill-of-sale]
url = "https://mcp.zovo.one/mcp/bill-of-sale"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add theluckystrike-bill-of-sale --url 'https://mcp.zovo.one/mcp/bill-of-sale' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-bill-of-sale:
    url: "https://mcp.zovo.one/mcp/bill-of-sale"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-bill-of-sale": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/bill-of-sale"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-bill-of-sale -t streamable-http -u 'https://mcp.zovo.one/mcp/bill-of-sale'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-bill-of-sale": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/bill-of-sale"
    }
  }
}
```

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-21 (score 82, +2)

- [security] Tool “sale_delete” is now declared destructive
- [functional] Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.

### 2026-09-19 (score 80, +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-18 (score 79, +54)

- [security regression] Authorization: unverified → fail
- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [functional improvement] Endpoint reachability: behind authorisation → reachable
- [functional improvement] Stability: unverified → 0.20
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] Tool coverage: unverified → 100
- [functional] Server version: 0.21.0 → 0.22.0

### 2026-09-17 (score 25, −53)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Stability: 0.13 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → unverified
- [security regression] Authorization: fail → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Schema quality: 100 → unverified

### 2026-09-15 (score 78, +1)

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

### 2026-09-13 (score 77, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-12 (score 76)

First indexed and scored.

## MCP tools (10)

### `sale_create` (~606 tokens)

Record a sale

Record a sale and generate the bill of sale: who sold, who bought, what item (with VIN, serial or IMEI where it has one), the price in minor units and the date. Returns the BOS-YYYY-NNNN number of the draft. The draft can still be changed with sale_update; sale_finalize freezes it into the signing copy and sale_render prints it. Free tier: 10 drafts.

Input parameters:

- `as_is` (boolean): Include the as-is clause: sold with all faults, no warranties except any written here. Default true, the norm for second-hand sales; pass false to leave it out
- `buyer_address` (string): The buyer's postal address, one string
- `buyer_email` (string): The buyer's email
- `buyer_name` (string, required): Who is buying, e.g. Jane Kowalska or Northwind Sp. z o.o.
- `buyer_phone` (string): The buyer's phone number
- `condition` (string): The condition at handover, e.g. used, good working order, or new, sealed
- `currency` (string, required): ISO code the price is in
- `date` (string): The date of the sale, YYYY-MM-DD. Default today
- `duplicate_ok` (boolean): Record it even though an identical sale to the same buyer exists, for a genuinely repeated sale. Default false
- `identifier_other` (string): Any other identifying number, e.g. a hull number or an asset tag
- `imei` (string): IMEI, 15 digits, for a phone or tablet
- `item_category` (string): What kind of item, e.g. vehicle, equipment, electronics, stock
- `item_description` (string, required): What was sold, specific enough to identify it, e.g. 2019 Honda Civic 1.5 petrol, grey, or MacBook Pro 14-inch 2021
- `notes` (string): Anything else the document should say, e.g. payment method or what is included in the sale
- `price_minor` (integer, required): The sale price in whole minor units (integer cents). 120000 is USD 1,200.00
- `quantity` (integer): How many units this document covers. Default 1
- `seller_address` (string): The seller's postal address, one string
- `seller_email` (string): The seller's email
- `seller_name` (string): Who is selling. Defaults to the shared business profile's name when the profile has one
- `seller_phone` (string): The seller's phone number
- `serial` (string): Serial number, for equipment and electronics
- `vin` (string): Vehicle Identification Number, 17 characters, for a vehicle sale
- `warranty` (string): A warranty the seller does give, in their own words, e.g. The seller warrants the engine for 30 days from the sale date

### `sale_update` (~274 tokens)

Change a bill of sale before signing

Change anything on a bill of sale that is not finalized yet: price, buyer, seller, item details, identifiers, the as-is clause, warranty or notes. Pass an empty string to clear an optional field. A finalized document cannot be edited.

Input parameters:

- `as_is` (boolean)
- `buyer_address` (string)
- `buyer_email` (string)
- `buyer_name` (string): Who is buying
- `buyer_phone` (string)
- `condition` (string)
- `currency` (string)
- `date` (string): The date of the sale, YYYY-MM-DD
- `identifier_other` (string)
- `imei` (string)
- `item_category` (string)
- `item_description` (string)
- `notes` (string)
- `price_minor` (integer): The sale price in whole minor units (integer cents)
- `quantity` (integer)
- `sale` (string, required): The bill of sale id, e.g. BOS-2026-0001
- `seller_address` (string)
- `seller_email` (string)
- `seller_name` (string): Who is selling
- `seller_phone` (string)
- `serial` (string)
- `vin` (string)
- `warranty` (string)

### `sale_finalize` (~80 tokens)

Finalize the bill of sale for signing

Finalize a bill of sale so it is ready to sign: the document is frozen from this call on, sale_update refuses it, and every later render is the signing copy without the DRAFT watermark. Free tier: 5 finalized documents.

Input parameters:

- `sale` (string, required): The bill of sale id, e.g. BOS-2026-0001

### `sale_list` (~77 tokens)

List bills of sale

List every bill of sale, drafts and finalized, newest first: id, status, date, item, buyer, seller and price. Filter to drafts or finalized documents with status.

Input parameters:

- `limit` (integer): Maximum rows, default 500
- `status` (string): Which documents to list: all (default), draft, or final

### `sale_get` (~69 tokens)

Read one bill of sale

Read one bill of sale in full by its BOS number: both parties, the item and its identifiers, price, terms, and whether it is still a draft or the finalized signing copy.

Input parameters:

- `sale` (string, required): The bill of sale id, e.g. BOS-2026-0001

### `sale_delete` (~111 tokens)

Delete a bill of sale

Delete a bill of sale by its BOS number. A draft goes outright. A finalized document needs confirm_finalized true, because it is the local copy of a record the buyer may hold. The BOS number is never reissued, so a gap in the series is the record that a document was deleted.

Input parameters:

- `confirm_finalized` (boolean): Required true to delete a finalized document. Default false
- `sale` (string, required): The bill of sale id, e.g. BOS-2026-0001

### `sale_render` (~232 tokens)

Print the bill of sale

Render a bill of sale as a clean printable document: Markdown, a self-contained HTML file ready for print-to-PDF, or both, with signature lines for seller and buyer. Drafts render with a DRAFT watermark so a review copy cannot be signed by mistake. Every file comes back as a download link valid for one hour, and out_path is only the stem the files are named with. Free.

Input parameters:

- `format` (string): What to render: markdown, html, or both (default). The HTML is one self-contained file, no external assets
- `out_path` (string): Name for the downloaded files, e.g. civic-sale; with format both, .md and .html are appended to the stem. Default: the document id. Each file comes back as a download link valid for one hour
- `overwrite` (boolean): Replace an existing file at out_path. Default false: an occupied explicit path is refused, a derived one gets -2, -3, ...
- `sale` (string, required): The bill of sale id, e.g. BOS-2026-0001

### `sale_summary` (~43 tokens)

Summarize the sales book

Summarize the book: how many drafts and finalized documents, and the total sold value per currency, drafts separate from finalized. Currencies are never added together. Free.

### `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-bill-of-sale/mcp-bill-of-sale#diagnostics

## Score history

- 2026-09-21: 82
- 2026-09-20: 80
- 2026-09-19: 80
- 2026-09-18: 79
- 2026-09-17: 25
- 2026-09-16: 78
- 2026-09-15: 78
- 2026-09-14: 77
- 2026-09-13: 77
- 2026-09-12: 76

## Common questions

### What is the io.github.theluckystrike/bill-of-sale MCP server?

io.github.theluckystrike/bill-of-sale is an MCP server listed in the public MCP registry as io.github.theluckystrike/bill-of-sale. Bills of sale for equipment, vehicles and stock: draft, finalize, print with signature lines. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/bill-of-sale).

### Is the io.github.theluckystrike/bill-of-sale MCP server safe to use?

io.github.theluckystrike/bill-of-sale scores 82 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/bill-of-sale MCP server expose?

io.github.theluckystrike/bill-of-sale exposes 10 tools: sale_create, sale_update, sale_finalize, sale_list, sale_get, and 5 more. Their descriptions and schemas cost roughly 1,623 tokens of context every time the server is loaded.

### Does the io.github.theluckystrike/bill-of-sale MCP server require authentication?

Yes. io.github.theluckystrike/bill-of-sale 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/bill-of-sale MCP server still maintained?

io.github.theluckystrike/bill-of-sale 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.

## Links

- Remote endpoint: https://mcp.zovo.one/mcp/bill-of-sale
- Authorisation metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/bill-of-sale
- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/bill-of-sale
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-bill-of-sale/mcp-bill-of-sale.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-bill-of-sale/mcp-bill-of-sale.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-bill-of-sale/mcp-bill-of-sale