McpStamp Bill of Sale
MCPB · BILL-OF-SALE.MCPB · 2 COMPONENTS
Bills of sale for vehicles, equipment or phones: drafts and signing copies with signature lines.
Available components
Last scanned (3 hours ago)
Scores higher than 93% of MCPB servers
Category Documents and Files
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security23
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs were checked across the 92 of 92 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 49 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1592 tokens (~159/item across 10 items; 10 tools + 0 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 10 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
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.
- 2 Nov 26 +54
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Dependency health: unverified → 0.85 ▲ functional
- Licence: MIT functional
- Package version: 0.22.5 → 0.21.0 functional
- 30 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 28 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 26 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 25 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 24 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 23 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 14 Oct 26 −52
- Stability: 0.87 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.87 → unverified ▼ security
- Known CVEs: partial → unverified ▼ security
- Provenance: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Dependency health: 0.84 → unverified ▼ functional
- License: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Maintenance: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- First check of Schema quality: unverified functional
- Licence: MIT functional
- Package version: 0.22.0 → 0.22.5 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 5 Nov 2026 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/bill-of-sale.mcpb@0.21.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 ~71
Activate a Pro key (MCPL1.xxx.yyy) from checkout: verified offline against a built-in public key, saved to your config file. A wrong, malformed or expired key is refused, unsaved. license_status reads it back.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from the checkout confirmation page |
No output schema declared.
No examples provided.
license_status License status ~54
Report this server's licence state: product, tier free or pro, licence id, expiry, the key source and the upgrade URL. No arguments, no network. Explains a free-tier refusal; license_activate installs a key.
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 ~207
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. Files default to the server's documents folder; pass out_path to choose. 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 | – | Where to write. With format both this is a stem and .md / .html are appended. Default: the server's documents folder under the data directory |
| 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.
How do I install the McpStamp Bill of Sale MCP server?
McpStamp Bill of Sale ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, e31c3b024a8e61f2c203b11fed048b2da87880c9385f7efa4e89f7d65b40384a; the commands to do that are on this page. If it does not match, do not open it.
mcpb · bill-of-sale.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
e31c3b024a8e61f2c203b11fed048b2da87880c9385f7efa4e89f7d65b40384a
macOS / Linux
echo "e31c3b024a8e61f2c203b11fed048b2da87880c9385f7efa4e89f7d65b40384a bill-of-sale.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\bill-of-sale.mcpb).Hash -eq "e31c3b024a8e61f2c203b11fed048b2da87880c9385f7efa4e89f7d65b40384a"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the McpStamp Bill of Sale MCP server?
McpStamp Bill of Sale is an MCP server listed in the public MCP registry as io.github.theluckystrike/bill-of-sale. Bills of sale for vehicles, equipment or phones: drafts and signing copies with signature lines. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/bill-of-sale.mcpb).
Is the McpStamp Bill of Sale MCP server safe to use?
McpStamp Bill of Sale scores 59 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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 McpStamp Bill of Sale MCP server expose?
McpStamp 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,592 tokens of context every time the server is loaded.
What licence is the McpStamp Bill of Sale MCP server under?
McpStamp Bill of Sale declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.