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.gluip/chart-canvas

NPM · @GLUIP/CHART-CANVAS-MCP

Create interactive visualizations and query data sources (SQLite, CSV, Parquet, JSON)

0 this week 83 Trust /100

Last scanned (17 hours ago)

Scores higher than 73% of npm 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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 42 of 137 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 605 tokens (~86/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "removeVisualization" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 7 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 (16)

  • Malware scan
  • 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

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.

  • 21 Nov 26 0
    • Stability: pass → 0.97 functional
  • 15 Nov 26 0
    • Stability: 0.97 → pass security
  • 14 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.

  • 12 Nov 26 +1

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

  • 10 Nov 26 +1

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

  • 8 Nov 26 +1

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

  • 6 Nov 26 +1

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

  • 4 Nov 26 −5
    • Stability: pass → 0.63 functional
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 npm/@gluip/chart-canvas-mcp@0.3.2

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 →

Dependencies 137 packages
Packages resolved 137
Stale 42
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~605 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
addVisualization ~130

Add a new chart visualization to the canvas

NameTypeReqDescription
descriptionstring–Optional description or explanation for the chart
mermaidstring–Mermaid diagram syntax (required for flowchart type)
seriesarray–Array of data series to display (required for charts)
tableobject–Table data (required for table type)
titlestring–Optional title for the chart
typestringyesType of visualization to create
xLabelsarray–Optional labels for the x-axis (e.g., dates). Should match the number of data points.

No output schema declared.

No examples provided.

clearCanvas ~16

Remove all visualizations from the canvas

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

getDatabaseSchema ~95

Get the schema of a data source (SQLite database, CSV, Parquet, or JSON file) including all tables/columns. Use this to understand the data structure before writing queries.

NameTypeReqDescription
databasePathstringyesPath to the data file. Supported formats: SQLite (.db, .sqlite, .sqlite3), CSV (.csv), Parquet (.parquet), JSON (.json, .jsonl, .ndjson)

No output schema declared.

No examples provided.

queryAndVisualize ~196

Execute a SQL query on a data source (SQLite, CSV, Parquet, or JSON file) and create a visualization from the results. The query must be read-only (SELECT only). You must specify how to map columns to the visualization.

NameTypeReqDescription
columnMappingobject–Mapping of query result columns to chart axes. Not required for table type.
databasePathstringyesPath to the data file (SQLite, CSV, Parquet, JSON)
descriptionstring–Optional description for the visualization
querystringyesSQL SELECT query to execute (read-only, max 10000 rows)
titlestring–Optional title for the visualization
useColumnAsXLabelboolean–If true, use the xColumn values as labels instead of numeric values (useful for dates/categories)
visualizationTypestringyesType of visualization to create from the query results

No output schema declared.

No examples provided.

removeVisualization ~30

Remove a visualization from the canvas by ID

NameTypeReqDescription
idstringyesID of the visualization to remove

No output schema declared.

No examples provided.

showCanvas ~20

Open the canvas in a browser window to view visualizations

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

updateVisualization ~118

Update an existing visualization on the canvas. You can change its data, title, description, or any other property.

NameTypeReqDescription
descriptionstring–Updated description
idstringyesID of the visualization to update
mermaidstring–Updated Mermaid diagram syntax
seriesarray–Updated data series for charts
tableobject–Updated table data
titlestring–Updated title
typestring–Type of visualization
xLabelsarray–Updated x-axis labels

No output schema declared.

No examples provided.

Install

How do I install the io.github.gluip/chart-canvas MCP server?

io.github.gluip/chart-canvas runs locally as an npm package, launched with npx -y @gluip/chart-canvas-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 · @gluip/chart-canvas-mcp

# add to Claude Code
claude mcp add gluip-chart-canvas -- npx -y @gluip/chart-canvas-mcp
Common questions

What is the io.github.gluip/chart-canvas MCP server?

io.github.gluip/chart-canvas is an MCP server listed in the public MCP registry as io.github.gluip/chart-canvas. Create interactive visualizations and query data sources (SQLite, CSV, Parquet, JSON). This page covers its npm package (@gluip/chart-canvas-mcp).

Is the io.github.gluip/chart-canvas MCP server safe to use?

io.github.gluip/chart-canvas scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting 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 io.github.gluip/chart-canvas MCP server expose?

io.github.gluip/chart-canvas exposes 7 tools: addVisualization, removeVisualization, updateVisualization, clearCanvas, showCanvas, and 2 more. Their descriptions and schemas cost roughly 605 tokens of context every time the server is loaded.

Is the io.github.gluip/chart-canvas MCP server still maintained?

io.github.gluip/chart-canvas 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 io.github.gluip/chart-canvas MCP server under?

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

VerifyMCP ran 16 checks on io.github.gluip/chart-canvas, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.