dev.brandpilot/brandpilot-mcp
NPM · BRANDPILOT-MCP · 2 COMPONENTS
BrandPilot design systems for coding agents: tokens, design handoff bundle, prompt pack, import.
Available components
Last scanned (2 hours ago)
Scores higher than 39% of npm 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 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
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
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 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 973 tokens (~121/item across 8 items; 8 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 Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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.
- 14 Oct 26 +31
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- First check of Tool coverage: 86 functional
- Package version: 0.3.0 → 0.3.1 functional
- 13 Oct 26 38
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 npm/brandpilot-mcp@0.3.1
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 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| 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 →
finish_external_design ~122
Validates that components and pages were imported, optionally accepts every pending imported draft, then resumes the pipeline at the coherence audit toward Design Review. Only valid while the project is paused at EXTERNAL_DESIGN.
| Name | Type | Req | Description |
|---|---|---|---|
| acceptAll | boolean | – | Accept all pending external-import drafts in one stroke (default false) |
| designId | string | yes | The Design id (cuid) - shown on the design page URL and in the continuation card |
| handoffKey | string | – | Design handoff key; falls back to the DESIGNFLOW_HANDOFF_KEY environment variable |
No output schema declared.
No examples provided.
get_agent_prompt ~62
Markdown onboarding doc for a public system: the two copy-paste prompts an external AI coding agent uses to bootstrap a design package and sync it to Claude Design.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | System name, public slug or alias (e.g. "launchwp") |
No output schema declared.
No examples provided.
get_design_handoff ~117
The design's continuation bundle as JSON: brief, tokens, board digest, the continuation contract (hard floor first, then the latitude level), live inventory, coherence audit and the import contract. Available mid-flow (project paused at EXTERNAL_DESIGN) and post-completion.
| Name | Type | Req | Description |
|---|---|---|---|
| designId | string | yes | The Design id (cuid) - shown on the design page URL and in the continuation card |
| handoffKey | string | – | Design handoff key; falls back to the DESIGNFLOW_HANDOFF_KEY environment variable |
No output schema declared.
No examples provided.
get_design_prompt_pack ~290
The app-authored sequential Claude Design prompt pack (markdown): anchor sheet first, then template-aware component sheets and page prompts, each embedding the latitude contract in force. Regenerated from live data on every call. Without pass it returns the v1 pack; pass=explore then pass=lock with the chosen direction return the v2 two-pass pack, and format=copy-map returns the copy map the v2 pack lists as a project file.
| Name | Type | Req | Description |
|---|---|---|---|
| designId | string | yes | The Design id (cuid) - shown on the design page URL and in the continuation card |
| direction | string | – | The direction chosen from the explore pass, max 2000 characters. Required with pass "lock"; only valid with a pass |
| format | string | – | markdown (default), json for the structured pack, or copy-map for the copy map the v2 pack lists as a project file |
| handoffKey | string | – | Design handoff key; falls back to the DESIGNFLOW_HANDOFF_KEY environment variable |
| pass | string | – | v2 pass: "explore" asks for 2-3 directions per surface, "lock" builds every surface in the chosen direction (needs direction). Omit for the v1 pack |
| with3d | boolean | – | Add one 3D Objects prompt to a v2 pack (only valid with a pass) |
No output schema declared.
No examples provided.
get_system_adoption ~55
Full adoption manifest for a public system: tokens, components, pages, brand asset URLs and the binding design-direction block.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | System name, public slug or alias (e.g. "launchwp") |
No output schema declared.
No examples provided.
get_system_tokens ~118
Export a public system's tokens in one format: globals-css, colors-ts, spacing-ts, typography-ts, tailwind-theme or brand-manifest. Calls the legacy /api/systems/export endpoint, not a v1 path - the export route has no v1 equivalent yet.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | One of globals-css, colors-ts, spacing-ts, typography-ts, tailwind-theme, brand-manifest (default globals-css) |
| name | string | yes | System name, public slug or alias (e.g. "launchwp") |
No output schema declared.
No examples provided.
import_design_artifacts ~177
Import externally designed work back into BrandPilot. Rows land as DRAFT on the carrier project's Deliverables tab for human review - nothing auto-approves. Components: self-contained HTML with inline styles. Pages: standalone HTML documents. Assets: PNG (base64 or URL) with optional sourceCode.
| Name | Type | Req | Description |
|---|---|---|---|
| assets | array | – | – |
| components | array | – | – |
| designId | string | yes | The Design id (cuid) - shown on the design page URL and in the continuation card |
| handoffKey | string | – | Design handoff key; falls back to DESIGNFLOW_HANDOFF_KEY |
| pages | array | – | – |
| source | string | – | Producer label for the Pending review queue: "harness" when archiving from an external build harness onto a harness carrier (default external-design-late) |
No output schema declared.
No examples provided.
list_systems ~32
List the public design systems in the BrandPilot pool (name, slug, brand color, token count, status).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the dev.brandpilot/brandpilot-mcp server?
dev.brandpilot/brandpilot-mcp runs locally as an npm package, launched with npx -y brandpilot-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 · brandpilot-mcp
claude mcp add dev-brandpilot-brandpilot-mcp -- npx -y brandpilot-mcp
What is the dev.brandpilot/brandpilot-mcp server?
dev.brandpilot/brandpilot-mcp is listed in the public MCP registry as dev.brandpilot/brandpilot-mcp. BrandPilot design systems for coding agents: tokens, design handoff bundle, prompt pack, import. This page covers its npm package (brandpilot-mcp).
Is the dev.brandpilot/brandpilot-mcp server safe to use?
dev.brandpilot/brandpilot-mcp scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 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 dev.brandpilot/brandpilot-mcp server expose?
dev.brandpilot/brandpilot-mcp exposes 8 tools: list_systems, get_system_adoption, get_system_tokens, get_agent_prompt, get_design_handoff, and 3 more. Their descriptions and schemas cost roughly 973 tokens of context every time the server is loaded.
Is the dev.brandpilot/brandpilot-mcp server still maintained?
dev.brandpilot/brandpilot-mcp 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 dev.brandpilot/brandpilot-mcp server under?
dev.brandpilot/brandpilot-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.