Mmcp.market

Xlsx Audit MCP server

by arose26·io.github.arose26/xlsx-audit-mcp·v0.1.0

Audit Excel workbooks: formula dependency tracing, circular references, risk smells. Local only.

A88/100grade A
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
New

0 stars24 downloads/wk

Reviews

Write one

Nobody has reviewed Xlsx Audit yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Xlsx Audit tools (4)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • audit_workbook

    Risk report across the whole model: circular references (with example chains), volatile functions (INDIRECT/OFFSET/NOW/RAND...), hardcoded constants inside formulas, external workbook links, merged cells, very long formulas.

  • list_formulas

    Formulas with addresses and cached values. Filter with `contains` (e.g. 'INDIRECT', 'VLOOKUP') and/or `sheet`.

  • trace_cell

    Audit one cell: its formula and cached value, precedents (cells and ranges it reads), and dependents (formulas that read it, directly or via a range). Address like 'Summary!B14'; unqualified addresses use the first sheet.

  • workbook_overview

    Structure of an .xlsx workbook: sheets with dimensions and formula counts, defined names, external workbook links, merged cells. The map you need before tracing or auditing.

Public scan report

scanner v0.1.9 · 2026-09-23 · same rubric, same numbers if you re-run it

no findings
  • Code scan7 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 40 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

What the publisher says

From the Xlsx Audit repository's README, as published. We do not edit it. Read it on GitHub

xlsx-audit-mcp

An MCP server that audits Excel workbooks. Other Excel MCP servers read and write your data — this one reviews your model:

  • "What feeds the Total cell on the Summary sheet?" — precedent tracing
  • "If I change this assumption, what breaks?" — dependent tracing, including cells that consume it through ranges like SUM(A1:A40)
  • "Audit this workbook" — circular references with example chains, volatile functions (INDIRECT, OFFSET, NOW, RAND...), hardcoded constants buried inside formulas, external workbook links, merged cells, extra-long formulas

Spreadsheet mistakes are famously expensive. This is the "trace precedents" discipline auditors apply by hand, exposed to an LLM for a whole workbook at once. Local files only; nothing leaves your machine.

Quick start

Claude Code

claude mcp add xlsx-audit -- npx -y xlsx-audit-mcp

Claude Desktop — add to claudedesktopconfig.json:

{
  "mcpServers": {
    "xlsx-audit": {
      "command": "npx",
      "args": ["-y", "xlsx-audit-mcp"]
    }
  }
}

Then: "Audit C:\\models\\budget-2026.xlsx and tell me what looks fragile."

Tools

How it works

  • Reference tokenizer that understands real formulas: string literals are stripped first (the "A1" in INDIRECT("A1") is not a reference), function names can't collide (the G10 in LOG10(...) is not a cell), $ absolutes, quoted sheet names ('My Data'!A1), and ranges are handled.
  • Shared formulas are materialized. Excel stores filled formulas once with an offset scheme; the loader translates them per-cell (relative refs shifted, absolutes preserved), so dependency queries see what each cell actually computes.
  • Ranges are never expanded for storage — dependents queries use range-containment tests, and cycle detection caps range fan-out (a SUM(A:A) can't explode the graph; capped ranges are reported, not silently dropped).
  • No formula evaluation. Cached values from the file are shown instead — no spreadsheet engine dependency.

Known limitations: R1C1 notation and structured table references ([@Column]) are counted but not resolved into the graph.

Development

npm install
npm test                 # offline tests — synthetic workbooks built in-suite
npm run build            # tsc → dist/
node scripts/smoke.mjs   # end-to-end: generates a workbook, drives the server over stdio

Architecture: src/xlsx.ts (zip + XML → workbook model) and src/formulas.ts (tokenizer, graph, smells) are pure logic; src/index.ts is the MCP wiring.

License

MIT

Nothing above is checked by us. What we check is on the safety report.

Install directly

Runs npx -y xlsx-audit-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add xlsx-audit-mcp -- npx -y xlsx-audit-mcp
Add to Cursor

Xlsx Audit: common questions

Is Xlsx Audit MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the Xlsx Audit safety report
How do I install Xlsx Audit?
It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does Xlsx Audit need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Xlsx Audit maintained?
The last commit was 41 days ago (2026-08-14). The latest release is v0.1.0.

More from arose26 →