# noddle draw (mcpb · noddle-draw.mcpb)

Read, create and edit open-source noddle draw diagram boards, browse versions and comment.

- Trust score: 51/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-24

## Components

- mcpb · `noddle-draw.mcpb`: 51/100 (this document), [markdown](https://verifymcp.io/servers/dev-noddle-draw/noddle-draw.md), [page](https://verifymcp.io/servers/dev-noddle-draw/noddle-draw)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/noddle-dev/noddle-draw/releases/download/mcpb-v1.0.0/noddle-draw.mcpb`
- Version: `1.0.0`
- Transport: `stdio`
- SHA-256: `12d4b05300b53cee0e75bae30fbd7e23df60f277aa752665b93e2d2947fc9147`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-24.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 20 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1212 tokens (~134/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 56% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**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.

## Install

### How do I install the noddle draw MCP server?

noddle draw ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 12d4b05300b53cee0e75bae30fbd7e23df60f277aa752665b93e2d2947fc9147; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/noddle-dev/noddle-draw/releases/download/mcpb-v1.0.0/noddle-draw.mcpb`
- SHA-256: `12d4b05300b53cee0e75bae30fbd7e23df60f277aa752665b93e2d2947fc9147`

### Verify on macOS / Linux

```bash
echo "12d4b05300b53cee0e75bae30fbd7e23df60f277aa752665b93e2d2947fc9147  noddle-draw.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\noddle-draw.mcpb).Hash -eq "12d4b05300b53cee0e75bae30fbd7e23df60f277aa752665b93e2d2947fc9147"
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-23 (score 51, +1)

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

### 2026-10-21 (score 50, +1)

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

### 2026-10-19 (score 49, +1)

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

### 2026-10-17 (score 48, +1)

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

### 2026-10-15 (score 47, +1)

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

### 2026-10-14 (score 46, +5)

- [functional improvement] Stability: unverified → 0.37

### 2026-10-03 (score 41)

First indexed and scored.

## MCP tools (9)

### `get_board` (~103 tokens)

Get board

Fetch one board by id or URL: name, url, my_role (editor|viewer), updated_at, page summary and the editable diagram JSON. Optionally restrict to one page.

Input parameters:

- `doc_id` (string, required): Board id (12 hex chars, the {id} in /d/{id}) or the full board URL.
- `include_svg` (boolean): Also return the flattened preview SVG (large).
- `page_id` (string): Return only this page.

Output parameters:

- `diagram` (object|null): Editable diagram JSON (pass-through).
- `id` (string)
- `link_policy` (string|null)
- `my_role` (string|null): viewer ⇒ the link is view-only; writes will fail.
- `name` (string|null)
- `pages` (array)
- `svg` (string|null)
- `updated_at` (number|null): Pass to update_board.expected_updated_at.
- `url` (string)

### `create_board` (~205 tokens)

Create board

Create a NEW board, optionally with diagram JSON. Returns the new id + url. The board is anonymous: anyone with the url can open and edit it.

Input parameters:

- `diagram` (object): noddle diagram JSON, passed through as-is: {pages:[{id,name,nodes,edges}]} (or legacy {nodes,edges}). Node required: id, kind (rect|rounded|ellipse|diamond|cylinder|text|freedraw|… — the editor catal…
- `name` (string, required)

Output parameters:

- `id` (string)
- `name` (string|null)
- `updated_at` (number|null)
- `url` (string)

### `update_board` (~263 tokens)

Replace board diagram

Replace a board's WHOLE diagram (full-state, like the live protocol; a version snapshot is kept). Fetch with get_board, modify, send everything back. Pass expected_updated_at to fail instead of overwriting a collaborator's newer edit.

Input parameters:

- `diagram` (object, required): noddle diagram JSON, passed through as-is: {pages:[{id,name,nodes,edges}]} (or legacy {nodes,edges}). Node required: id, kind (rect|rounded|ellipse|diamond|cylinder|text|freedraw|… — the editor catal…
- `doc_id` (string, required): Board id (12 hex chars, the {id} in /d/{id}) or the full board URL.
- `expected_updated_at` (number): updated_at from get_board (optimistic concurrency).

Output parameters:

- `id` (string)
- `name` (string|null)
- `updated_at` (number|null)
- `url` (string)

### `rename_board` (~56 tokens)

Rename board

Rename a board (fails on a view-only link).

Input parameters:

- `doc_id` (string, required): Board id (12 hex chars, the {id} in /d/{id}) or the full board URL.
- `name` (string, required)

Output parameters:

- `id` (string)
- `name` (string|null)
- `updated_at` (number|null)
- `url` (string)

### `list_versions` (~56 tokens)

List board versions

Version-history snapshots of a board, newest first (id, created_at, author_name).

Input parameters:

- `doc_id` (string, required): Board id (12 hex chars, the {id} in /d/{id}) or the full board URL.

Output parameters:

- `versions` (array)

### `get_version` (~71 tokens)

Get board version

One snapshot's diagram JSON. To restore it, send that diagram to update_board.

Input parameters:

- `doc_id` (string, required): Board id (12 hex chars, the {id} in /d/{id}) or the full board URL.
- `include_svg` (boolean)
- `version_id` (string, required)

Output parameters:

- `author_name` (string|null)
- `created_at` (number|null)
- `diagram` (object|null): Editable diagram JSON (pass-through).
- `id` (string|null)
- `svg` (string|null)

### `list_comments` (~55 tokens)

List comments

A board's comment threads (roots carry the anchor; replies are one level deep).

Input parameters:

- `doc_id` (string, required): Board id (12 hex chars, the {id} in /d/{id}) or the full board URL.

Output parameters:

- `comments` (array)

### `add_comment` (~170 tokens)

Add comment

Comment on a board, signed with NODDLE_AGENT_NAME. Anchor to ONE of: node_id, edge_id, a reply to a thread root (parent_id), or a canvas point (x, y; default 100,100). Works on view-only links too. Returns the full updated thread list.

Input parameters:

- `body` (string, required)
- `doc_id` (string, required): Board id (12 hex chars, the {id} in /d/{id}) or the full board URL.
- `edge_id` (string)
- `node_id` (string)
- `page_id` (string): Page the pin lives on (multi-page boards).
- `parent_id` (string): Root comment id to reply to.
- `x` (number)
- `y` (number)

Output parameters:

- `comments` (array)

### `generate_diagram` (~104 tokens)

Generate diagram from text

Turn prose or Mermaid into editable noddle diagram JSON via the server's AI (your own key from NODDLE_AI_PROVIDER/NODDLE_AI_KEY, else the instance's shared pool if it has one). Does NOT save anything — pass the result to create_board or update_board. The text leaves noddle for the AI provider: never include PII, credentials or account numbers.

Input parameters:

- `format` (string)
- `text` (string, required)

Output parameters:

- `diagram` (object)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/dev-noddle-draw/noddle-draw#diagnostics

## Score history

- 2026-10-24: 51
- 2026-10-23: 51
- 2026-10-22: 50
- 2026-10-21: 50
- 2026-10-20: 49
- 2026-10-19: 49
- 2026-10-18: 48
- 2026-10-17: 48
- 2026-10-16: 47
- 2026-10-15: 47
- 2026-10-14: 46
- 2026-10-13: 41
- 2026-10-12: 41
- 2026-10-10: 41
- 2026-10-09: 41
- 2026-10-06: 41
- 2026-10-04: 41
- 2026-10-03: 41

## Common questions

### What is the noddle draw MCP server?

noddle draw is an MCP server listed in the public MCP registry as dev.noddle/draw. Read, create and edit open-source noddle draw diagram boards, browse versions and comment. This page covers its MCPB bundle (https://github.com/noddle-dev/noddle-draw/releases/download/mcpb-v1.0.0/noddle-draw.mcpb).

### Is the noddle draw MCP server safe to use?

noddle draw scores 51 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 noddle draw MCP server expose?

noddle draw exposes 9 tools: get_board, create_board, update_board, rename_board, list_versions, and 4 more. Their descriptions and schemas cost roughly 1,083 tokens of context every time the server is loaded.

### What licence is the noddle draw MCP server under?

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

## Links

- Repository: https://github.com/noddle-dev/noddle-draw
- Website: https://draw.noddle.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-noddle-draw/noddle-draw.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-noddle-draw/noddle-draw.json
- HTML version of this page: https://verifymcp.io/servers/dev-noddle-draw/noddle-draw