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.

Doodleworks MCP

NPM · DOODLEWORKS-MCP · SCANNED SEP 20

Hand-drawn explainer illustrations in your AI host, via an MCP App with an interactive viewer.

Available components

+2 this week 94 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
  • 55 of 165 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to SalZaki/doodleworks-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 81 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
  • 89% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 894 tokens (~81/item across 11 items; 3 tools + 8 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 75% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
Install

How do I install the Doodleworks MCP server?

Doodleworks MCP runs locally as an npm package, launched with npx -y doodleworks-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 · doodleworks-mcp

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

  • 20 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.

  • 18 Sept 26 −2
    • Security disclosure: unverified → pass functional
    • Stability: pass → 0.80 functional
  • 17 Sept 26 0
    • Stability: 0.97 → pass security
    • Security disclosure: pass → unverified functional
  • 16 Sept 26 +1

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

  • 15 Sept 26 +2
    • CVE-2026-82562 no longer affects this package security
    • CVE-2026-82417 no longer affects this package security
    • Known CVEs: fail → pass security
    • Security disclosure: unverified → pass functional
  • 14 Sept 26 0
    • Security disclosure: pass → unverified functional
  • 13 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.

  • 12 Sept 26 +1
    • Security disclosure: unverified → pass 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 20 Sept 2026 · Analysed npm/doodleworks-mcp@1.1.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 SalZaki/doodleworks-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/SalZaki/doodleworks-mcp/.github/workflows/release.yml@refs/heads/main
Rekor log index 2026772273
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:d40091fc562fece7dc6d1a05d4a493568141c73538eaa059392e1ce8c7018a7c45ed717a1f089830591f55b4ef574a782dcc4b52feb379989976a852e

Background: How many MCP packages publish verified provenance →

Dependencies 165 packages
Packages resolved 165
Deprecated 1
Stale 54
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~657 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
create_illustrations ~305

Render a set of single-idea, hand-drawn Tinku illustrations (each 16:9; an optional 21:9 hero) and open an interactive viewer. Supply one entry per illustration; each `prompt` is a contraption composition + Tinku's action + its exact English annotations — the server applies the Tinku character, the conceptual engine, and the house style. Use this when the user wants hand-drawn illustrations for an article, post, or explainer.

NameTypeReqDescription
illustrationsarrayyesIllustrations in order (1-10); each is 16:9 by default. An optional 21:9 hero may go first.
qualitystringImage quality (OpenAI). Lower is faster & cheaper. Defaults to DOODLEWORKS_QUALITY env or 'low'.
resolutionstringSize tier (default 1k; 2k is heavier for inline display).
styleReferencestringOptional drawing-style reference for the whole set (style calibration only — the clean even line weight, the pure-white background, whitespace, restraint; NEVER the reference's character, layout, or…
titlestringA title for the set.

No output schema declared.

No examples provided.

get_illustration ~74

Return the rendered image for one illustration of a previously created set. The viewer calls this for each illustration after create_illustrations so a single tool result never carries the whole set.

NameTypeReqDescription
indexintegeryesZero-based illustration index.
setIdstringyesThe setId returned by create_illustrations.

No output schema declared.

No examples provided.

regenerate_illustration ~278

Re-render a single illustration with the same (or a tweaked) prompt and aspect. Image models are non-deterministic, so this yields a fresh take. Returns the new image in `_meta` for the viewer.

NameTypeReqDescription
archetypestring
aspectstring
indexintegerRequired with setId — zero-based illustration index to replace.
promptstringyesThe illustration composition + 'Required text only:' block (style is re-applied server-side).
qualitystringImage quality (OpenAI). Lower is faster & cheaper. Defaults to DOODLEWORKS_QUALITY env or 'low'.
resolutionstring
setIdstringIf present, also replace the cached image so a viewer reopen sees the regenerated illustration.
styleReferencestringOptional drawing-style reference for the whole set (style calibration only — the clean even line weight, the pure-white background, whitespace, restraint; NEVER the reference's character, layout, or…
titlestring

No output schema declared.

No examples provided.

Common questions

What is the Doodleworks MCP server?

Doodleworks MCP is listed in the public MCP registry as io.github.SalZaki/doodleworks-mcp. Hand-drawn explainer illustrations in your AI host, via an MCP App with an interactive viewer. This page covers its npm package (doodleworks-mcp).

Is the Doodleworks MCP server safe to use?

Doodleworks MCP scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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 Doodleworks MCP server expose?

Doodleworks MCP exposes 3 tools: create_illustrations, get_illustration, regenerate_illustration. Their descriptions and schemas cost roughly 657 tokens of context every time the server is loaded.

Is the Doodleworks MCP server still maintained?

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

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