Skip to content

McpStamp Bill of Sale MCP server

io.github.theluckystrike/bill-of-saletheluckystrikestreamable-httpv0.23.0Scanned

Bills of sale for vehicles, equipment or phones: drafts and signing copies with signature lines.

10 tools: 1 can delete or cancel things, 1 do something that can't be undone, 4 change things and 4 only read.

Tools: 1 delete, 1 irreversible, 4 write, 4 read.
  • Reads private data · 1
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 1 does something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the McpStamp Bill of Sale MCP server can do

The McpStamp Bill of Sale MCP server is published by the GitHub account theluckystrike. It has 10 tools. It can delete or cancel things (1 tool: sale_delete), do things that cannot be undone, such as sending, paying or publishing (sale_finalize) and create or change data (4 tools: sale_create, sale_update, sale_render and license_activate). 4 tools only read.

1 tool reads private data (sale_summary); 1 tool brings in text other people can write (license_status).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 15, 2026, version 0.23.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

10 tools

Deletes or cancels 1Claude Code: deny
  • sale_deleteDelete a bill of sale by its BOS number.No findings

    Why it is in this group

    • The name "sale_delete" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
Can't be undone 1Claude Code: ask
  • sale_finalizeFinalize 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 water…No findings

    Why it is in this group

    • The name "sale_finalize" says "finalize": a word for a change that another call does not undo.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Changes things 4Claude Code: ask
  • license_activateTurn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • sale_createRecord 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.No findings

    Why it is in this group

    • The name "sale_create" says "create": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • sale_renderRender 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • sale_updateChange anything on a bill of sale that is not finalized yet: price, buyer, seller, item details, identifiers, the as-is clause, warranty or notes.No findings

    Why it is in this group

    • The name "sale_update" says "update": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 4Show 4 read-only tools
  • license_statusReport 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.Reads text others writeNo findings

    Why it is in this group

    • The name "license_status" says "status": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • sale_getRead 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.No findings

    Why it is in this group

    • The name "sale_get" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • sale_listList every bill of sale, drafts and finalized, newest first: id, status, date, item, buyer, seller and price.No findings

    Why it is in this group

    • The name "sale_list" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • sale_summarySummarize the book: how many drafts and finalized documents, and the total sold value per currency, drafts separate from finalized.Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "summarize": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "summarize" and "document": it reads documents.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:27 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
6
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/bill-of-sale
Authorization servers
https://mcp.zovo.one
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (1 destructive, 1 irreversible, 4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.zovo.one/mcp/bill-of-sale: tools/list returned 10 tools to an anonymous client, including sale_delete (destructive), sale_finalize (irreversible), sale_create (write), sale_update (write), sale_render (write) and 1 more

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource to https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/bill-of-sale

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource -> https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/bill-of-sale.View diff
    • RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource to https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/bill-of-sale

Install

Pinned to version 0.23.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http bill-of-sale https://mcp.zovo.one/mcp/bill-of-sale
claude mcp add --transport http bill-of-sale https://mcp.zovo.one/mcp/bill-of-sale

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__bill-of-sale__sale_list",
      "mcp__bill-of-sale__sale_get",
      "mcp__bill-of-sale__sale_summary",
      "mcp__bill-of-sale__license_status"
    ],
    "ask": [
      "mcp__bill-of-sale__sale_create",
      "mcp__bill-of-sale__sale_update",
      "mcp__bill-of-sale__sale_finalize",
      "mcp__bill-of-sale__sale_render",
      "mcp__bill-of-sale__license_activate"
    ],
    "deny": [
      "mcp__bill-of-sale__sale_delete"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as bill-of-sale. Review it before you use it.

Capability tags behind 2 rules
  • mcp__bill-of-sale__sale_summary private-data
  • mcp__bill-of-sale__license_status untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.theluckystrike/bill-of-sale/verify?hash=aaf173e60ef22a232cb463d4bf6f840add05c73ac484c63c67830f137a16ad21" | jq -e '.changed == false'

Pinned hash aaf173e60ef2, from Nov 15, 2026, 06:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.theluckystrike/bill-of-sale/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.theluckystrike/bill-of-sale
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.theluckystrike/bill-of-sale.svg)](https://radar.anlyon.com/servers/io.github.theluckystrike/bill-of-sale)

Source: MCP Registry · repository. Synced Nov 2, 2026, 03:18 UTC.

McpStamp Bill of Sale MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the McpStamp Bill of Sale MCP server safe?

No scan can promise that. What its definitions show: 10 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the McpStamp Bill of Sale MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: sale_delete.

Can the McpStamp Bill of Sale MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: sale_finalize.

What tools does the McpStamp Bill of Sale MCP server have?

10 tools: 1 destructive, 1 irreversible, 4 write, 4 read. sale_delete, sale_finalize, sale_create, sale_update, sale_render, license_activate, sale_list, sale_get and 2 more.

Does the McpStamp Bill of Sale MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the McpStamp Bill of Sale MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the McpStamp Bill of Sale MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.