io.github.lazyants/lexware
io.github.lazyants/lexware
Is the io.github.lazyants/lexware MCP server down? Yes. It has given no valid answer since 2026-10-27: crashed on start.
MCP server for the Lexware Office API — invoices, contacts, articles, and vouchers.
crashed on start down since 2026-10-27 · probed 2026-11-14
MCP error -32000: Connection closed
Error: LEXWARE_READ_ONLY must be "true", "1", "false" or "0" (unset or empty means off).
at ModuleJob.run (node:internal- Run it
- npx -y @lazyants/lexware-mcp-server@5.5.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/lazyants/lexware-mcp-server
- Registry
- active, updated 2026-11-13 · registry entry
- Changes
- 2 recorded, reachable in 1 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.laveeshb/logicapps-mcp · alive
- qURL io.github.layervai/qurl-mcp · crashed on start
- Layoza io.github.layoza/layoza · crashed on start
- io.github.lazyants/hetzner · alive
- io.github.lazyants/transkribus · alive
- io.github.lazymac2x/mcpwatch · alive
- io.github.lazytitan30/billing-doctor · alive
- io.github.lchampz/heimdall · alive
Servers that mention lexware.
- Lexware Office MCP by usefulapi io.usefulapi/lexware-office · timeout
- io.github.benethos-hub/benethos-lexware-office-mcp · alive
- Konverter Pro de.konverter-pro/konverter-pro · alive
- Lexware Office (lexoffice) MCP Server and API by Cotlet dev.cotlet/lexware-office · not probed
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-10-27 06:55 | crashed on start | ||||
| 2026-10-16 06:26 | alive | 634 ms | 66 | 22k | 13k |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-10-27, in every probe since then.
- The process exited on start before it answered initialize. The error output is above.