Xlwings (PyPI) MCP Server
xlwings-mcp-server
PyPI
v1.0.4
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 8 = 92. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
high Shell/command execution in server code (src/xlwings_mcp/session.py)MTC-SRC-002
In the server's implementation (`src/xlwings_mcp/session.py:536`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: subprocess.run(['taskkill', '/F', '/PID', str(session.process_id)],
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/xlwings_mcp/session.py
Tools 29
Each tool and what it can reach — statically extracted from the published source.
apply_formulano sensitive capabilityclose_workbookno sensitive capabilitycopy_rangeno sensitive capabilitycopy_worksheetno sensitive capabilitycreate_chartno sensitive capabilitycreate_pivot_tableno sensitive capabilitycreate_tableno sensitive capabilitycreate_workbookno sensitive capabilitycreate_worksheetno sensitive capabilitydelete_rangeno sensitive capability
Show 19 more tools ↓
delete_sheet_columnsno sensitive capabilitydelete_sheet_rowsno sensitive capabilitydelete_worksheetno sensitive capabilityforce_close_workbook_by_path_toolno sensitive capabilityformat_rangeno sensitive capabilityget_data_validation_infono sensitive capabilityget_merged_cellsno sensitive capabilityget_workbook_metadatano sensitive capabilityinsert_columnsno sensitive capabilityinsert_rowsno sensitive capabilitylist_workbooksno sensitive capabilitymerge_cellsno sensitive capabilityopen_workbookno sensitive capabilityread_data_from_excelno sensitive capabilityrename_worksheetno sensitive capabilityunmerge_cellsno sensitive capabilityvalidate_excel_rangeno sensitive capabilityvalidate_formula_syntaxno sensitive capabilitywrite_data_to_excelno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (29 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.4 latest |
A 92/100 | 1 | 1.9.0 | 2026-07-23 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan xlwings-mcp-server --online --registry pypiOther implementations of Xlwings 1
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
More in Developer Tools
Security scan results for the 1stay MCP server.
Security scan results for the Adguard Home MCP server.
Security scan results for the Ado Browser MCP server.
Security scan results for the Adobe Experience Dev MCP server.
Security scan results for the Aemet MCP server.
Security scan results for the Affinity Mcp Bridge MCP server.