sketch/design — System Design Interview Board
NPM · SYSDESIGN-BOARD
Hand-drawn whiteboard for system design mock interviews; your AI watches, asks and gives feedback.
Available components
Last scanned (11 hours ago)
Scores higher than 55% of npm servers
Category Testing and QA
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
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- 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 Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1322 tokens (~101/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 46% 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
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 14 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
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.
- 5 Nov 26 +7
- Stability: unverified → 0.50 ▲ functional
- 22 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 21 Oct 26 55
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 5 Nov 2026 · Analysed npm/sysdesign-board@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
annotate Pin a comment on the board ~86
Pin an interviewer comment bubble on the board, pointing at a component (by id or label) or at a position. Great for "what if this fails?" style probes.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | – | Element id or label, e.g. "Redis" or "Load Balancer" |
| text | string | yes | – |
| x | number | – | – |
| y | number | – | – |
No output schema declared.
No examples provided.
clear_annotations Remove interviewer comments ~26
Remove your pinned comments (all, or specific ids).
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | – | – |
No output schema declared.
No examples provided.
draw_on_board Draw on the board ~234
Add components, connections, sticky notes and zones in the same sketchy style (marked as drawn by the interviewer). Use sparingly — the candidate should drive. Component kinds: user (User), browser (Web App), mobile (Mobile App), dns (DNS), cdn (CDN), lb (Load Balancer), gateway (API Gateway), firewall (Rate Limiter), server (App Server), service (Service), worker (Worker), lambda (Function), cron (Scheduler), sql (SQL DB), nosql (NoSQL DB), cache (Cache), storage (Object Store), search (Search Index), warehouse (Data Warehouse), queue (Queue), stream (Event Stream), pubsub (Pub/Sub), notify (Notifications), auth (Auth), monitor (Monitoring), ml (ML Model), external (External API). Connections reference a component by its ref/label (new or existing) or id. Positions are optional (auto-laid out to the right of existing content).
| Name | Type | Req | Description |
|---|---|---|---|
| components | array | – | – |
| connections | array | – | – |
| notes | array | – | – |
| zones | array | – | – |
No output schema declared.
No examples provided.
end_interview End the interview with feedback ~94
Close the session and show a feedback card on the board. Scores are 1-5.
| Name | Type | Req | Description |
|---|---|---|---|
| improvements | array | yes | – |
| scores | object | yes | 1 = poor, 3 = meets bar, 5 = exceptional |
| signal | string | – | e.g. "Lean hire (senior)" |
| strengths | array | yes | – |
| summary | string | yes | 2-4 sentence overall assessment |
No output schema declared.
No examples provided.
get_board Read the board ~71
Structured description of the board: components (type, label, id, position, zone), connections (from -> to, label, dashed=async), zones, notes and text, freehand strokes, plus what changed since you last looked.
| Name | Type | Req | Description |
|---|---|---|---|
| include_json | boolean | – | Also return raw element JSON (verbose) |
No output schema declared.
No examples provided.
get_board_image Look at the board ~43
A PNG picture of the whole board as the candidate sees it (handwriting, sketches, layout). Use when get_board mentions freehand strokes or you need visual context.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_transcript Conversation transcript ~19
Full chat/voice transcript of the current session.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
highlight Point at components ~59
Make components glow on the candidate’s board (e.g. while asking about them). Optionally scroll/zoom their view to them.
| Name | Type | Req | Description |
|---|---|---|---|
| focus | boolean | – | – |
| seconds | number | – | – |
| targets | array | yes | Element ids or labels |
No output schema declared.
No examples provided.
open_board Open the board ~22
Open the sketch board in the user’s browser and return its URL.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
say Speak to the candidate ~53
Send a message to the candidate. It appears in the board chat and is read aloud. Keep it short and conversational (no markdown).
| Name | Type | Req | Description |
|---|---|---|---|
| speak | boolean | – | Read aloud (default true) |
| text | string | yes | – |
No output schema declared.
No examples provided.
set_phase Move to an interview phase ~57
Update the phase tracker the candidate sees: requirements (Requirements), estimation (Estimation), api (API & Data), high-level (High-level), deep-dive (Deep dive), wrap-up (Wrap-up).
| Name | Type | Req | Description |
|---|---|---|---|
| phase | string | yes | – |
No output schema declared.
No examples provided.
start_interview Start a system design interview ~145
Start a new interview session on the board: sets the problem statement, timer and phase, opens the board, and posts your opening message (spoken aloud to the candidate).
| Name | Type | Req | Description |
|---|---|---|---|
| clear_board | boolean | – | Wipe the board first (default false) |
| duration_minutes | integer | – | Default 45 |
| level | string | – | – |
| opening_message | string | – | Your first spoken line, e.g. a greeting and the problem |
| problem | string | yes | The prompt as you would say it to the candidate, plus any constraints you want to reveal up front |
| title | string | yes | Short problem title, e.g. "Design a URL shortener" |
No output schema declared.
No examples provided.
wait_for_candidate Listen to the candidate ~76
Block until the candidate says something (typed or by voice), the board changes and then settles, or the timeout passes. Returns what they said, what changed on the board, and interview timing. Call this in a loop between your replies.
| Name | Type | Req | Description |
|---|---|---|---|
| timeout_seconds | integer | – | Default 45. Keep under your client’s tool timeout. |
No output schema declared.
No examples provided.
How do I install the sketch/design — System Design Interview Board MCP server?
sketch/design — System Design Interview Board runs locally as an npm package, launched with npx -y sysdesign-board. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · sysdesign-board
claude mcp add tghattas-sysdesign-board -- npx -y sysdesign-board
What is the sketch/design — System Design Interview Board MCP server?
sketch/design — System Design Interview Board is an MCP server listed in the public MCP registry as io.github.tGhattas/sysdesign-board. Hand-drawn whiteboard for system design mock interviews; your AI watches, asks and gives feedback. This page covers its npm package (sysdesign-board).
Is the sketch/design — System Design Interview Board MCP server safe to use?
sketch/design — System Design Interview Board scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 sketch/design — System Design Interview Board MCP server expose?
sketch/design — System Design Interview Board exposes 13 tools: open_board, start_interview, wait_for_candidate, say, get_board, and 8 more. Their descriptions and schemas cost roughly 985 tokens of context every time the server is loaded.
Is the sketch/design — System Design Interview Board MCP server still maintained?
sketch/design — System Design Interview Board is still listed as active in the MCP registry. We last reached this channel on 5 November 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 sketch/design — System Design Interview Board MCP server under?
sketch/design — System Design Interview Board declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.