io.github.lazyants/lexware
NPM · @LAZYANTS/LEXWARE-MCP-SERVER · SCANNED AUG 3
MCP server for the Lexware Office API — invoices, contacts, articles, and vouchers.
Available components
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (120 of 121), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (120 of 121), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency84
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to lazyants/lexware-mcp-server). View diagnostics → Pass
- License check failed: the license (FSL-1.1-MIT) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 (good).Pass
- Tool/resource definitions use about 4062 tokens (~60/item across 67 items; 66 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @lazyants/lexware-mcp-server
claude mcp add lazyants-lexware -- npx -y @lazyants/lexware-mcp-server
codex mcp add lazyants-lexware -- npx -y @lazyants/lexware-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lazyants-lexware": {
"type": "local",
"command": [
"npx",
"-y",
"@lazyants/lexware-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add lazyants-lexware --command npx --arg -y --arg @lazyants/lexware-mcp-server
mcp_servers:
lazyants-lexware:
command: "npx"
args: ["-y", "@lazyants/lexware-mcp-server"] {
"mcpServers": {
"lazyants-lexware": {
"command": "npx",
"args": [
"-y",
"@lazyants/lexware-mcp-server"
]
}
}
} 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.
- 3 Aug 26 +28
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Provenance: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- The attested source repository moved: lazyants/lexware-mcp-server security
- License: unverified → fail ▼ functional
- MCP protocol: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Licence: FSL-1.1-MIT functional
- 2 Aug 26 +10
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- 31 Jul 26 +31
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −67
- Provenance: pass → unverified ▼ security
- Known CVEs: partial → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- The attested source repository moved: lazyants/lexware-mcp-server security
- License: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Dependency health: partial → unverified ▼ functional
- Maintenance: pass → unverified ▼ functional
- Licence: FSL-1.1-MIT functional
- 28 Jul 26 +65
- Provenance: unverified → pass ▲ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- The attested source repository moved: lazyants/lexware-mcp-server security
- License: unverified → fail ▼ functional
- Security disclosure: unverified → fail ▼ functional
- Maintenance: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: good functional
- First check of Schema quality: pass functional
- First check of Schema quality: fail functional
- Licence: FSL-1.1-MIT functional
- 27 Jul 26 8
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 3 Aug 2026 · Analysed npm/@lazyants/[email protected]
Provenance verified
Ecosystem: npm · Outcome: verified
Reason: verified
- Source repo:
- lazyants/lexware-mcp-server
- Certificate issuer:
- https://token.actions.githubusercontent.com
- Certificate SAN:
- https://github.com/lazyants/lexware-mcp-server/.github/workflows/publish-registry.yml@refs/tags/v5.0.0
- Rekor log index:
- 2259829562
- Predicate type:
- https://slsa.dev/provenance/v1
- Subject digest:
- sha512:b51b9f9d0a8032db0834ef61b1f0e36c45fb24798ac7c12833c54221481ceb13ab30f2725ff5e7ff4ac17c8930cdcb8e3459516000d45284b171b3dba
- Discovery method:
- attestation_endpoint
Dependencies 120 packages
120 packages in the resolved dependency tree · 120 deprecated · 32 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
lexware_list_posting_categories List Posting Categories ~20
List all available posting categories for bookkeeping.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lexware_list_print_layouts List Print Layouts ~18
List available print layout templates.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lexware_list_recurring_templates List Recurring Templates ~47
List recurring invoice templates from Lexware.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | — | Page number (0-indexed) |
| size | integer | — | Results per page (max 250) |
No output schema declared.
No examples provided.
lexware_list_voucherlist List Voucherlist ~294
Search and filter across all voucher types in Lexware. This is the main way to find invoices, credit notes, quotations, and other voucher types.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | — | Filter by archived status |
| contactId | string | — | Filter by contact UUID |
| createdDateFrom | string | — | Filter by creation date from (yyyy-MM-dd) |
| createdDateTo | string | — | Filter by creation date to (yyyy-MM-dd) |
| page | integer | — | Page number (0-indexed) |
| size | integer | — | Results per page (max 250) |
| voucherDateFrom | string | — | Filter vouchers from date (ISO, e.g. "2024-01-01") |
| voucherDateTo | string | — | Filter vouchers to date (ISO, e.g. "2024-12-31") |
| voucherNumber | string | — | Filter by voucher number |
| voucherStatus | string | — | Voucher status(es), comma-separated, or "any" for no status filter (default). Values: draft, open, overdue, paid, paidoff, voided, accepted, rejected, unchecked |
| voucherType | string | — | Voucher type(s), comma-separated, or "any" for no type filter (default). Values: invoice, creditnote, orderconfirmation, quotation, deliverynote, downpaymentinvoice, dunning, purchaseinvoice, purchas… |
No output schema declared.
No examples provided.
lexware_list_vouchers List Vouchers ~60
List bookkeeping vouchers from Lexware with optional filters.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | — | Page number (0-indexed) |
| size | integer | — | Results per page (max 250) |
| voucherNumber | string | — | Filter by voucher number |
No output schema declared.
No examples provided.
lexware_pursue_credit_note Pursue to a Credit Note ~171
Create a new credit note as a follow-up to a preceding invoice. Maps to the documented `POST /credit-notes?precedingSalesVoucherId={id}[&finalize=true]` endpoint. Set finalize=true to immediately finalize the credit note; omit or false to create as draft.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | Credit note JSON body. Same shape as lexware_create_credit_note. See Lexware API docs for full schema. |
| finalize | boolean | — | When true, creates the credit note in finalized status (immediately paid-off, reducing the invoice open amount). When false or omitted, creates as draft. Maps to the documented ?finalize=true query p… |
| precedingSalesVoucherId | string | yes | UUID of the preceding invoice that this credit note is pursued from. |
No output schema declared.
No examples provided.
lexware_pursue_delivery_note Pursue to a Delivery Note ~109
Create a new delivery note as a follow-up to a preceding quotation or order confirmation. Maps to the documented `POST /delivery-notes?precedingSalesVoucherId={id}` endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | Delivery note JSON body. Same shape as lexware_create_delivery_note. See Lexware API docs for full schema. |
| precedingSalesVoucherId | string | yes | UUID of the preceding sales voucher (quotation or order confirmation) that this delivery note is pursued from. |
No output schema declared.
No examples provided.
lexware_pursue_dunning Pursue to a Dunning ~142
Create a new dunning as a follow-up to a preceding invoice via the documented `POST /dunnings?precedingSalesVoucherId={id}` endpoint. Dunnings are always created in draft mode and do not need to be finalized.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | Dunning JSON body. Key fields: voucherDate, address (object with contactId or manual fields), lineItems (array), totalPrice (object), taxConditions (object). See Lexware API docs for full schema. |
| precedingSalesVoucherId | string | yes | UUID of the preceding invoice that this dunning is pursued from. Required by the Lexware API. |
No output schema declared.
No examples provided.
lexware_pursue_invoice Pursue to an Invoice ~198
Create a new invoice as a follow-up to a preceding sales voucher (quotation, order confirmation, or delivery note). Maps to the documented `POST /invoices?precedingSalesVoucherId={id}[&finalize=true]` endpoint. Set finalize=true to immediately finalize the new invoice (status "open"); omit or false to create as draft.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | Invoice JSON body. Same shape as lexware_create_invoice. Required fields: voucherDate, address, lineItems, totalPrice, taxConditions. See Lexware API docs for full schema. |
| finalize | boolean | — | When true, creates the invoice in finalized "open" status. When false or omitted, creates as draft. Maps to the documented ?finalize=true query parameter. |
| precedingSalesVoucherId | string | yes | UUID of the preceding sales voucher (quotation, order confirmation, or delivery note) that this invoice is pursued from. |
No output schema declared.
No examples provided.
lexware_pursue_order_confirmation Pursue to an Order Confirmation ~99
Create a new order confirmation as a follow-up to a preceding quotation. Maps to the documented `POST /order-confirmations?precedingSalesVoucherId={id}` endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | Order confirmation JSON body. Same shape as lexware_create_order_confirmation. See Lexware API docs for full schema. |
| precedingSalesVoucherId | string | yes | UUID of the preceding quotation that this order confirmation is pursued from. |
No output schema declared.
No examples provided.
lexware_update_article Update Article ~70
Update an existing article. The body must include the version field for optimistic locking.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | Article JSON with version field included for optimistic locking. Key fields: title, type, unitName, unitPrice, description, version (required) |
| id | string | yes | Article ID |
No output schema declared.
No examples provided.
lexware_update_contact Update Contact ~52
Update an existing contact. The body must include the version field for optimistic locking.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | Contact JSON with version field. Same structure as create. |
| id | string | yes | Contact ID |
No output schema declared.
No examples provided.
lexware_update_voucher Update Voucher ~51
Update an existing bookkeeping voucher in Lexware. Requires version field for optimistic locking.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | Voucher JSON with version field for optimistic locking |
| id | string | yes | Voucher UUID |
No output schema declared.
No examples provided.
lexware_upload_file Upload File ~61
Upload a file to Lexware.
| Name | Type | Req | Description |
|---|---|---|---|
| contentBase64 | string | yes | Base64-encoded file content |
| contentType | string | — | MIME type, defaults to application/pdf |
| fileName | string | yes | Name of the file to upload |
No output schema declared.
No examples provided.
lexware_upload_voucher_file Upload Voucher File ~74
Upload a file attachment to a bookkeeping voucher.
| Name | Type | Req | Description |
|---|---|---|---|
| contentBase64 | string | yes | Base64-encoded file content |
| contentType | string | — | MIME type, defaults to application/pdf |
| fileName | string | yes | Name of the file to upload |
| id | string | yes | Voucher UUID |
No output schema declared.
No examples provided.
lexware_verify_webhook_signature Verify Webhook Signature ~171
Verify a Lexware webhook X-Lxo-Signature (RSA-SHA512, base64) against the raw request body. Pass the EXACT raw HTTP body bytes you received — do not JSON.parse/stringify round-trip, as Lexware signs the compact JSON as transmitted (whitespace and key order matter). On first call the public key is fetched once from developers.lexware.io and cached for the process lifetime; set LEXWARE_WEBHOOK_PUBLIC_KEY (PEM) to override (recommended for production where you cannot tolerate one-time TLS-substitution risk on the public-key fetch).
| Name | Type | Req | Description |
|---|---|---|---|
| payload | string | yes | Raw HTTP request body received from Lexware (verbatim, untransformed). |
| signature | string | yes | Value of the X-Lxo-Signature header (base64). |
No output schema declared.
No examples provided.