io.github.lazyants/lexware
NPM · @LAZYANTS/LEXWARE-MCP-SERVER · SCANNED SEP 21
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 → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 34 of 121 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency87
- 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 31 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability85
- 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 4615 tokens (~68/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 Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 67 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
How do I install the io.github.lazyants/lexware MCP server?
io.github.lazyants/lexware runs locally as an npm package, launched with npx -y @lazyants/lexware-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @lazyants/lexware-mcp-server
claude mcp add lazyants-lexware -- npx -y @lazyants/lexware-mcp-server
{
"mcpServers": {
"lazyants-lexware": {
"command": "npx",
"args": [
"-y",
"@lazyants/lexware-mcp-server"
]
}
}
} {
"servers": {
"lazyants-lexware": {
"command": "npx",
"args": [
"-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": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@lazyants/lexware-mcp-server"
]
}
}
} assistant mcp add lazyants-lexware -t stdio -c npx -a -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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 −3
- Stability: pass → 0.77 functional
- 19 Sept 26 0
- Stability: 0.97 → pass security
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −1
- Stability: fail → 0.93 functional
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 96.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 86 to 89.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 79 to 83.
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 21 Sept 2026 · Analysed npm/@lazyants/lexware-mcp-server@5.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| 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.2.0 |
| Rekor log index | 2535429375 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:f555d0bdcf6f9f2d8f9b0e2426fdf0cbddc417210384b3e20ae09d68fa89e1703d0f392734f185893c2e46f6ec011e77544b1566f356e4350d8e42cdf |
Background: How many MCP packages publish verified provenance →
Dependencies 121 packages
| Packages resolved | 121 |
|---|---|
| Stale | 34 |
| 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 →
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 ~409
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 |
| contactName | string | – | Wildcard filter on contactName, applied client-side after fetching. % = any sequence, _ = exactly one character. Case-insensitive. Example: "Müller%". Implies fetchAllPages. |
| createdDateFrom | string | – | Filter by creation date from (yyyy-MM-dd) |
| createdDateTo | string | – | Filter by creation date to (yyyy-MM-dd) |
| fetchAllPages | boolean | – | When true, follow pagination until every page is retrieved (capped at 100 requests) instead of returning a single page. |
| hasOpenAmount | boolean | – | When true, keep only entries with openAmount > 0. Applied client-side after fetching. Implies fetchAllPages. |
| 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 Look Up Vouchers by Number ~144
Look up bookkeeping vouchers by voucher number. GET /vouchers is a LOOKUP endpoint, not a browsable collection: the Lexware API rejects any call without voucherNumber with HTTP 400 "voucherNumber parameter is required". To browse or filter vouchers, use lexware_list_voucherlist, which is the collection endpoint and carries the summary fields (contactName, openAmount) that /vouchers does not.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (0-indexed) |
| size | integer | – | Results per page (max 250) |
| voucherNumber | string | yes | Voucher number to look up. REQUIRED — the API returns 400 without it. |
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 ~176
Upload a file to Lexware. Provide either filePath (absolute path on the MCP server host) or contentBase64 (base64-encoded content) — not both. When using filePath, fileName is optional (derived from the file name) and contentType is auto-detected for common image extensions. When using contentBase64, fileName is required.
| Name | Type | Req | Description |
|---|---|---|---|
| contentBase64 | string | – | Base64-encoded file content. Required when filePath is not provided. |
| contentType | string | – | MIME type, defaults to application/pdf |
| fileName | string | – | File name for the upload. Required when using contentBase64; derived from filePath when omitted. |
| filePath | string | – | Absolute path to the file on the MCP server host. Must be readable by the MCP server process. |
No output schema declared.
No examples provided.
lexware_upload_voucher_file Upload Voucher File ~189
Upload a file attachment to a bookkeeping voucher. Provide either filePath (absolute path on the MCP server host) or contentBase64 (base64-encoded content) — not both. When using filePath, fileName is optional (derived from the file name) and contentType is auto-detected for common image extensions. When using contentBase64, fileName is required.
| Name | Type | Req | Description |
|---|---|---|---|
| contentBase64 | string | – | Base64-encoded file content. Required when filePath is not provided. |
| contentType | string | – | MIME type, defaults to application/pdf |
| fileName | string | – | File name for the upload. Required when using contentBase64; derived from filePath when omitted. |
| filePath | string | – | Absolute path to the file on the MCP server host. Must be readable by the MCP server process. |
| 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.
What is the io.github.lazyants/lexware MCP server?
io.github.lazyants/lexware is an MCP server listed in the public MCP registry as io.github.lazyants/lexware. MCP server for the Lexware Office API, invoices, contacts, articles, and vouchers. This page covers its npm package (@lazyants/lexware-mcp-server).
Is the io.github.lazyants/lexware MCP server safe to use?
io.github.lazyants/lexware scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 io.github.lazyants/lexware MCP server expose?
io.github.lazyants/lexware exposes 66 tools: lexware_create_invoice, lexware_get_invoice, lexware_download_invoice_file, lexware_pursue_invoice, lexware_deeplink_invoice, and 61 more. Their descriptions and schemas cost roughly 4,591 tokens of context every time the server is loaded.
Is the io.github.lazyants/lexware MCP server still maintained?
io.github.lazyants/lexware is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.lazyants/lexware MCP server under?
io.github.lazyants/lexware declares the FSL-1.1-MIT licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.