io.github.benethos-hub/benethos-lexware-office-mcp
io.github.benethos-hub/benethos-lexware-office-mcp · v0.6.1
Unofficial MCP server for the Lexware Office accounting API — runs over stdio or HTTP.
Normalized over 100 points of available evidence.
Score breakdown
Known advisories
source: OSV.devMetadata change timeline
rug-pull detection- v0.6.0 → v0.6.1Oct 20, 2026
versionchanged version bump"0.6.0" → "0.6.1"
packages.0.versionchanged package version bump"0.6.0" → "0.6.1"
packages.1.identifierchanged image tag 0.6.0 → 0.6.1 (version)"ghcr.io/benethos-hub/benethos-lexware-office-mcp:0.6.0" → "ghcr.io/benethos-hub/benethos-lexware-office-mcp:0.6.1"
packages.2.identifierchanged version-only identifier change"https://github.com/benethos-hub/lexware-office-mcp/releases/download/v0.6.0/benethos-lexware-office-mcp-0.6.0.mcpb" → "https://github.com/benethos-hub/lexware-office-mcp/releases/download/v0.6.1/benethos-lexware-office-mcp-0.6.1.mcpb"
- First snapshot (v0.6.0)Oct 17, 2026
Tool lists: not published by the registry — unknown.
FAQ
auto-generated from the data aboveIs io.github.benethos-hub/benethos-lexware-office-mcp safe?
MCPWatch gives io.github.benethos-hub/benethos-lexware-office-mcp a heuristic security score of 93/100 (strong), based on 100 points of available evidence. This is an automated heuristic, not an audit.
Does io.github.benethos-hub/benethos-lexware-office-mcp have known CVEs or vulnerabilities?
No advisories were found in OSV.dev for the pypi package benethos-lexware-office-mcp. That is not proof of safety.
When was io.github.benethos-hub/benethos-lexware-office-mcp last updated?
The latest registry version is 0.6.1, published Oct 19, 2026. The last push to benethos-hub/lexware-office-mcp was on Oct 19, 2026. MCPWatch last checked it on Oct 21, 2026.
What license does io.github.benethos-hub/benethos-lexware-office-mcp use?
GitHub reports the license of benethos-hub/lexware-office-mcp as MIT.