Skip to main content
Glama
theluckystrike

mcp-bill-of-sale

by theluckystrike
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to mcp-bill-of-sale

No user-submitted related servers found.

    Related Servers

    • mcp-credit-note

      theluckystrike
      A
      license
      A
      quality
      B
      maintenance
      Enables issuing credit notes and credit memos against an invoice or standalone as revisable drafts that can be finalized into frozen numbered documents, then rendered as Markdown or printable HTML with totals broken down by currency, reason and month. All amounts are handled as integer minor units and all data stays local, so nothing is sent anywhere.
      10
      MIT

    • mad-invoice-mcp

      mad-sol-dev
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables creation and management of invoices with JSON storage and LaTeX-based PDF rendering. Supports draft creation and professional PDF generation through customizable LaTeX templates.
      Apache 2.0

    • Job Card

      theluckystrike
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables trades and field service work to be tracked per job: logging labor hours at worker rates and materials used, keeping running totals in integer cents per currency, and moving each job through a status machine from open to invoiced or archived. It also produces daily or weekly summaries of hours and value, and renders a printable card with a signature line for client sign-off.
      MIT

    • blocksign-mcp

      andrecolin
      A
      license
      Not graded
      quality
      C
      maintenance
      Blockchain-anchored e-signatures. Create, send, negotiate, and verify legally binding agreements — every signature anchored to XRPL + Bitcoin with public verification. Agents can pay autonomously.
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a distinct lifecycle or query role: create/update/finalize/render/list/get/delete/summary cover separate actions, while license_status and license_activate are clearly separated. No overlapping purposes or ambiguous boundaries are apparent.

    Naming Consistency5/5

    All tools use snake_case with resource prefixes (sale_* and license_*), making the set predictable. The suffix choices are consistent enough for an agent to infer the target domain and action.

    Tool Count5/5

    Ten tools is well-scoped for a bill-of-sale server with license management. Each tool earns its place, covering core document lifecycle plus necessary licensing checks.

    Completeness5/5

    The surface covers full lifecycle: create, read/list, update, finalize, render, delete, summarize, and license activation/status. No obvious gaps for the stated bill-of-sale domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources