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.

Charts by Szum

REMOTE · SZUM.IO

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

Available components

0 this week 81 Trust /100

Last scanned (20 hours ago)

Scores higher than 83% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Data and Analytics

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability78
  • 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 3506 tokens (~184/item across 19 items; 16 tools + 3 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 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 18 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
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

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.

  • 5 Nov 26 0
    • Stability: 0.97 → pass security
  • 4 Nov 26 0
    • Stability: pass → 0.97 functional
  • 2 Nov 26 0
    • New tool “restore_chart_version”, which the server declares destructive security
    • Tool “get_chart_document” rewrote its description, which is the text the model reads security
    • Server version: 2.1.0 → 2.2.0 functional
    • New tool “list_chart_versions” functional
    • “get_chart_document” added an optional parameter “version” cosmetic
  • 26 Oct 26 +4
    • Stability: fail → pass ▲ security
  • 22 Oct 26 0
    • “update_chart” added an optional parameter “title” cosmetic
    • “update_chart” reworded the description of “sharedTheme” cosmetic

    2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 21 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “list_themes” rewrote its description, which is the text the model reads security
    • Server version: 2.0.0 → 2.1.0 functional
    • “list_charts” added an optional parameter “author” cosmetic
    • “render_chart” added an optional parameter “sharedTheme” cosmetic
    • “save_chart” added an optional parameter “sharedTheme” cosmetic
    • “update_chart” added an optional parameter “sharedTheme” cosmetic
  • 14 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_examples” rewrote its description, which is the text the model reads security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 5 Nov 2026 · Probed https://szum.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=szum.io CN=WE1,O=Google Trust Services,C=US 26 Sept 2026 25 Dec 2026 ECDSA 256 ECDSA-SHA256 760e5c94097272ad13f78dca4fd60acd
SANs: szum.io, *.szum.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of szum.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
szum.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://szum.io/mcp Verified 200
http (plaintext) http://szum.io/mcp HTTPS enforced 301 https://szum.io/mcp
MCP tools · 16 exposed · ~2,671 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
delete_chart ~55

Use this when the user explicitly wants to permanently delete one saved chart. Deletion cannot be undone, and retrying an already completed deletion succeeds; requires authentication.

NameTypeReqDescription
idstringyesOpaque 32-character saved-chart id
NameTypeReqDescription
deletedbooleanyes–

No examples provided.

get_chart ~62

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 does not return its document; requires authentication.

NameTypeReqDescription
idstringyesOpaque 32-character saved-chart id
NameTypeReqDescription
createdAtstringyesISO-8601 creation timestamp
documentUrlstringyesOwner-only chart-document endpoint
editUrlstringyes–
embedUrlstringyesInteractive-embed URL
idstringyesOpaque 32-character saved-chart id
imageUrlstringyesRendered-image URL
manageUrlstringyes–
publishedAtstring|nullyesISO-8601 publish timestamp, or null when public URLs are dark
sizeBytesintegeryesCompressed size of the stored published document, excluding drafts; 0 means no published document has been stored yet
sourcestringyesChart origin; an open set of string values
titlestringyesSaved chart title
updatedAtstringyesISO-8601 last-update timestamp
viewstringyes–

No examples provided.

get_chart_document ~89

Use this when the user identifies a saved chart by id and needs its complete published Szum document for inspection or reuse, or an earlier version's document from list_chart_versions. Does not return a newer editor draft; requires authentication.

NameTypeReqDescription
idstringyesOpaque 32-character saved-chart id
versioninteger–Version number from list_chart_versions; omit for the published document

Structured output declared, but exposes no named fields.

No examples provided.

get_examples ~194

Get complete Szum documents for validation, rendering, or saving, with guidance on when to use each pattern. No filters returns one starter per chart type. Any filter searches the complete catalog; all supplied filters intersect. Most data is illustrative; the Vinyl waterfall cites RIAA reports. Empty matches mean no example satisfies every filter; remove a filter to broaden the search.

NameTypeReqDescription
chart_typestring–Filter examples by chart type
example_idstring–Retrieve an exact ID from an earlier example result. Intersects any other supplied filters.
featuresarray–Return examples teaching every selected feature. Annotations explain data; references mark fixed values or statistics; ranges encode start/end values; intervals show lower/upper bounds around scatter…
purposestring–Filter by the primary chart question. Distribution means categorical frequencies, not automatic histogram binning. Range means bounded values, time spans, or uncertainty.
NameTypeReqDescription
examplesarrayyes–

No examples provided.

get_preview_state ~64

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, and hidden from the model.

NameTypeReqDescription
previewIdstringyesOpaque 16-character chart-preview id

Structured output declared, but exposes no named fields.

No examples provided.

get_schema ~116

Use this before authoring an unfamiliar field instead of probing validate_chart for errors. Returns the JSON Schema for the whole Szum document, covering config, data, presentation, size, and output, with every referenced definition included. Pass chart_type to keep only that family's config variants; omitting it returns every family and is much larger. Generated value lists are summarized rather than enumerated; validate_chart remains the authority.

NameTypeReqDescription
chart_typestring–Keep only the config variants for this chart type. Pass it whenever the family is known.
NameTypeReqDescription
chartTypestring––
schemaobjectyes–
versionstringyes–

No examples provided.

list_chart_types ~30

Use this when choosing a chart family. Returns every current chart type with its shared and family-specific fields.

Input schema present but exposes no named parameters.

NameTypeReqDescription
chartTypesarrayyes–
shared–yes–

No examples provided.

list_chart_versions ~128

Use this when the user wants to see a saved chart's earlier publications, find one to read with get_chart_document, or pick one to restore with restore_chart_version. Returns versions newest first with who published each, from where and what changed; requires authentication.

NameTypeReqDescription
cursorstring–Opaque nextCursor from the previous page
idstringyesOpaque 32-character saved-chart id
limitinteger–Page size; defaults to 100 and has a maximum of 1000
namedboolean–List only versions that were given a name
NameTypeReqDescription
currentVersionNumber–yesNumber of the version the chart publishes now, or null for a chart that was never published
itemsarrayyes–
nextCursorstring|nullyesOpaque cursor for older versions, or null on the last page

No examples provided.

list_charts ~198

Use this when the user wants to find charts in their saved library. Returns paginated metadata and URLs, not chart documents; requires authentication. Draft-only editor charts have publishedAt null, hasDraft true, and sizeBytes 0 because sizeBytes measures only the stored published document, not draft storage.

NameTypeReqDescription
authorstring–An authorId from a listed chart, or "former" for charts whose author has left the workspace; omit to list every author
cursorstring–Opaque nextCursor from the previous page
limitinteger–Page size; defaults to 100 and has a maximum of 1000
qstring–Case-insensitive title substring search; trimmed and limited to 100 characters
sortstring–Sort by creation time (default), update time, or title A-Z
source––Filter by one or more chart sources; omit to list all
NameTypeReqDescription
itemsarrayyes–
nextCursorstring|nullyesOpaque cursor for the next page, or null on the last page
totalinteger–Exact match count, present for title searches or when explicitly requested
workspaceobjectyesWorkspace this connection saves and lists charts in

No examples provided.

list_themes ~44

Use this when choosing a visual theme for a chart. Returns every built-in theme with guidance on where each works best and, when signed in, the workspace's shared themes.

Input schema present but exposes no named parameters.

NameTypeReqDescription
themesarrayyes–
workspaceThemesarray–The signed-in workspace's shared themes. Pass a name as sharedTheme to render_chart, save_chart, or update_chart.

No examples provided.

rename_chart ~71

Use this when the user wants to change a saved chart's library title without changing its document, publication state, or public URLs; requires authentication.

NameTypeReqDescription
idstringyesOpaque 32-character saved-chart id
titlestringyesNew saved-chart title; trimmed and limited to 200 characters
NameTypeReqDescription
createdAtstringyesISO-8601 creation timestamp
documentUrlstringyesOwner-only chart-document endpoint
editUrlstringyes–
embedUrlstringyesInteractive-embed URL
idstringyesOpaque 32-character saved-chart id
imageUrlstringyesRendered-image URL
manageUrlstringyes–
publishedAtstring|nullyesISO-8601 publish timestamp, or null when public URLs are dark
sizeBytesintegeryesCompressed size of the stored published document, excluding drafts; 0 means no published document has been stored yet
sourcestringyesChart origin; an open set of string values
titlestringyesSaved chart title
updatedAtstringyesISO-8601 last-update timestamp
viewstringyes–

No examples provided.

render_chart ~382

Use this when the user wants to preview or generate a chart. Validate each generated or changed chart input once before rendering, saving, or updating. Do not revalidate unchanged input; a successful render preflights it for later saves or updates. Errors block; warnings require explicit user approval for the exact chart input. Rendering may add layout warnings to the semantic findings before an action proceeds. Suggestions do not block. A suggestedDocument is a complete, validated replacement. Review the proposed changes before using it; validate again only if you modify it. Stores a 1 hour preview and returns public image URLs. Authenticated previews use the account's render allowance, and each image produced from a returned URL is another render. Anonymous previews are complimentary; their images use the anonymous image allowance.

NameTypeReqDescription
acknowledgeWarningsboolean–Set true only after the user explicitly approves every warning returned for this exact request
requeststringyesComplete current ChartDocument JSON with version, config, and data, plus optional presentation, size, and output. Use the same document for validation, rendering, and saving; version must match confi…
sharedThemestring–Name of a shared theme from list_themes' workspaceThemes. The chart uses that theme and stays linked to it, so later edits to the theme reach the chart. When omitted and the document sets neither the…
NameTypeReqDescription
durableInput–yes–
expiresAtstringyes–
formatstringyes–
imageUrlstringyes–
mimeTypestringyes–
titlestringyes–
validationobjectyes–
viewstringyes–

No examples provided.

restore_chart_version ~120

Use this when the user wants a saved chart to go back to an earlier version from list_chart_versions. Publishes that version's document again as a new version, keeping the chart's id and URLs, so the version it replaces stays restorable. Refuses charts with unpublished editor changes; requires authentication.

NameTypeReqDescription
acceptLossesarray–Compatibility loss codes explicitly accepted by the user for restoring an older document
idstringyesOpaque 32-character saved-chart id
versionintegeryesVersion number from list_chart_versions
NameTypeReqDescription
createdAtstringyesISO-8601 creation timestamp
documentUrlstringyesOwner-only chart-document endpoint
editUrlstringyes–
embedUrlstringyesInteractive-embed URL
idstringyesOpaque 32-character saved-chart id
imageUrlstringyesRendered-image URL
manageUrlstringyes–
publishedAtstring|nullyesISO-8601 publish timestamp, or null when public URLs are dark
sizeBytesintegeryesCompressed size of the stored published document, excluding drafts; 0 means no published document has been stored yet
sourcestringyesChart origin; an open set of string values
titlestringyesSaved chart title
updatedAtstringyesISO-8601 last-update timestamp
versionNumberintegeryesNumber of the version the chart publishes now; list_chart_versions lists the earlier ones and restore_chart_version publishes one again
viewstringyes–

No examples provided.

save_chart ~421

Use this when the user wants to permanently save and publish a Szum chart document. Validate each generated or changed chart input once before rendering, saving, or updating. Do not revalidate unchanged input; a successful render preflights it for later saves or updates. Errors block; warnings require explicit user approval for the exact chart input. Rendering may add layout warnings to the semantic findings before an action proceeds. Suggestions do not block. A suggestedDocument is a complete, validated replacement. Review the proposed changes before using it; validate again only if you modify it. Supply one idempotencyKey per intended chart and reuse it for retries. Returns permanent public Image and Embed URLs plus Edit and Studio links; requires authentication and saved-chart storage.

NameTypeReqDescription
acceptLossesarray–Compatibility loss codes explicitly accepted by the user for this save
acknowledgeWarningsboolean–Set true only after the user explicitly approves every warning returned for this exact document
documentstringyesComplete current ChartDocument JSON with version, config, and data, plus optional presentation, size, and output. Use the same document for validation, rendering, and saving; version must match confi…
idempotencyKeystring–Stable retry key of at most 255 characters; reuse only for the exact same document
sharedThemestring–Name of a shared theme from list_themes' workspaceThemes. The chart uses that theme and stays linked to it, so later edits to the theme reach the chart. When omitted and the document sets neither the…
NameTypeReqDescription
editUrlstringyes–
embedUrlstringyes–
formatstringyes–
idstringyesOpaque 32-character saved-chart id
imageUrlstringyes–
manageUrlstringyes–
mimeTypestringyes–
titlestringyes–
validationobjectyes–
versionNumberintegeryesNumber of the version the chart publishes now; list_chart_versions lists the earlier ones and restore_chart_version publishes one again
viewstringyes–
workspaceobjectyesWorkspace this connection saves and lists charts in

No examples provided.

update_chart ~438

Use this when the user wants to replace and publish a saved chart's document while keeping its id and URLs. Validate each generated or changed chart input once before rendering, saving, or updating. Do not revalidate unchanged input; a successful render preflights it for later saves or updates. Errors block; warnings require explicit user approval for the exact chart input. Rendering may add layout warnings to the semantic findings before an action proceeds. Suggestions do not block. A suggestedDocument is a complete, validated replacement. Review the proposed changes before using it; validate again only if you modify it. Refuses charts with unpublished editor changes; requires authentication and saved-chart storage.

NameTypeReqDescription
acceptLossesarray–Compatibility loss codes explicitly accepted by the user for this update
acknowledgeWarningsboolean–Set true only after the user explicitly approves every warning returned for this exact document
documentstringyesComplete current ChartDocument JSON with version, config, and data, plus optional presentation, size, and output. Use the same document for validation, rendering, and saving; version must match confi…
idstringyesOpaque 32-character saved-chart id
sharedTheme––Name of a shared theme from list_themes' workspaceThemes. The chart uses that theme and stays linked to it, so later edits to the theme reach the chart. When omitted, the chart keeps its current link…
titlestring–Library title; omit to keep a renamed title, while a title that still follows the document follows the new one; an empty title follows the document
NameTypeReqDescription
createdAtstringyesISO-8601 creation timestamp
documentUrlstringyesOwner-only chart-document endpoint
editUrlstringyes–
embedUrlstringyesInteractive-embed URL
idstringyesOpaque 32-character saved-chart id
imageUrlstringyesRendered-image URL
manageUrlstringyes–
publishedAtstring|nullyesISO-8601 publish timestamp, or null when public URLs are dark
sizeBytesintegeryesCompressed size of the stored published document, excluding drafts; 0 means no published document has been stored yet
sourcestringyesChart origin; an open set of string values
titlestringyesSaved chart title
updatedAtstringyesISO-8601 last-update timestamp
validationobjectyes–
versionNumberintegeryesNumber of the version the chart publishes now; list_chart_versions lists the earlier ones and restore_chart_version publishes one again
viewstringyes–

No examples provided.

validate_chart ~259

Use this when a chart request or document will be rendered, saved, or updated. Validate each generated or changed chart input once before rendering, saving, or updating. Do not revalidate unchanged input; a successful render preflights it for later saves or updates. Errors block; warnings require explicit user approval for the exact chart input. Rendering may add layout warnings to the semantic findings before an action proceeds. Suggestions do not block. A suggestedDocument is a complete, validated replacement. Review the proposed changes before using it; validate again only if you modify it. Read-only, free, and fast.

NameTypeReqDescription
chartstringyesComplete current ChartDocument JSON with version, config, and data, plus optional presentation, size, and output. Use the same document for validation, rendering, and saving; version must match confi…
NameTypeReqDescription
compatibility–––
diagnosticsarrayyes–
suggestedDocumentobject–Complete current ChartDocument. get_schema returns its JSON Schema.
validbooleanyes–

No examples provided.

Install

How do I install the Charts by Szum MCP server?

Charts by Szum is a hosted endpoint at https://szum.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · szum.io

# add to Claude Code
claude mcp add --transport http io-szum-charts 'https://szum.io/mcp'
Common questions

What is the Charts by Szum MCP server?

Charts by Szum is an MCP server listed in the public MCP registry as io.szum/charts. Create, inspect, manage, and render charts and data visualizations as SVG/PNG or interactive embeds. This page covers its hosted endpoint (https://szum.io/mcp).

Is the Charts by Szum MCP server safe to use?

Charts by Szum scores 81 out of 100 on VerifyMCP. 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 Charts by Szum MCP server expose?

Charts by Szum exposes 16 tools: render_chart, save_chart, list_charts, get_chart, get_chart_document, and 11 more. Their descriptions and schemas cost roughly 2,671 tokens of context every time the server is loaded.

Does the Charts by Szum MCP server require authentication?

No. We connected to Charts by Szum without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Charts by Szum MCP server still maintained?

Charts by Szum 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 did VerifyMCP test on the Charts by Szum MCP server?

VerifyMCP ran 14 checks on Charts by Szum, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.