io.github.theluckystrike/bill-of-sale
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS · SCANNED SEP 20
Bills of sale for equipment, vehicles and stock: draft, finalize, print with signature lines.
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 1675 tokens (~152/item across 11 items; 10 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 68% 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; "sale_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 11 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/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.
remote · mcp.zovo.one
claude mcp add --transport http theluckystrike-bill-of-sale 'https://mcp.zovo.one/mcp/bill-of-sale'
{
"mcpServers": {
"theluckystrike-bill-of-sale": {
"url": "https://mcp.zovo.one/mcp/bill-of-sale"
}
}
} {
"servers": {
"theluckystrike-bill-of-sale": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/bill-of-sale"
}
}
} [mcp_servers.theluckystrike-bill-of-sale] url = "https://mcp.zovo.one/mcp/bill-of-sale"
{
"$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 mcp add theluckystrike-bill-of-sale --url 'https://mcp.zovo.one/mcp/bill-of-sale' --transport streamable-http
mcp_servers:
theluckystrike-bill-of-sale:
url: "https://mcp.zovo.one/mcp/bill-of-sale" {
"McpServers": {
"theluckystrike-bill-of-sale": {
"Transport": "http",
"Url": "https://mcp.zovo.one/mcp/bill-of-sale"
}
}
} assistant mcp add theluckystrike-bill-of-sale -t streamable-http -u 'https://mcp.zovo.one/mcp/bill-of-sale'
{
"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.
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.
- 19 Sept 26 +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.
- 18 Sept 26 +54
- Authorization: unverified → fail ▼ security
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Stability: unverified → 0.20 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Server version: 0.21.0 → 0.22.0 functional
- 17 Sept 26 −53
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: 0.13 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 15 Sept 26 +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.
- 13 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Sept 26 76
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 · Probed https://mcp.zovo.one/mcp/bill-of-sale
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/bill-of-sale | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/bill-of-sale | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/bill-of-sale |
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 →
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.
sale_create Record a sale ~606
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | 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 | yes | 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 | yes | 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 |
No output schema declared.
No examples provided.
sale_delete Delete a bill of sale ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_finalized | boolean | – | Required true to delete a finalized document. Default false |
| sale | string | yes | The bill of sale id, e.g. BOS-2026-0001 |
No output schema declared.
No examples provided.
sale_finalize Finalize the bill of sale for signing ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| sale | string | yes | The bill of sale id, e.g. BOS-2026-0001 |
No output schema declared.
No examples provided.
sale_get Read one bill of sale ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| sale | string | yes | The bill of sale id, e.g. BOS-2026-0001 |
No output schema declared.
No examples provided.
sale_list List bills of sale ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum rows, default 500 |
| status | string | – | Which documents to list: all (default), draft, or final |
No output schema declared.
No examples provided.
sale_render Print the bill of sale ~232
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The bill of sale id, e.g. BOS-2026-0001 |
No output schema declared.
No examples provided.
sale_summary Summarize the sales book ~43
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sale_update Change a bill of sale before signing ~274
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | – | – |
No output schema declared.
No examples provided.
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 80 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.