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.

Brandsystem MCP — Brand Guidelines for AI

NPM · @BRANDSYSTEM/MCP · SCANNED SEP 20

Use existing brand guidelines with AI. Turn websites, PDFs, and Figma into a .brand runtime.

Available components

0 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 Security99
  • 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
  • 49 of 179 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 Brandcode-Studio/brandsystem-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 61 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3087 tokens (~220/item across 14 items; 12 tools + 2 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 Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 (100% 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.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
Install

How do I install the Brandsystem MCP — Brand Guidelines for AI server?

Brandsystem MCP — Brand Guidelines for AI runs locally as an npm package, launched with npx -y @brandsystem/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 · @brandsystem/mcp

# add to Claude Code
claude mcp add brandcode-studio-brandsystem-mcp -- npx -y @brandsystem/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "brandcode-studio-brandsystem-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@brandsystem/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "brandcode-studio-brandsystem-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@brandsystem/mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add brandcode-studio-brandsystem-mcp -- npx -y @brandsystem/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "brandcode-studio-brandsystem-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@brandsystem/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add brandcode-studio-brandsystem-mcp --command npx --arg -y --arg @brandsystem/mcp
# ~/.hermes/config.yaml
mcp_servers:
  brandcode-studio-brandsystem-mcp:
    command: "npx"
    args: ["-y", "@brandsystem/mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "brandcode-studio-brandsystem-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@brandsystem/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add brandcode-studio-brandsystem-mcp -t stdio -c npx -a -y @brandsystem/mcp
// mcp.json
{
  "mcpServers": {
    "brandcode-studio-brandsystem-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@brandsystem/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 −3
    • Stability: pass → 0.80 functional
  • 17 Sept 26 +1
    • Stability: 0.97 → pass security
  • 15 Sept 26 +1

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

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

  • 11 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 10 Sept 26 +1
    • Stability: 0.97 → pass security
  • 7 Sept 26 +1

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

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/@brandsystem/mcp@0.16.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 Brandcode-Studio/brandsystem-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Brandcode-Studio/brandsystem-mcp/.github/workflows/publish.yml@refs/tags/v0.16.1
Rekor log index 2204754842
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:5a49b5b0c2b8e8a6120e80508255d2254795b2cba6912efb6a749c1055f94ce2efeeaa583fea507780a9fc0479e6773cfbe1cd0fbaf2af080510c8260

Background: How many MCP packages publish verified provenance →

Dependencies 179 packages
Packages resolved 179
Deprecated 1
Stale 49
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 12 exposed · ~2,886 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
brand_brandcode_auth ~297

Activate Brandcode Studio connection for saving and pushing brands. Preferred mode: "activate" displays a short code (e.g. BRAND-7K4X) for the user to enter at brandcode.studio/activate — no copy-paste of tokens needed. Also supports: "status" (check auth), "login" (magic link fallback), "set_key" (manual token), "logout" (clear credentials). Use when the user wants to save their brand to Studio or says "activate", "connect to Brandcode", or "save my brand online". NOT needed for extraction, preview, or brand_check — those work without auth.

NameTypeReqDescription
emailstringEmail address for login. Required when mode="login".
keystringSession token from magic link verification. Required when mode="set_key". Format: JWT from /api/auth/verify.
modestringyesAuth action. "activate" (recommended) starts device code flow — displays a short code for the user to enter at brandcode.studio/activate, then polls for completion. No copy-paste needed. "status" che…
studio_urlstringBrandcode Studio base URL. Defaults to "https://brandcode.studio". Override for self-hosted instances.
NameTypeReqDescription
_metadataobjectyes

No examples provided.

brand_brandcode_connect ~218

Connect a local .brand/ to Brandcode Studio. Two modes: "pull" (default) downloads an existing hosted brand by URL/slug. "save" uploads the local .brand/ to Studio (requires prior auth via brand_brandcode_auth). THE tool when the user says "make our brand available to my whole team", "share our brand with the team", "connect to Brandcode", "pull from Studio", "save brand to Studio", or "upload my brand". Returns brand name, slug, sync token, and connection details.

NameTypeReqDescription
modestring"pull" connects to an existing hosted brand and downloads it. "save" uploads the local .brand/ to Studio (requires auth via brand_brandcode_auth).
share_tokenstringShare token for protected brands (x-brand-share-token)
urlstringBrandcode Studio brand URL or slug. Required for mode="pull". Examples: "https://brandcode.studio/start/brands/pendium", "pendium"
NameTypeReqDescription
_metadataobjectyes

No examples provided.

brand_check ~297

Inline brand linter — call this WHILE writing content or code, the way you call a type-checker. <50ms pass/fail on any combination of text (voice/never-say/AI-isms), color (palette match with ΔE distance), font (typography match), or css (anti-pattern violations). Designed for tight loops: write a sentence, brand_check it, fix, continue. Returns specific actionable fixes per failed input. Requires brand_compile to have run first. NOT a publish-time gate — use brand_check_compliance for the single PASS/FAIL verdict before shipping. NOT for 0-100 scoring — use brand_audit_content. NOT for HTML/CSS rule violations — use brand_preflight.

NameTypeReqDescription
colorstringHex color to check against the brand palette. Returns nearest brand color with perceptual distance (ΔE). Example: "#3b82f6"
cssstringCSS snippet to check for visual anti-pattern violations (shadows, gradients, etc.). Example: "box-shadow: 0 2px 4px rgba(0,0,0,0.1)"
fontstringFont family name to check against brand typography. Example: "Helvetica"
textstringText to check for voice violations (never-say words, anchor term misuse, AI-isms). Example: "We leverage cutting-edge AI solutions"
NameTypeReqDescription
_metadataobjectyes
brand_palettearray
checkedarray
errorstring
flagsarray
passboolean

No examples provided.

brand_clarify ~193

Resolve an ambiguous brand value interactively. After brand_compile, some values need human confirmation — wrong primary color, unknown font, unassigned color roles. Pass the clarification item ID and the user's answer (hex color, role name, font name, or 'yes'/'no'). Supports natural language: 'the purple one is accent' or '#5544f2 is secondary'. Returns updated identity and remaining clarification count.

NameTypeReqDescription
answerstringyesThe user's answer: a hex color (#ff0000), a role name (primary, secondary, accent, neutral, surface, text, action, tint, overlay, border, gradient, highlight), a font name, 'yes'/'no', or natural lan…
idstringyesClarification item ID from needs-clarification.yaml (e.g. 'clarify-1')
NameTypeReqDescription
_metadataobjectyes

No examples provided.

brand_compile ~119

Generate DTCG design tokens, design-synthesis.json, DESIGN.md, brand runtime, and interaction policy from extracted brand data. Transforms core-identity.yaml into tokens.json, brand-runtime.json (single-document brand contract for AI agents), and interaction-policy.json (enforceable rules). When Session 2+ data exists, also generates visual-identity-manifest.md and system-integration.md. Use after brand_extract_web, brand_extract_site, brand_extract_visual, or brand_extract_figma. Returns token counts, clarification items, and file list.

Input schema present but exposes no named parameters.

NameTypeReqDescription
_metadataobjectyes

No examples provided.

brand_context ~328

Select a task-scoped brand context from the compiled runtime. THE tool to call first when the user says 'write this in our voice', 'write this LinkedIn post in our brand voice', 'make an on-brand social graphic', or 'build a landing page' — it returns only the governed rules relevant to that task instead of the full runtime. Deterministic: task_type maps to sections via a fixed table, audience matches governed personas exactly or reports no-match — no inference. Returns context (the selected brand slices), output_contract (required delivery shape), matched_selectors (what was chosen and why), and no_governed_match. NOT for reading the entire runtime (use brand_runtime) or checking finished content (use brand_check).

NameTypeReqDescription
audiencestringOptional audience label (e.g. 'security leaders'). Matched against governed persona names by normalized substring — an explicit no-match is returned rather than guessing.
budgetstring'standard' returns the selected sections in full. 'compact' returns identity colors/typography plus hard rules only (anti-patterns + never_say) — for tight sub-agent contexts.
channelstringOptional channel label (e.g. 'LinkedIn'). Recorded in matched_selectors for the agent; does not alter governed rules.
task_typestringyesWhat is being created. Deterministically selects runtime sections: visual tasks (code-ui, image-graphic) get identity+visual; copy tasks (blog-article, email, video-script) get voice+strategy; mixed…
NameTypeReqDescription
_metadataobjectyes
approvalstring
contextobject
errorstring
matched_selectorsobject
no_governed_matchboolean
output_contractobject

No examples provided.

brand_export ~356

Bundle the compiled brand system into a portable artifact for a specific destination. Use when asked 'share my brand', 'export for ChatGPT/Cursor/team', 'generate brand guidelines', 'make a one-pager', or 'create a brand PDF'. Target 'chat': self-contained markdown for upload to any AI conversation (Claude, ChatGPT, Gemini). Target 'code': MCP server config + CLAUDE.md/.cursorrules snippet. Target 'team': human-readable brand guidelines for designers/writers/marketers. Target 'email': ~500-word summary for Slack or email. Target 'claude-skill': SKILL.md with embedded logo + rules for persistent Claude artifacts. Target 'pdf': branded PDF with swatches, type, anti-patterns, and voice. Set include_logo=false to drop the embedded SVG/data URI when size matters. Writes to .brand/exports/<file> and returns the full content (markdown targets) or a generation summary (pdf). Requires brand_compile to have run first. NOT for previewing one section — use brand_preview.

NameTypeReqDescription
include_logobooleanEmbed logo SVG/data URI in the export. Set false to reduce file size. Default: true.
targetstringyesWhere this export will be used. 'chat': upload to AI conversation (Claude/ChatGPT/Gemini). 'code': paste into CLAUDE.md or .cursorrules. 'team': share with designers/writers. 'email': send via Slack…
NameTypeReqDescription
_metadataobjectyes

No examples provided.

brand_preflight ~193

Check HTML/CSS against brand rules — catches off-brand colors, wrong fonts, missing logo, and anti-pattern violations (drop shadows, gradients, etc.). Pass an HTML string or file path. Mode 'check' (default) runs all compliance checks and returns pass/warn/fail per rule. Mode 'rules' lists all active preflight rules without checking content. Use after generating any visual content to validate brand compliance. Returns overall status and per-check details. NOT for scoring content copy — use brand_audit_content. NOT for brand directory validation — use brand_audit.

NameTypeReqDescription
htmlstringyesHTML to validate: either a full HTML string (with <style> blocks) or a file path ending in .html (e.g. 'output.html')
modestring'check' (default): validates HTML against all brand rules. 'rules': lists all active rules without running checks.
NameTypeReqDescription
_metadataobjectyes

No examples provided.

brand_report ~92

Generate a portable HTML brand identity report with embedded logos, color swatches, typography, and tokens. The HTML is self-contained and works offline — upload it to any AI chat (Claude, ChatGPT, Gemini) as instant brand guidelines. Written to .brand/brand-report.html. Use after brand_compile. Returns file path, report summary (color/font/logo counts), and a ready-to-copy Brand Instructions text block.

Input schema present but exposes no named parameters.

NameTypeReqDescription
_metadataobjectyes

No examples provided.

brand_runtime ~255

Read the compiled brand runtime contract (brand-runtime.json). Returns the brand system that AI agents load as context for on-brand output. Supports slicing: 'full' (~1200 tokens, everything), 'visual' (~200 tokens, colors + fonts + anti-patterns), 'voice' (~400 tokens, tone + vocabulary + perspective), 'minimal' (~100 tokens, primary color + heading font). Use slices when passing brand context to sub-agents — smaller context reduces token cost and agent satisficing. Live Mode aware: when enabled via brand_brandcode_live, the runtime refreshes from the hosted Brandcode runtime on each call (subject to cache TTL). Falls back silently to the local mirror on network error. Read-only. Run brand_compile to refresh.

NameTypeReqDescription
slicestringWhich slice of the runtime to return. 'full': everything (~1200 tokens). 'visual': colors, typography, logo, anti-patterns, composition (~200 tokens). 'voice': tone, vocabulary, never-say, perspectiv…
NameTypeReqDescription
_metadataobjectyes
agent_tipstring
approvalstring
errorstring
runtimeobject
runtime_originstring

No examples provided.

brand_start ~447

Adopt a brand into a portable .brand/ runtime from whatever source already exists: existing brand guidelines (PDF), a website URL, a Figma library, or a hosted Brandcode Studio brand. THE entry point when the user says 'use my existing brand guidelines with AI', 'I have a PDF brand guide', 'use our Figma library', 'create a brand system', 'extract brand from website', or 'set up brand guidelines'. Pass website_url, guideline_pdf, figma_file_key, or brandcode_url — or pass no source and it discovers local candidates and presents a menu with a privacy explanation. Set mode='auto' with a website_url to run the full pipeline (extract, compile DTCG tokens + design-synthesis.json + DESIGN.md + brand runtime + interaction policy, generate HTML report) in one call. If .brand/ already exists, returns current status with next steps. NOT for reading an already-compiled brand (use brand_runtime or brand_context) or for sharing an existing brand with a team (use brand_brandcode_connect).

NameTypeReqDescription
brandcode_urlstringBrandcode Studio brand URL for adopting an existing hosted brand (e.g. 'https://brandcode.studio/start/brands/acme'). Routes adoption through brand_brandcode_connect.
client_namestringyesCompany or brand name (e.g. 'Acme Corp')
figma_file_keystringFigma file key for design-file extraction. Routes adoption through brand_extract_figma.
guideline_pdfstringPath to a PDF brand guideline in or under the working directory (e.g. './brand-guidelines.pdf'). Routes adoption through brand_extract_pdf.
industrystringIndustry vertical for smarter extraction (e.g. 'fintech', 'healthcare', 'content marketing')
modestring'auto' (recommended): runs full pipeline in one call when website_url is provided. 'interactive': assesses available sources (including files discovered in the working directory) and presents a sourc…
website_urlstringCompany website URL to extract brand identity from (e.g. 'https://acme.com')
NameTypeReqDescription
_metadataobjectyes

No examples provided.

brand_status ~91

Check brand system progress and get next steps. Shows what has been extracted (colors, fonts, logo), confidence levels, session completion status, and what to do next. Use when resuming a previous session, checking readiness, or when the user asks 'what's the state of my brand?' If no .brand/ exists, returns a full getting-started guide with all available tools. Returns structured status data.

Input schema present but exposes no named parameters.

NameTypeReqDescription
_metadataobjectyes
errorstring
getting_startedobject
recoveryobject
statusstring
tool_sessionsarray

No examples provided.

Common questions

What is the Brandsystem MCP — Brand Guidelines for AI server?

Brandsystem MCP — Brand Guidelines for AI is listed in the public MCP registry as io.github.Brandcode-Studio/brandsystem-mcp. Use existing brand guidelines with AI. Turn websites, PDFs, and Figma into a .brand runtime. This page covers its npm package (@brandsystem/mcp).

Is the Brandsystem MCP — Brand Guidelines for AI server safe to use?

Brandsystem MCP — Brand Guidelines for AI 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 Brandsystem MCP — Brand Guidelines for AI server expose?

Brandsystem MCP — Brand Guidelines for AI exposes 12 tools: brand_start, brand_status, brand_compile, brand_clarify, brand_report, and 7 more. Their descriptions and schemas cost roughly 2,886 tokens of context every time the server is loaded.

Is the Brandsystem MCP — Brand Guidelines for AI server still maintained?

Brandsystem MCP — Brand Guidelines for AI 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 Brandsystem MCP — Brand Guidelines for AI server under?

Brandsystem MCP — Brand Guidelines for AI declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.