MCP server for terminal commands, file operations, and process management
Nothing to run from here
xlvane: XLSX workbooks is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
97/100
trust score
7
tools declared
local
runs on your machine
—
downloads a day
What it does
XLSX tools: inspect, read, diff and validate workbooks; write, edit and convert with --allow-write.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user xlvane-xlsx-workbooks-mcp '--' npx -y @xlvane/mcp --root '<root>'
# 2 — ask your agent for something these tools do
# inspect_workbook, read_table, diff and 4 more
Put your own value in place of <root> before you run this.
xlvane: XLSX workbooks costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
DEAll 1 server
devxord1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts xlvane: XLSX workbooks as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Put your own value in place of <root> before you run this. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user xlvane-xlsx-workbooks-mcp '--' npx -y @xlvane/mcp --root '<root>'Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Describes an XLSX file without changing it: sheets (including hidden ones), used ranges, detected header rows, column types with sample values, merged cells, example formulas, and warnings (macros, external links, damaged parts). Macros are never run and links are never followed. Use it before…
No parameter schema on file.
Reads a sheet as an array of row objects keyed by the header row (or by column letters with header: false). Dates are returned as ISO 8601 strings in UTC, error cells as their code (e.g. "#N/A"), formulas as their cached result. Returns at most … rows per call; use offset to page through larger…
No parameter schema on file.
Compares two XLSX files cell by cell (values and formulas; formatting with styles: true). Sheets are matched by name. Use it to check the result of an edit.
No parameter schema on file.
Reports read warnings of an XLSX file and, with columns, checks a table: each listed column must exist in the header row, its cells must not be empty unless optional is true, and must have the given type. Each problem names the cell. ok is false when problems were found (warnings count only with…
No parameter schema on file.
Writes an array of row objects (or arrays) to an XLSX file. The "report" preset (default) adds a bold header row, frozen first row, autofilter, fitted column widths and date and number formats; "plain" writes values only. Strings that look like ISO dates stay strings; pass {"date": "..."} for dates.
No parameter schema on file.
Changes cells and appends rows in an existing XLSX file while keeping everything else in it (styles, formulas, other sheets) unchanged. The result is written to output; to change the file in place, omit output and pass "overwrite": true. xlvane does not calculate formulas; the edited file asks…
No parameter schema on file.
Converts a sheet of an XLSX file to CSV, TSV or JSON (an array of row objects), or CSV, TSV or JSON to a plain XLSX file. Formats come from the file extensions. CSV output escapes text that starts with =, +, -, @ and similar characters, so spreadsheet programs do not run it as a formula; dates are…
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install xlvane: XLSX workbooks or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 97 / 100
Release 1.2.2 · scanned 3 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score97
Findings0 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationsource
Surface digestf0e527cec12b3a5080fd964c710f5a79c0a4a76ba74a4ebdd081796e8cc4db87
Score vectorthreat 100 → client 97
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (7 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>".
3 of the 7 recovered tools are registered only when !allowWrite is false (dist/server-B1Px_tvv.js:724) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 4.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
4 tools are registered unconditionally · 3 more only when !allowWrite is false (dist/server-B1Px_tvv.js:724) — typically when a key or option is configured. All 7 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| inspect_workbook | no tags | |
| read_table | no tags | |
| diff | no tags | |
| validate | no tags | |
| write_table conditional | state-write | state-write: declares readOnlyHint: false |
| edit_cells conditional | state-write | state-write: declares readOnlyHint: false |
| convert conditional | state-write | state-write: declares readOnlyHint: false |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestf0e527cec12b3a50
Scanned2026-11-03
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.2.2. Pin a release below and the command asks for exactly that one.
1.2.2
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish xlvane: XLSX workbooks can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.