Bill Of Sale Generator

io.github.theluckystrikePublished by GitHub account theluckystrikev0.22.5Updated Oct 24, 2026

Record a vehicle, equipment or stock sale and print a bill of sale with signature lines.

VerifiedSTDIODesktop onlyProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

A local MCP server that records vehicle, equipment or stock sales and produces a printable bill of sale with signature lines.

What you can do
Create, update and finalize bills of sale with seller, buyer, item identifiers, price and date, keeping drafts editable until frozen into a signing copy. List, retrieve and summarize the sales book, with draft and finalized counts and totals kept separate per currency. Render documents as Markdown or a self-contained HTML file for print-to-PDF, with a DRAFT watermark on review copies. Delete drafts, or finalized documents only with explicit confirmation. Check and activate a free or Pro license.
When to use it
Useful when a small seller needs a paper-ready record of a second-hand vehicle, equipment or stock sale, including an as-is clause, warranty wording and signature lines, without an account or cloud service.
Requirements
Runs as a local process on the user's machine (desktop only). The README notes the npm package is not yet published, so a clone and build is currently the working install path. No account, API key or network access is needed; an optional Pro license key can be supplied through the MCP_LICENSE_KEY environment variable.
Before you install
The free tier caps open drafts at 10 and finalized documents at 5; Pro is a paid one-time purchase. Deleting a finalized document requires explicit confirmation and its number is never reissued. The rendered document is a generic template, not legal advice, and vehicle, boat or regulated-goods sales may have statutory form or filing requirements. Data is stored locally on disk.

Installation

In SourceWeft

  1. Open Bill Of Sale Generator in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

mcp-bill-of-sale

[theluckystrike/mcp-bill-of-sale MCP server]

In the official MCP Registry (io.github.theluckystrike/bill-of-sale). Record a sale and get a signed-paper-ready bill of sale. Tell your assistant who sold, who bought, what the item is, with the VIN, serial number or IMEI where it has one, the price and the date, and the server writes the document: parties, item, price, an as-is clause for second-hand sales, any warranty in your own words, and signature lines for both sides. Work on it as a draft, finalize it into the frozen signing copy, and print it as Markdown or as a single self-contained HTML file that prints to PDF from any browser with no assets beside it. Everything stays on your machine; there is no account and no network call in this server at all.

Built by theluckystrike.

npm publish for @theluckystrike/mcp-bill-of-sale is pending, so npx -y @theluckystrike/mcp-bill-of-sale returns 404 today. Until then, a clone+build is the working path.

Install

Claude Desktop

macOS ~/Library/Application Support/Claude/claude_desktop_config.json, Windows %APPDATA%\Claude\claude_desktop_config.json:

json
{  "mcpServers": {    "bill-of-sale": {      "command": "npx",      "args": ["-y", "@theluckystrike/mcp-bill-of-sale"]    }  }}

Claude Code

sh
claude mcp add bill-of-sale -- npx -y @theluckystrike/mcp-bill-of-sale

Cursor

~/.cursor/mcp.json (global) or .cursor/mcp.json (project), same entry as Claude Desktop.

Tools

toolwhat it does
sale_createRecord a sale and generate the bill of sale: seller, buyer, item with VIN/serial/IMEI where it has one, price in minor units, date. Returns BOS-YYYY-NNNN. An identical repeat sale is refused unless you confirm it
sale_updateChange anything on a draft before signing: price, parties, item details, identifiers, the as-is clause, warranty, notes. Empty string clears an optional field
sale_finalizeFreeze the draft into the signing copy. From here sale_update refuses it and every render prints without the DRAFT watermark
sale_listEvery bill of sale, newest first: id, status, date, item, buyer, seller, price. Filter to drafts or finalized
sale_getOne bill of sale in full by its BOS number
sale_deleteDelete a draft outright; a finalized document needs confirm_finalized: true. The number is never reissued, so a gap in the series is the record of the deletion
sale_renderPrint the document: Markdown, a self-contained HTML file for print-to-PDF, or both, with signature lines. Drafts carry a DRAFT watermark so a review copy cannot be signed by mistake
sale_summaryThe book at a glance: draft and finalized counts, total value per currency. Currencies are never added together
license_status / license_activateFree or Pro, and the key

Free vs Pro

FreePro
Open drafts10Unlimited
Finalized documents5Unlimited
Render to Markdown and HTML (sale_render)UnlimitedUnlimited
Read, list and summarize (sale_get, sale_list, sale_summary)UnlimitedUnlimited
Delete (sale_delete)YesYes

The document itself is never metered. Whether you hold a signed record of the sale is the question this server exists to answer, and a free tier that withholds the document is a demo. What is metered is the volume of records held: ten open drafts and five finalized documents is a real year of side-business sales, not a trial. sale_delete is free for the same reason the cap is on records held: a draft typed in twice would otherwise cost a slot with no way back but a key.

Get Pro: https://mcp.zovo.one/buy/bill-of-sale, $19 one-time for this server, or $39 for the bundle.

How a sale flows

  1. sale_create with the facts. The seller defaults to the shared business profile's name when the profile has one, so the seller block is typed once for the whole suite.
  2. sale_render prints the review copy, watermarked DRAFT.
  3. sale_update fixes anything the buyer or seller spots.
  4. sale_finalize freezes it. sale_render now prints the signing copy: sign the printed page or print the HTML to PDF, and both parties keep a copy.

Every amount is an integer number of minor units, a price is never a float, and dates are checked as real calendar dates. A VIN that is not 17 characters or an IMEI that is not 15 digits is stored as given but flagged in the response, because those are the two identifiers a buyer most often misreads.

Privacy

All data stays local, in ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/bill-of-sale/. Two files: sales.json, counter.json, plus rendered documents under documents/. Nothing is sent anywhere, there is no account, no API key and no network call in this server at all. License keys are verified offline.

The rendered document is a generic template, not legal advice. Bills of sale for vehicles, boats and regulated goods may have statutory form or filing requirements where the sale happens.

Built by theluckystrike. https://github.com/theluckystrike

Use these docs as an MCP server

Any MCP client (Claude, Cursor, Windsurf, VS Code) can read this repository's documentation directly via GitMCP - no install:

Source: servers/bill-of-sale/README.md at commit 1bd9d69

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.22.5LatestOct 14, 2026
  2. v0.21.0Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts