Xlsx (knorq-ai) MCP Server

xlsx-mcp-server npm v1.1.0

Published by knorq-ai — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Trust grade
A
99/100
Last scanned
Trust
A · 99/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
A Why this grade threat 100 − adoption risk = 99/100

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 − 1 = 99. 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:

PointsAdoption-risk factor
capability blast radius (minimal) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable
inspection depth (source) — how much of the target the scan could see

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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 37

Each tool and what it can reach — statically extracted from the published source.

  • add_data_validationno sensitive capability
  • add_named_rangeno sensitive capability
  • add_sheetno sensitive capability
  • clear_cellsno sensitive capability
  • copy_sheetno sensitive capability
  • create_workbookno sensitive capability
  • delete_columnsno sensitive capability
  • delete_named_rangeno sensitive capability
  • delete_rowsno sensitive capability
  • delete_sheetno sensitive capability
  • format_cellsno sensitive capability
  • format_cells_bulkno sensitive capability
  • get_sheet_propertiesno sensitive capability
  • get_workbook_infono sensitive capability
  • insert_columnsno sensitive capability
  • insert_rowsno sensitive capability
  • list_data_validationsno sensitive capability
  • list_imagesno sensitive capability
  • list_named_rangesno sensitive capability
  • merge_cellsno sensitive capability
  • read_cellno sensitive capability
  • read_sheetno sensitive capability
  • remove_auto_filterno sensitive capability
  • remove_data_validationno sensitive capability
  • rename_sheetno sensitive capability
  • search_cellsno sensitive capability
  • set_auto_filterno sensitive capability
  • set_column_widthno sensitive capability
  • set_column_widthsno sensitive capability
  • set_freeze_panesno sensitive capability
  • set_row_heightno sensitive capability
  • set_row_heightsno sensitive capability
  • unmerge_cellsno sensitive capability
  • write_cellno sensitive capability
  • write_cellsno sensitive capability
  • write_rowno sensitive capability
  • write_rowsno sensitive capability

What this scan could not see

Versions

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.

VersionScoreFindingsEngineScanned
v1.1.0 latest A 99/100 0 1.8.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.

MCP Trust Score: A · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/xlsx-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/xlsx-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/xlsx-mcp-server"><img src="https://mcptrustchecker.com/registry/xlsx-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/xlsx-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

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 xlsx-mcp-server --online

Use the free API → How scoring works

Other implementations of Xlsx 2

Independent packages implementing the same tool, scanned with the same engine. Compare all 3 side by side →

More in Files & Storage