# io.szum/charts

Create, inspect, manage, and render charts and data visualizations as SVG/PNG or interactive embeds.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 2.0.0
- **Author:** io.szum
- **License:** Unknown
- **Endpoints:** streamable-http https://szum.io/mcp
- **Source:** https://szum.io
- **Endpoint health:** reachable (last checked 2026-09-30T19:15:34.603Z, 6 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 32 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-03T05:04:59.615Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

13 declared. Observed from a live `tools/list` probe.
- `render_chart` — Use this when the user wants to preview or generate a chart. Validate each generated or changed config once before rendering, saving, or updating. Do not revali
- `save_chart` — Use this when the user wants to permanently save and publish a chart from a Szum config. Validate each generated or changed config once before rendering, saving
- `list_charts` — Use this when the user wants to find charts in their saved library. Returns paginated metadata and URLs, not chart configs; requires authentication. Draft-only 
- `get_chart` — Use this when the user identifies a saved chart by id and wants to view it or retrieve its metadata and URLs. Displays the published chart when available and do
- `get_chart_config` — Use this when the user identifies a saved chart by id and needs its complete published Szum config for inspection or reuse. Does not return a newer editor draft
- `get_preview_state` — Use this when the Szum chart App needs to restore a rendered preview as its current transient or saved view. It is read-only, owner-scoped when authenticated, a
- `update_chart` — Use this when the user wants to replace and publish a saved chart's config while keeping its id and URLs. Validate each generated or changed config once before 
- `rename_chart` — Use this when the user wants to change a saved chart's library title without changing its config, publication state, or public URLs; requires authentication.
- `delete_chart` — Use this when the user explicitly wants to permanently delete one saved chart. Deletion cannot be undone, and retrying an already completed deletion succeeds; r
- `validate_chart` — Use this when a chart config will be rendered, saved, or updated. Validate each generated or changed config once before rendering, saving, or updating. Do not r
- `list_themes` — Use this when choosing a visual theme for a chart. Returns every available theme and guidance on where each works best.
- `list_marks` — Use this when choosing or configuring chart mark types. Returns every available mark with its properties and defaults.
- `get_examples` — Use this when the model needs current, ready-to-use Szum chart configs or preferred semantic patterns. Optionally filters examples by mark type.

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"charts\": {\n      \"type\": \"http\",\n      \"url\": \"https://szum.io/mcp\"\n    }\n  }\n}"
```

## Blast radius

Moderate to extensive — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: deletes data; runs on someone else's infrastructure.
- Floor 33, ceiling 57 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/io.szum%2Fcharts
- Install plan: https://forgeregistry.com/api/v1/packages/io.szum%2Fcharts/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/io.szum%2Fcharts
- HTML page: https://forgeregistry.com/registry/io.szum%2Fcharts
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.