io.github.benethos-hub/benethos-lexware-office-mcp
PYPI · BENETHOS-LEXWARE-OFFICE-MCP · 3 COMPONENTS
Unofficial MCP server for the Lexware Office accounting API — runs over stdio or HTTP.
Last scanned (10 hours ago)
Scores higher than 62% of PyPI servers
Category Finance and Payments
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 35 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 355 tokens (~355/item across 0 items; 0 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Nothing to assess: this server has no tools to check for usage examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage0
- Nothing to assess: this server exposes no tools, so there are no tool definitions to check for coverage.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- Destructive-tool annotations not yet verified: our capture listed no tools, so there were no annotations to read.Unverified
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
- Package version: 0.5.4 → 0.6.0 functional
- 15 Oct 26 0
- Tool safety: pass → unverified ▼ 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
- Tool coverage: fail → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.5.3 → 0.5.4 functional
- 14 Oct 26 +20
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → fail ▼ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: unverified functional
- First check of Schema quality: fair functional
- First check of Schema quality: unverified functional
- Package version: 0.5.2 → 0.5.3 functional
- 12 Oct 26 39
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 18 Oct 2026 · Analysed pypi/benethos-lexware-office-mcp@0.6.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 35 packages
| Packages resolved | 35 |
|---|---|
| No linked repository | 1 |
| 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 →
The sandbox run completed and this package exposed no tools.
How do I install the io.github.benethos-hub/benethos-lexware-office-mcp server?
io.github.benethos-hub/benethos-lexware-office-mcp runs locally as a PyPI package, launched with uvx benethos-lexware-office-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · benethos-lexware-office-mcp
claude mcp add benethos-hub-benethos-lexware-office-mcp -- uvx benethos-lexware-office-mcp
What is the io.github.benethos-hub/benethos-lexware-office-mcp server?
io.github.benethos-hub/benethos-lexware-office-mcp is listed in the public MCP registry as io.github.benethos-hub/benethos-lexware-office-mcp. Unofficial MCP server for the Lexware Office accounting API, runs over stdio or HTTP. This page covers its PyPI package (benethos-lexware-office-mcp).
Is the io.github.benethos-hub/benethos-lexware-office-mcp server safe to use?
io.github.benethos-hub/benethos-lexware-office-mcp scores 61 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 2026. 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.benethos-hub/benethos-lexware-office-mcp server expose?
io.github.benethos-hub/benethos-lexware-office-mcp exposes no tools. We connected to it and read its tool list, and it was empty, so it offers an MCP client nothing to call.
Is the io.github.benethos-hub/benethos-lexware-office-mcp server still maintained?
io.github.benethos-hub/benethos-lexware-office-mcp is still listed as active in the MCP registry. We last reached this channel on 18 October 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.benethos-hub/benethos-lexware-office-mcp server under?
io.github.benethos-hub/benethos-lexware-office-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.