Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.theluckystrike/gantt-chart

MCPB · SPREADSHEET.MCPB · 2 COMPONENTS

Build Gantt charts from your AI chat: tasks, dependencies, timeline spreadsheets. All data is local.

0 this week 62 Trust /100

Last scanned (18 hours ago)

Scores higher than 96% of MCPB servers

Category Data and Analytics

Trust breakdown (7 categories)

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 Security22
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs were checked across the 101 of 101 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • 40 of 101 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1519 tokens (~138/item across 11 items; 10 tools + 1 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 87% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 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
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • 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.

  • Malware scan in Supply Chain SecurityNo malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.

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 →

Changelog

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.

  • 18 Nov 26 0
    • Stability: 0.97 → pass security
  • 17 Nov 26 0
    • Stability: pass → 0.97 functional
  • 12 Nov 26 0
    • Provenance: unverified → fail ▼ security
  • 11 Nov 26 0
    • Provenance: fail → unverified ▼ security
    • Stability: 0.97 → pass security
  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 5 Nov 26 −2
    • Stability: pass → 0.80 functional
  • 30 Oct 26 0
    • Stability: 0.97 → pass security
Diagnostics

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 mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/spreadsheet.mcpb@0.22.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Dependencies 101 packages
Packages resolved 101
Stale 40
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~1,487 tokens

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 →

Tool Tokens
license_activate ~71

Activate a Pro key (MCPL1.xxx.yyy) from checkout: verified offline against a built-in public key, saved to your config file. A wrong, malformed or expired key is refused, unsaved. license_status reads it back.

NameTypeReqDescription
keystringyesLicense key from the checkout confirmation page

No output schema declared.

No examples provided.

license_status ~54

Report this server's licence state: product, tier free or pro, licence id, expiry, the key source and the upgrade URL. No arguments, no network. Explains a free-tier refusal; license_activate installs a key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

sheet_add_column ~289

Call this tool to add a computed column and save the result to a NEW file; the source is never modified unless out_path points at it. Returns the new file path, the row count and a preview of the first rows.

NameTypeReqDescription
decimalsinteger–Round numeric formula results to this many decimals. Default: the widest decimal count of the columns the formula reads, capped at 2 when they all hold 2 or fewer (money in, money out); otherwise no…
formulastring–Expression over the columns of each row, in the same expression language as sheet_query, e.g. "[Qty] * [Unit Price]" or '[Country] = "PL"'. Give either formula or values
namestringyesName of the new column. It must not already exist on the sheet
out_pathstring–Output file; default <source>-plus-<column>.<same ext>. The source file is left untouched unless this points at it
pathstringyesPath to the source .xlsx/.xlsm/.xlsb/.ods/.csv/.tsv file (~ is expanded); it is never modified
sheetstring–Sheet name; default is the first sheet
valuesarray–Explicit values, one per data row, instead of a formula. Missing entries are left blank

No output schema declared.

No examples provided.

sheet_convert ~167

Call this tool to convert a sheet between excel (xlsx), csv and json. Writes a new file next to the source unless out_path is given; the source is never modified. Returns the new file path with its row and column counts.

NameTypeReqDescription
out_pathstring–Where to write; default is the source name with the new extension, next to the source. It must differ from the source path
pathstringyesPath to the source .xlsx/.xlsm/.xlsb/.ods/.csv/.tsv file (~ is expanded); it is never modified
sheetstring–Sheet to convert; default is the first sheet. Only that one sheet is written
tostringyesTarget format; the default out_path takes this as its extension

No output schema declared.

No examples provided.

sheet_find ~123

Call this tool to search every cell of a spreadsheet or CSV for text; built-in file readers cannot parse spreadsheets. Matching is case insensitive. Returns cell addresses with a preview of the row each hit is on.

NameTypeReqDescription
pathstringyesPath to the .xlsx/.xlsm/.xlsb/.ods/.csv/.tsv file (~ is expanded)
sheetstring–Sheet name; default searches every sheet
textstringyesText to look for; matched case insensitively anywhere inside a cell. Up to 200 hits are returned

No output schema declared.

No examples provided.

sheet_info ~79

Call this tool for any spreadsheet or CSV file path; built-in file readers cannot parse spreadsheets and must not be used for them. Start here: sheet names, size, header row, column types and samples.

NameTypeReqDescription
pathstringyesPath to the .xlsx/.xlsm/.xlsb/.ods/.csv/.tsv file (~ is expanded)

No output schema declared.

No examples provided.

sheet_query ~240

Call this tool for any spreadsheet or CSV file path; built-in file readers cannot parse spreadsheets and must not be used for them. Filters, groups, aggregates and sorts in one call: where '[Qty] > 10'.

NameTypeReqDescription
aggregatearray–Aggregates per group, e.g. [{"col":"Units","fn":"sum","as":"total_units"}]. Defaults to a row count when group_by is given.
asstring––
group_byarray–Group rows by these columns before aggregating, e.g. ["Rep"] or ["Region","Rep"]
limitinteger–Default 100
pathstringyesPath to the .xlsx or .csv file
selectarray–Column names to return; default all (with group_by, defaults to the group columns plus the aggregates)
sheetstring––
sortobject–Sort column; may be an aggregate alias such as total_units
wherestring–Filter, e.g. [Qty] >= 5 AND ([Status] = "open" OR [Status] = "new")

No output schema declared.

No examples provided.

sheet_read ~138

Call this tool for any spreadsheet or CSV file path; built-in file readers cannot parse spreadsheets and must not be used for them. Reads rows as a table, JSON or CSV; page with limit/offset or an A1 range.

NameTypeReqDescription
asstring–Output format, default table
limitinteger–Rows to return, default 100
offsetinteger–Rows to skip, default 0
pathstringyes–
rangestring–A1 range such as A1:D50; overrides limit/offset
sheetstring–Sheet name; defaults to the first sheet

No output schema declared.

No examples provided.

sheet_stats ~82

Call this tool for any spreadsheet or CSV file path; built-in file readers cannot parse spreadsheets and must not be used for them. Whole-column statistics: count, empty, distinct, min, max, sum, mean, median.

NameTypeReqDescription
columnsarray–Limit to these columns; default all
pathstringyes–
sheetstring––

No output schema declared.

No examples provided.

sheet_write ~244

Call this tool to write rows to an xlsx, csv, tsv or json file; the extension of out_path picks the format. mode is new_file, append or overwrite. Other sheets are kept. Free: 500 rows per file.

NameTypeReqDescription
modestringyesnew_file writes a brand new file and refuses to clobber an existing one; append adds the rows under the existing data; overwrite replaces the file contents
out_pathstring–Where to write; default is a new file next to the source for new_file, or the source itself for append/overwrite. The output format follows this extension: .xlsx, .csv, .tsv or .json. An extension is…
pathstringyesSource file for append/overwrite, or the intended file for new_file (~ is expanded)
rowsarrayyesArray of objects, whose keys become the headers, or an array of arrays with the header row first
sheetstring–Sheet to write; default is the first sheet of the source, or "Sheet1" for a new file. Other sheets of an existing workbook are kept unchanged

No output schema declared.

No examples provided.

Install

How do I install the io.github.theluckystrike/gantt-chart MCP server?

io.github.theluckystrike/gantt-chart ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check the download against.

mcpb · spreadsheet.mcpb

Download bundle

The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check it against. Open it with an MCPB-capable host such as Claude Desktop.

Common questions

What is the io.github.theluckystrike/gantt-chart MCP server?

io.github.theluckystrike/gantt-chart is an MCP server listed in the public MCP registry as io.github.theluckystrike/gantt-chart. Build Gantt charts from your AI chat: tasks, dependencies, timeline spreadsheets. All data is local. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/spreadsheet.mcpb).

Is the io.github.theluckystrike/gantt-chart MCP server safe to use?

io.github.theluckystrike/gantt-chart scores 62 out of 100 on VerifyMCP. 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 io.github.theluckystrike/gantt-chart MCP server expose?

io.github.theluckystrike/gantt-chart exposes 10 tools: license_status, license_activate, sheet_info, sheet_read, sheet_query, and 5 more. Their descriptions and schemas cost roughly 1,487 tokens of context every time the server is loaded.

What licence is the io.github.theluckystrike/gantt-chart MCP server under?

io.github.theluckystrike/gantt-chart 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 io.github.theluckystrike/gantt-chart MCP server?

VerifyMCP ran 15 checks on io.github.theluckystrike/gantt-chart, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.theluckystrike/gantt-chart: Malware scan. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.