drawspec
PYPI · DRAWSPEC
Validate and render declarative diagram specs to clean SVG or PNG; no coordinates needed.
Available components
Last scanned (6 hours ago)
Scores higher than 79% of PyPI servers
Category Design and Media
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 1 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to nuncaeslupus/drawspec). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1442 tokens (~288/item across 5 items; 5 tools + 0 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 (80% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 17 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 15 Oct 26 64
First indexed and scored.
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 17 Oct 2026 · Analysed pypi/drawspec@0.3.3
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 | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | nuncaeslupus/drawspec |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/nuncaeslupus/drawspec/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 3268159944 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:f183a198f108c1f812fb582fcc1dacfc718e7e5d31be03af14a863664f9e7d23 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 1 package
| Packages resolved | 1 |
|---|---|
| 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 →
get_example Get an example document of one kind ~150
Get the smallest valid document of one kind, as JSON ready to edit: the fastest way to the right field names. `kind` is one exact value from `list_kinds`, e.g. `flow`. Use it after `list_kinds` has settled the kind, and `get_schema` only for a field the example leaves out. Static and local: the document `drawspec example <kind>` prints, under 1 KB, identical every call; it passes `validate_document` as is. An unknown kind is an error result naming `list_kinds`.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | A diagram kind, exactly as `list_kinds` names it, e.g. `flow`. |
Structured output declared, but exposes no named fields.
No examples provided.
get_schema Get the JSON Schema for one kind ~155
Get the JSON Schema (draft 2020-12) for one kind's documents: every field it accepts, with types, limits and descriptions, plus only the shared `$defs` it refers to. `kind` is one value from `list_kinds`, e.g. `sequence`. Use it when `get_example` does not show a field you need. Local and deterministic: 3 to 13 KB per kind, cut from the ~150 KB published schema. Referential rules (unique ids, edges that land on real nodes) are beyond JSON Schema — `validate_document` checks those.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | A diagram kind, exactly as `list_kinds` names it, e.g. `flow`. |
Structured output declared, but exposes no named fields.
No examples provided.
list_kinds List the diagram kinds ~104
List the vocabulary: all 36 values `kind` may take, each with a one-line purpose. Call it first, before choosing a kind — several kinds are not box-and-arrow diagrams and are easy to miss — then `get_example` for a starting document. No arguments. Static and local: no I/O, about 4 KB, the same answer every call, in a fixed order that keeps related kinds (graphs, grids, shapes, charts) adjacent.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| kinds | array | yes | – |
No examples provided.
render_document Render a drawspec document to SVG, PNG or text ~582
Draw the document. Use it when it is ready to show; while still fixing errors, `validate_document` returns just the verdict. Returns one content block by `format`: `svg` (default) self-contained SVG text, safe inline in Markdown; `png` a base64 `image/png` block (needs the server's `drawspec[png]` extra, slowest); `text` plain text for a code block, only for kinds with a text form. `width`/`height` override the document's size; with `text`, `width` is cells per line and `height` and `theme` are ignored. Local, deterministic, writes nothing. Refusals are error results with JSON text `{"ok": false, "error": "DocumentError", "message": "...", "violations": [{"pointer": "/edges/0/to", "message": "..."}]}`: `error` is e.g. `DocumentError` or `FitError`, `pointer` is RFC 6901 (empty for the whole document), and `violations` is never empty.
| Name | Type | Req | Description |
|---|---|---|---|
| background | string | – | png only: the page the drawing is on (default light). |
| charset | string | – | text only: box-drawing characters, or ASCII only (default unicode). |
| document | object | yes | A drawspec document as a JSON object (not a string or a path), e.g. `{"version": 1, "kind": "flow", "nodes": [...], "edges": [...]}`. `list_kinds` names the 36 values `kind` may take, `get_example` r… |
| format | string | – | svg (default), png, or text: the diagram as plain text for a code block or a terminal, for the kinds files, tree, sequence, gantt, timeline, board, stack, rag, meter, flow, states, lanes. |
| height | number | – | Override the document's height (ignored with format `text`). |
| scale | number | – | png only: pixels per SVG unit (default 2). |
| theme | string | – | A bundled theme name (accent, blueprint, compartment, default, wheel) or a path to a `.toml` theme file on the server's disk, e.g. `blueprint`. Omit for `default`. |
| width | number | – | Override the document's width, e.g. `640`. With format `text`, the most terminal cells a line may take (default 80, or 100 for `lanes` and `sequence`). |
No output schema declared.
No examples provided.
validate_document Validate a drawspec document ~343
Check whether `render_document` would refuse this document, and exactly where. It renders with the same `theme` and discards the drawing, so it passes only what draws; every violation comes back at once, so one pass is one edit. Call it while writing or editing; skip it when about to render anyway, since `render_document` refuses in the same shape. Local, deterministic, milliseconds. Refusals are error results with JSON text `{"ok": false, "error": "DocumentError", "message": "...", "violations": [{"pointer": "/edges/0/to", "message": "..."}]}`: `error` is e.g. `DocumentError` or `FitError`, `pointer` is RFC 6901 (empty for the whole document), and `violations` is never empty.
| Name | Type | Req | Description |
|---|---|---|---|
| document | object | yes | A drawspec document as a JSON object (not a string or a path), e.g. `{"version": 1, "kind": "flow", "nodes": [...], "edges": [...]}`. `list_kinds` names the 36 values `kind` may take, `get_example` r… |
| theme | string | – | A bundled theme name (accent, blueprint, compartment, default, wheel) or a path to a `.toml` theme file on the server's disk, e.g. `blueprint`. Omit for `default`. |
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | – |
| message | string | yes | – |
| ok | boolean | yes | – |
No examples provided.
How do I install the drawspec MCP server?
drawspec runs locally as a PyPI package, launched with uvx drawspec. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · drawspec
claude mcp add nuncaeslupus-drawspec -- uvx drawspec
What is the drawspec MCP server?
drawspec is an MCP server listed in the public MCP registry as io.github.nuncaeslupus/drawspec. Validate and render declarative diagram specs to clean SVG or PNG; no coordinates needed. This page covers its PyPI package (drawspec).
Is the drawspec MCP server safe to use?
drawspec scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. 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 drawspec MCP server expose?
drawspec exposes 5 tools: list_kinds, get_example, get_schema, validate_document, render_document. Their descriptions and schemas cost roughly 1,334 tokens of context every time the server is loaded.
Is the drawspec MCP server still maintained?
drawspec is still listed as active in the MCP registry. We last reached this channel on 17 October 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 drawspec MCP server under?
drawspec declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.