io.github.mortenator/charta
NPM · @CHARTA/MCP
Generate beautiful, presentation-ready charts (SVG + PNG). Supports 14+ chart types.
Available components
Last scanned (14 hours ago)
Scores higher than 51% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects sharp 0.33.5, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 123 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 251 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 441 tokens (~88/item across 5 items; 5 tools + 0 resources), lean.Pass
- 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 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- 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.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
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.
- 19 Nov 26 +1
- Stability: 0.97 → pass security
- 18 Nov 26 −1
- Stability: pass → 0.97 functional
- 12 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 −2
- Stability: pass → 0.87 functional
- 27 Oct 26 +1
- Stability: 0.97 → pass security
- 25 Oct 26 −1
- Stability: pass → 0.93 functional
- 24 Oct 26 0
- CVE-2023-54404 affects this package: high ▼ security
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/@charta/mcp@1.0.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 →
Vulnerabilities 4 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-f88m-g3jw-g9cj | CVE-2026-114113 | high | yes | |
| GHSA-rgj7-g3m4-5g8c | CVE-2026-114112 | high | yes | |
| GHSA-wq5f-xc86-pv6w | CVE-2026-114111 | high | yes | |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 123 packages
| Packages resolved | 123 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
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 →
describe_chart ~91
Given your data and context, recommend the best chart type and explain why. Also suggests alternatives. Great for when you're not sure which chart to use.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | What you're trying to show or communicate. E.g. 'quarterly revenue growth over 2 years', 'market share by product', 'project timeline' |
| data | array | yes | Your data array (can be partial/sample data) |
No output schema declared.
No examples provided.
generate_chart ~149
Generate a beautiful, presentation-ready chart and return it as an SVG string. The chart is automatically cached and can be saved later with save_chart.
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | Data points. Shape varies by chart type — use list_chart_types or get_chart_schema for details. |
| seriesLabels | array | – | Series labels for multi-series charts (grouped-bar, stacked-bar, line with values[]) |
| style | object | – | Optional styling options |
| title | string | – | Optional chart title displayed at the top |
| type | string | yes | The type of chart to generate |
| xLabel | string | – | Optional X-axis label |
| yLabel | string | – | Optional Y-axis label |
No output schema declared.
No examples provided.
get_chart_schema ~42
Get the full JSON schema for a specific chart type, including all required and optional fields.
| Name | Type | Req | Description |
|---|---|---|---|
| type | string | yes | The chart type to get the schema for |
No output schema declared.
No examples provided.
list_chart_types ~35
List all supported chart types with descriptions, required data shapes, and examples. Use this to discover which chart type fits your data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
save_chart ~124
Save a chart to a file as SVG or PNG. Provide either a chartId (from a previous generate_chart call) or an SVG string directly.
| Name | Type | Req | Description |
|---|---|---|---|
| chartId | string | – | The chartId returned by generate_chart (preferred) |
| format | string | yes | Output format. PNG requires the 'sharp' package to be installed. |
| outputPath | string | yes | Absolute or relative path where the file should be saved, e.g. /tmp/chart.png or ./output/revenue.svg |
| svg | string | – | SVG string to save directly (alternative to chartId) |
No output schema declared.
No examples provided.
How do I install the io.github.mortenator/charta MCP server?
io.github.mortenator/charta runs locally as an npm package, launched with npx -y @charta/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 · @charta/mcp
claude mcp add mortenator-charta -- npx -y @charta/mcp
What is the io.github.mortenator/charta MCP server?
io.github.mortenator/charta is an MCP server listed in the public MCP registry as io.github.mortenator/charta. Generate beautiful, presentation-ready charts (SVG + PNG). Supports 14+ chart types. This page covers its npm package (@charta/mcp).
Is the io.github.mortenator/charta MCP server safe to use?
io.github.mortenator/charta scores 75 out of 100 on VerifyMCP. We recorded 4 known advisories 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 io.github.mortenator/charta MCP server expose?
io.github.mortenator/charta exposes 5 tools: generate_chart, list_chart_types, get_chart_schema, save_chart, describe_chart. Their descriptions and schemas cost roughly 441 tokens of context every time the server is loaded.
Is the io.github.mortenator/charta MCP server still maintained?
io.github.mortenator/charta 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.mortenator/charta MCP server under?
io.github.mortenator/charta 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.mortenator/charta MCP server?
VerifyMCP ran 15 checks on io.github.mortenator/charta, 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 io.github.mortenator/charta: Security disclosure. 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.