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.

Blueprint Chart

NPM · @BLUEPRINT-CHART/MCP · SCANNED SEP 13

The open chart format an LLM writes and the browser renders — to interactive, accessible SVG.

0 this week 95 Trust /100
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 Security98
  • 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
  • 72 of 203 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to blueprint-chart/mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 14 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability88
  • 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
  • Tool/resource definitions use about 3108 tokens (~45/item across 68 items; 11 tools + 57 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 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
  • 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
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 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
Install

How do I install the Blueprint Chart MCP server?

Blueprint Chart runs locally as an npm package, launched with npx -y @blueprint-chart/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 · @blueprint-chart/mcp

# add to Claude Code
claude mcp add blueprint-chart-mcp -- npx -y @blueprint-chart/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "blueprint-chart-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@blueprint-chart/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "blueprint-chart-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@blueprint-chart/mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add blueprint-chart-mcp -- npx -y @blueprint-chart/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "blueprint-chart-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@blueprint-chart/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add blueprint-chart-mcp --command npx --arg -y --arg @blueprint-chart/mcp
# ~/.hermes/config.yaml
mcp_servers:
  blueprint-chart-mcp:
    command: "npx"
    args: ["-y", "@blueprint-chart/mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "blueprint-chart-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@blueprint-chart/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add blueprint-chart-mcp -t stdio -c npx -a -y @blueprint-chart/mcp
// mcp.json
{
  "mcpServers": {
    "blueprint-chart-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@blueprint-chart/mcp"
      ]
    }
  }
}
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.

  • 13 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 12 Sept 26 +1
    • Security disclosure: fail → unverified functional
  • 10 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 9 Sept 26 +1
    • Stability: 0.97 → pass security
  • 8 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 7 Sept 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.

  • 6 Sept 26 0
    • Security disclosure: fail → unverified functional
  • 5 Sept 26 +1

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

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 13 Sept 2026 · Analysed npm/@blueprint-chart/mcp@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo blueprint-chart/mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/blueprint-chart/mcp/.github/workflows/release.yml@refs/heads/main
Rekor log index 2639705115
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:eeb118b4a566fe0958fb2cfe3ddeb5d257026065d7277ddc110f4c923d61dba8a484bb0ddc7bc888a4be854a6ef5c848b95f8a6e48cb0453cb8d3ff81

Background: How many MCP packages publish verified provenance →

Dependencies 203 packages
Packages resolved 203
Deprecated 1
Stale 72
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 11 exposed · ~1,336 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
describe_chart_type ~115

Return everything an LLM needs to write a .bpc for a given chart type — typically your second call, after recommend_chart_type. Input: { chartType: "bar-horizontal" } (or any canonical/alias name). Returns summary, when-to-use, when-NOT-to-use, full property list with enum choices, data-shape example, and a pointer to a canonical sample.

NameTypeReqDescription
chartTypestringyesA chart type or alias to describe, e.g. "bar-horizontal" or "line".
NameTypeReqDescription
aliasesarrayyesAccepted alias names.
dataShapeobjectyesThe data shape this chart type expects.
directivesarrayyesSupported directives.
docsUrlstringPublic docs URL.
exampleSlugstringId of a canonical sample for this type.
namestringyesCanonical chart-type identifier.
propertiesarrayyesSupported chart properties.
summarystringyesOne-line description.
whenNotToUsearrayyesSituations to avoid it.
whenToUsearrayyesSituations this chart type fits.

No examples provided.

export_chart ~181

Turn a validated .bpc source into shareable URLs plus an inline visual preview of what was published. Returns { copyUrl, embedUrl, urls?, frame } and a PNG preview image block so you can confirm the chart looks right before sharing. copyUrl opens an editable copy in the editor; embedUrl is a read-only iframe target; urls.{png,svg,bpc} (when MCP_PUBLIC_URL is set) are stateless rendered-image/source links. Set modelVisible:false to drop the inline preview from the response entirely, spending no image tokens. Requires BLUEPRINT_CHART_EDITOR_URL; preview failures never block the export.

NameTypeReqDescription
modelVisiblebooleanWhen false, the preview image is omitted from the response so it costs no image tokens.
sourcestringyesThe .bpc chart source to validate and publish to shareable URLs.
NameTypeReqDescription
copyUrlstringyesEditor URL that opens an editable copy of the chart.
embedUrlstringyesRead-only iframe-embeddable URL.
frameobjectyesFrame metadata extracted from the chart.
previewOmittedbooleanSet when the preview render failed.
urlsobjectStateless hosted render URLs (only when MCP_PUBLIC_URL is set).

No examples provided.

get_example ~89

Return a canonical .bpc example. Pass { name } for a specific sample id, { chartType } for the first sample of that type, or no args for a starter sample.

NameTypeReqDescription
chartTypestringReturn the first canonical sample for this chart type (or alias).
namestringReturn a specific sample by its id, e.g. "co2-emissions".
NameTypeReqDescription
chartTypestringyesChart type of the sample.
dslstringyesThe full .bpc source of the sample.
idstringyesSample id.
titlestringyesSample title.

No examples provided.

get_grammar ~95

Return the .bpc DSL grammar as markdown. Pass { section: "chart" | "data" | "properties" | "scenes" | "annotations" } for a focused subset, or no args for the full grammar.

NameTypeReqDescription
sectionstringLimit to one grammar section: "chart", "properties", "scenes", or "annotations". Omit (or "all") for the full grammar.
NameTypeReqDescription
sectionstringyesThe grammar section returned.
textstringyesThe grammar reference as markdown.

No examples provided.

inspect_dsl ~73

Parse a .bpc source and return a structured summary: chartType, scenes, data (rowCount, entryCount, labels, seriesNames, multiSeries), annotation/colorize/highlight/area-fill presence flags, series count.

NameTypeReqDescription
sourcestringyesThe .bpc chart source to parse and summarize.
NameTypeReqDescription
chartTypestringyesDeclared chart type.
dataobjectyesSummary of the data block.
hasAnnotationsbooleanyesWhether any annotation/range/note is present.
hasAreaFillsbooleanyesWhether any area-fill is present.
hasColorizesbooleanyesWhether any non-highlight colorize is present.
hasHighlightsbooleanyesWhether any highlight is present.
scenesarrayyesPer-scene summaries, base chart first (always at least one).
seriesCountintegeryesNumber of series.

No examples provided.

list_chart_types ~40

Reference list of every chart type the renderer supports, with aliases and one-line summaries. To choose a type for a dataset, call recommend_chart_type instead.

Input schema present but exposes no named parameters.

NameTypeReqDescription
chartTypesarrayyesEvery renderable chart type.

No examples provided.

list_palettes ~32

List every named colour palette with its label and hex colours, for use in `colorPalette = "<name>"`.

Input schema present but exposes no named parameters.

NameTypeReqDescription
palettesarrayyesEvery named palette.

No examples provided.

recommend_chart_type ~145

Start here before writing any .bpc. Takes column types, row count, and the user's goal (a prose sentence — it determines the chart family: comparison/ranking/part-to-whole/composition-over-time/trend/range). Returns ranked chart-type recommendations plus guidance.

NameTypeReqDescription
columnTypesarrayyesThe type of each data column, in order: "string", "number", or "date".
goalstringOptional prose sentence describing what the chart should show. Determines the chart family (comparison / ranking / part-to-whole / composition-over-time / trend / range).
rowCountintegeryesNumber of data rows in the dataset.
NameTypeReqDescription
guidancestringProse next-step guidance for the top recommendation.
recommendationsarrayyesRanked chart-type recommendations, best first.

No examples provided.

render ~402

Render a .bpc source to SVG (default), PNG, or HTML. With format:"png" the chart comes back as an inline IMAGE you and the user can both see — render, look at the result, fix issues, re-render. Always returns structured frame metadata. When MCP_PUBLIC_URL is set the response includes stateless `urls` ({png,svg,bpc}). Set modelVisible:false to drop the inline image from the response entirely, spending no image tokens (reach the image via `urls.png` or `save`). Pass `save:<path>` to write the output into MCP_FS_WRITE_DIR instead of returning it inline. Width/height are capped at 1600; PNGs are rasterized at 2× for retina sharpness.

NameTypeReqDescription
formatstringOutput format. "svg" (default) and "html" return text; "png" returns an inline image you and the user can both see.
heightintegerOutput height in pixels (max 1600).
modelVisiblebooleanWhen false, the inline PNG is omitted from the response so it costs no image tokens; use it for bulk renders, with `urls.png` or `save` to reach the image.
savestringOptional output path, always resolved inside MCP_FS_WRITE_DIR (relative paths are joined to it; absolute paths are re-anchored under it). When set, the output is written to disk and omitted from the…
sceneintegerScene number to render, matching the editor player: scene 1 is the base chart and each `scene` block that follows is the next number. Omit for the base chart.
sourcestringyesThe .bpc chart source to render.
widthintegerOutput width in pixels (max 1600). PNGs are rasterized at 2x for retina sharpness.
NameTypeReqDescription
frameobjectyesFrame metadata extracted from the chart.
htmlstringHTML markup, when format is "html" and `save` was not used.
mimeTypestringyesMIME type of the rendered output.
savedTostringAbsolute path the output was written to, when `save` was used.
svgstringSVG markup, when format is "svg" and `save` was not used.
urlsobjectStateless hosted render URLs (only when MCP_PUBLIC_URL is set).
urlsOmittedstringSet when URLs were omitted because the source exceeded the URL cap.

No examples provided.

search_examples ~99

Find canonical .bpc examples by topic keywords and/or chart type. Returns ranked pointers { id, title, description, chartType } — call get_example with an id to fetch the full DSL.

NameTypeReqDescription
chartTypestringRestrict results to this chart type (or alias).
limitintegerMaximum number of results to return (max 20).
querystringTopic keywords to match against sample titles and descriptions.
NameTypeReqDescription
resultsarrayyesRanked sample pointers, best first.

No examples provided.

validate_dsl ~65

Parse and semantically validate a .bpc source. Returns { valid, errors[], warnings[] }. Errors include unknown chart types, unknown properties, and empty data blocks with nearest-neighbour suggestions.

NameTypeReqDescription
sourcestringyesThe .bpc chart source to parse and validate.
NameTypeReqDescription
errorsarrayyesFatal structural and value-level errors.
validbooleanyesTrue when the source parses and passes semantic validation.
warningsarrayyesNon-fatal advisories.

No examples provided.

Common questions

What is the Blueprint Chart MCP server?

Blueprint Chart is an MCP server listed in the public MCP registry as io.github.blueprint-chart/mcp. The open chart format an LLM writes and the browser renders, to interactive, accessible SVG. This page covers its npm package (@blueprint-chart/mcp).

Is the Blueprint Chart MCP server safe to use?

Blueprint Chart scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 13 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Blueprint Chart MCP server expose?

Blueprint Chart exposes 11 tools: validate_dsl, inspect_dsl, recommend_chart_type, render, list_chart_types, and 6 more. Their descriptions and schemas cost roughly 1,336 tokens of context every time the server is loaded.

Is the Blueprint Chart MCP server still maintained?

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

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