Excel automation via xlwings COM. DRM-protected files, live sessions, VBA macros. Windows only.
MCP server for Excel automation via xlwings COM. Works with DRM-protected files. Libraries like or read files directly from disk. This fails when: DRM / file-level encryption is applied (common in enterprise environments) You need to interact with a live Excel session (formulas, macros, add-ins) Files are locked by another process uses COM automation to talk to the running Excel process, so it…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 2 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
MCP server for Excel automation via xlwings COM. Works with DRM-protected files. Libraries like or read files directly from disk. This fails when: DRM / file-level encryption is applied (common in enterprise environments) You need to interact with a live Excel session (formulas, macros, add-ins) Files are locked by another process uses COM automation to talk to the running Excel process, so it can read and write any file that Excel itself can open -- including DRM-protected documents. These…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.