io.szum/charts

Est-ce que io.szum/charts est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.szum/charts » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 14 outils

• delete_chart≈ 208 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    Opaque 32-character saved-chart id

  Exemple d'appel

  {"name": "delete_chart", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"deleted": true}}

• get_chart≈ 507 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    Opaque 32-character saved-chart id

  Exemple d'appel

  {"name": "get_chart", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "view": "texte", "title": "texte", "source": "texte", "editUrl": "texte", "embedUrl": "texte", "imageUrl": "texte", "createdAt": "texte", "manageUrl": "texte", "sizeBytes": 1, "updatedAt": "texte", "documentUrl": "texte"}}

• get_chart_document≈ 199 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    Opaque 32-character saved-chart id

  Exemple d'appel

  {"name": "get_chart_document", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_examples≈ 774 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • purpose · string · optionnel · comparison | change | trend | composition | relationship | distribution | range
    Filter by the primary chart question. Distribution means categorical frequencies, not automatic histogram binning. Range means bounded values, time spans, or uncertainty.
  • features · array · optionnel
    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 observations.
  • chart_type · string · optionnel · column | bar | line | area | scatter | pie | waterfall
    Filter examples by chart type
  • example_id · string · optionnel
    Retrieve an exact ID from an earlier example result. Intersects any other supplied filters.

  Exemple d'appel

  {"name": "get_examples", "arguments": {"purpose": "comparison", "features": [], "chart_type": "column", "example_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"examples": []}}

• get_preview_state≈ 978 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • previewId · string · requis
    Opaque 16-character chart-preview id

  Exemple d'appel

  {"name": "get_preview_state", "arguments": {"previewId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"chart": {}, "status": "saved"}}

• get_schema≈ 346 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • chart_type · string · optionnel · column | bar | line | area | scatter | pie | waterfall
    Keep only the config variants for this chart type. Pass it whenever the family is known.

  Exemple d'appel

  {"name": "get_schema", "arguments": {"chart_type": "column"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"schema": {}, "version": "texte", "chartType": "column"}}

• list_chart_types≈ 261 tokens

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

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_chart_types", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"shared": "texte", "chartTypes": []}}

• list_charts≈ 814 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

  • q · string · optionnel
    Case-insensitive title substring search; trimmed and limited to 100 characters
  • sort · string · optionnel · updated | created | title
    Sort by creation time (default), update time, or title A-Z
  • limit · integer · optionnel
    Page size; defaults to 100 and has a maximum of 1000
  • cursor · string · optionnel
    Opaque nextCursor from the previous page
  • source · ? · optionnel
    Filter by one or more chart sources; omit to list all

  Exemple d'appel

  {"name": "list_charts", "arguments": {"q": "texte", "sort": "updated", "limit": 1, "cursor": "texte", "source": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"items": [], "total": 1, "nextCursor": "texte"}}

• list_themes≈ 196 tokens

  Use this when choosing a visual theme for a chart. Returns every available theme and guidance on where each works best.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_themes", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"themes": []}}

• rename_chart≈ 525 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • id · string · requis
    Opaque 32-character saved-chart id
  • title · string · requis
    New saved-chart title; trimmed and limited to 200 characters

  Exemple d'appel

  {"name": "rename_chart", "arguments": {"id": "texte", "title": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "view": "texte", "title": "texte", "source": "texte", "editUrl": "texte", "embedUrl": "texte", "imageUrl": "texte", "createdAt": "texte", "manageUrl": "texte", "sizeBytes": 1, "updatedAt": "texte", "documentUrl": "texte"}}

• render_chart≈ 2944 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • request · string · requis
    Complete 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 config.version. Semantic field roles must match row keys. Chronological annual values use YYYY strings on an explicit UTC scale. Column and bar charts with long, wide, or count values, and all area charts, use linear value scales. Their inferred domains include zero, while an explicit domain excluding zero produces a warning. Base-10 log roles and explicit log domains require positive finite values; use line, scatter, or ranged columns and bars.
  • acknowledgeWarnings · boolean · optionnel
    Set true only after the user explicitly approves every warning returned for this exact request

  Exemple d'appel

  {"name": "render_chart", "arguments": {"request": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"view": "texte", "title": "texte", "format": "svg", "imageUrl": "texte", "mimeType": "image/svg+xml", "expiresAt": "texte", "validation": {}, "durableInput": "texte"}}

• save_chart≈ 2926 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • document · string · requis
    Complete 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 config.version. Semantic field roles must match row keys. Chronological annual values use YYYY strings on an explicit UTC scale. Column and bar charts with long, wide, or count values, and all area charts, use linear value scales. Their inferred domains include zero, while an explicit domain excluding zero produces a warning. Base-10 log roles and explicit log domains require positive finite values; use line, scatter, or ranged columns and bars.
  • acceptLosses · array · optionnel
    Compatibility loss codes explicitly accepted by the user for this save
  • idempotencyKey · string · optionnel
    Stable retry key of at most 255 characters; reuse only for the exact same document
  • acknowledgeWarnings · boolean · optionnel
    Set true only after the user explicitly approves every warning returned for this exact document

  Exemple d'appel

  {"name": "save_chart", "arguments": {"document": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "view": "texte", "title": "texte", "format": "svg", "editUrl": "texte", "embedUrl": "texte", "imageUrl": "texte", "mimeType": "image/svg+xml", "manageUrl": "texte", "validation": {}}}

• update_chart≈ 3075 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • id · string · requis
    Opaque 32-character saved-chart id
  • document · string · requis
    Complete 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 config.version. Semantic field roles must match row keys. Chronological annual values use YYYY strings on an explicit UTC scale. Column and bar charts with long, wide, or count values, and all area charts, use linear value scales. Their inferred domains include zero, while an explicit domain excluding zero produces a warning. Base-10 log roles and explicit log domains require positive finite values; use line, scatter, or ranged columns and bars.
  • acceptLosses · array · optionnel
    Compatibility loss codes explicitly accepted by the user for this update
  • acknowledgeWarnings · boolean · optionnel
    Set true only after the user explicitly approves every warning returned for this exact document

  Exemple d'appel

  {"name": "update_chart", "arguments": {"id": "texte", "document": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "view": "texte", "title": "texte", "source": "texte", "editUrl": "texte", "embedUrl": "texte", "imageUrl": "texte", "createdAt": "texte", "manageUrl": "texte", "sizeBytes": 1, "updatedAt": "texte", "validation": {}}}

• validate_chart≈ 2605 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • chart · string · requis
    Complete 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 config.version. Semantic field roles must match row keys. Chronological annual values use YYYY strings on an explicit UTC scale. Column and bar charts with long, wide, or count values, and all area charts, use linear value scales. Their inferred domains include zero, while an explicit domain excluding zero produces a warning. Base-10 log roles and explicit log domains require positive finite values; use line, scatter, or ranged columns and bars.

  Exemple d'appel

  {"name": "validate_chart", "arguments": {"chart": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"valid": true, "diagnostics": [], "compatibility": "texte", "suggestedDocument": {}}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://szum.io/mcp