tabular-mcp
NPM · @NOPILOT/TABULAR-MCP
CSV/JSONL/xlsx toolkit: schema inference, dirty-row reports, format conversion, seeded sampling
Available components
Last scanned (12 hours ago)
Scores higher than 38% of npm servers
Category Data and Analytics
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security89
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects uuid 8.3.2, reached via @nopilot/tabular-engine > exceljs > uuid. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 239 of 262 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 544 tokens (~181/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 16 Nov 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed npm/@nopilot/tabular-mcp@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 239 packages
| Packages resolved | 239 |
|---|---|
| Deprecated | 6 |
| Stale | 98 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
tabular_convert Convert tabular file ~206
Convert a local tabular file: csv->jsonl, jsonl->csv, or xlsx->csv/jsonl. Returns the converted content inline and optionally writes it to an output path. xlsx reads the first sheet by default (allSheets: true reads every non-empty sheet; multi-sheet CSV output uses "# sheet: <name>" separator lines, multi-sheet JSONL adds a "sheet" field). Same input always yields byte-identical output. Pure local computation, no network.
| Name | Type | Req | Description |
|---|---|---|---|
| allSheets | boolean | – | xlsx only: convert every non-empty sheet instead of just the first |
| format | string | – | Force the input format. Default: detect from extension (.csv/.tsv, .jsonl/.ndjson, .xlsx). |
| outputPath | string | – | Also write the converted content to this local path |
| path | string | yes | Absolute or cwd-relative path of the local file to read |
| to | string | yes | Target format |
No output schema declared.
No examples provided.
tabular_inspect Inspect tabular file ~149
Inspect a local CSV, JSONL (ndjson) or xlsx file: row count, column list, inferred schema (per-column dominant type + full type distribution + empty counts) and a dirty-row report with 1-based file row numbers (format errors, missing/extra columns, type drift vs the inferred schema). CSV: header = file row 1. JSONL: rows are line numbers. Pure local computation, no network.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Force the input format. Default: detect from extension (.csv/.tsv, .jsonl/.ndjson, .xlsx). |
| path | string | yes | Absolute or cwd-relative path of the local file to read |
No output schema declared.
No examples provided.
tabular_sample Stream-sample tabular file ~189
Sample rows from a local CSV/JSONL/xlsx file without loading it fully: head N, tail N, or seeded random sampling (deterministic: same file + count + seed always returns the exact same rows, independent of stream chunking). Each row carries its 1-based file row number. JSONL sampling streams the file, so arbitrarily large files are fine. Pure local computation.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of rows to return (1..10000) |
| format | string | – | Force the input format. Default: detect from extension (.csv/.tsv, .jsonl/.ndjson, .xlsx). |
| mode | string | yes | Sampling mode |
| path | string | yes | Absolute or cwd-relative path of the local file to read |
| seed | string | – | Deterministic seed for random mode (any string; same seed = same sample) |
No output schema declared.
No examples provided.
How do I install the tabular-mcp server?
tabular-mcp runs locally as an npm package, launched with npx -y @nopilot/tabular-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @nopilot/tabular-mcp
claude mcp add latbert-tabular-mcp -- npx -y @nopilot/tabular-mcp
What is the tabular-mcp server?
tabular-mcp is listed in the public MCP registry as io.github.latbert/tabular-mcp. CSV/JSONL/xlsx toolkit: schema inference, dirty-row reports, format conversion, seeded sampling. This page covers its npm package (@nopilot/tabular-mcp).
Is the tabular-mcp server safe to use?
tabular-mcp scores 66 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the tabular-mcp server expose?
tabular-mcp exposes 3 tools: tabular_inspect, tabular_convert, tabular_sample. Their descriptions and schemas cost roughly 544 tokens of context every time the server is loaded.
Is the tabular-mcp server still maintained?
tabular-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the tabular-mcp server under?
tabular-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the tabular-mcp server?
VerifyMCP ran 15 checks on tabular-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about tabular-mcp: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.