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.

ChartPNG

NPM · @CHARTPNG/MCP

Draw Chart.js charts as PNG images: a shareable image URL or the PNG itself.

Available components

67 Trust /100

Last scanned (5 hours ago)

Scores higher than 35% of npm servers

Category Design and Media

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 Security97
  • 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
  • 1 of 1 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 283 tokens (~141/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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.

  • 5 Nov 26 +1

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

  • 4 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 3 Nov 26 +1
    • Malware scan: unverified → pass ▲ security
    • Dependency health: 0.85 → 0.75 ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • Package version: 0.1.0 → 0.2.0 functional
  • 2 Nov 26 50

    First indexed and scored.

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 5 Nov 2026 · Analysed npm/@chartpng/mcp@0.2.0

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 1 package
Packages resolved 1
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~283 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
chart_url ~156

Get a public PNG URL for a chart. Use it when the chart goes into an email, a Slack or chat message, a PDF or a Markdown document (as ![title](url)). The data travels in the URL: anyone with the URL can see the chart and its data, so for confidential data use render_chart.

NameTypeReqDescription
backgroundstring–CSS color, default white
configobjectyesA Chart.js v4 configuration as plain JSON (no functions), e.g. {"type":"bar","data":{"labels":[...],"datasets":[{"label":"...","data":[...]}]}}
heightinteger–Pixels, default 360
widthinteger–Pixels, default 600

No output schema declared.

No examples provided.

render_chart ~127

Render a chart and return the PNG image itself, to look at it or save it as a file. Takes configs up to 16 KB of JSON, larger than a URL allows.

NameTypeReqDescription
backgroundstring–CSS color, default white
configobjectyesA Chart.js v4 configuration as plain JSON (no functions), e.g. {"type":"bar","data":{"labels":[...],"datasets":[{"label":"...","data":[...]}]}}
heightinteger–Pixels, default 360
widthinteger–Pixels, default 600

No output schema declared.

No examples provided.

Install

How do I install the ChartPNG MCP server?

ChartPNG runs locally as an npm package, launched with npx -y @chartpng/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 · @chartpng/mcp

# add to Claude Code
claude mcp add dev-chartpng-chartpng -- npx -y @chartpng/mcp
Common questions

What is the ChartPNG MCP server?

ChartPNG is an MCP server listed in the public MCP registry as dev.chartpng/chartpng. Draw Chart.js charts as PNG images: a shareable image URL or the PNG itself. This page covers its npm package (@chartpng/mcp).

Is the ChartPNG MCP server safe to use?

ChartPNG scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 ChartPNG MCP server expose?

ChartPNG exposes 2 tools: chart_url, render_chart. Their descriptions and schemas cost roughly 283 tokens of context every time the server is loaded.

Is the ChartPNG MCP server still maintained?

ChartPNG is still listed as active in the MCP registry. We last reached this channel on 5 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 ChartPNG MCP server under?

ChartPNG declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.