Spreadshet Audit MCP
Related Servers
Alternatives to Spreadshet Audit MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceAudits Excel workbooks by tracing cell dependencies and detecting circular references, volatile functions, and other formula risks, enabling natural-language audit queries on local files.443 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to edit real .xlsx workbooks in place through spreadsheet-native tools like describe, find, read, write, and structural edits, recalculating formulas without Excel, LibreOffice, or Python. Every change comes back as a review link showing changed cells before and after, and nothing is written until the user accepts, while charts, pivots, and VBA data return byte-identical.10Apache 2.0
- AlicenseAqualityAmaintenance50 tools and 400 functions for working with Excel/.xlsx spreadsheets — read/write, recalculate formulas, diff, repair broken references, and audit. Built for AI agents.503,792 npm6MIT
- FlicenseCqualityBmaintenanceAn MCP server for safe .xlsx inspection and controlled workbook writes, enabling spreadsheet reads, search, filtering, aggregation, and preview-based writes with workspace confinement and audit logging.12-
- AlicenseBqualityBmaintenanceProvides secure, agentic Excel analysis and calculation capabilities, enabling users to inspect workbook structure, perform statistical computations, write formulas, and generate outputs through whitelisted MCP tools with audit trails and backups.15MIT
- AlicenseNot gradedqualityAmaintenanceValidates Excel (.xlsx) workbooks against reviewed, lockable acceptance contracts, catching errors and outputting structured issues that agents can repair.22 PyPI1MIT
TDQS
Scored across 2 tools
The two tools are cleanly separated: audit_workbook performs a whole-file heuristic sweep, while inspect_cell zooms in on a single cell's formula, value, and precedents. The drill-down workflow is explicitly described, so an agent can always tell which to reach for.
Both names follow the same verb_noun snake_case convention (audit_workbook, inspect_cell), with verbs that accurately mirror each tool's scope. No stylistic deviations.
Two tools is at the thin edge for a spreadsheet auditing server; the surface is coherent but leaves no room for reporting, filtering, or remediation operations. It works as a minimal diagnose-then-drill pair, nothing more.
Detection and follow-up tracing are covered, but there is no way to export or summarize findings, fix/annotate flagged issues, or compare across workbooks. For a read-only audit domain this is workable, but agents will hit dead ends on any remediation or reporting task.