Brandsystem MCP Server

@brandsystem/mcp npm v0.16.1 Source verified

Published by brandcode-studio — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

Use existing brand guidelines with AI. This MCP server turns websites, PDFs, and Figma libraries into a portable .brand runtime with design tokens, voice rules, provenance, and compliance checks.

Trust grade
A
94/100
Last scanned get badge →
Trust
A · 94/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 94/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 2

high Shell/command execution in server code (dist/tools/brand-feedback.js)MTC-SRC-002

In the server's implementation (`dist/tools/brand-feedback.js:75`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: /require\s*\(\s*['"]child_process/i, /import\s+.*child_process/i, ]; function sanitize(input) { let s = inpu

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/tools/brand-feedback.js

low Shell/command execution in packaging/dev tooling (dist/cli/install.js)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`dist/cli/install.js:16`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: rt { spawn } from "node:child_process"; export const INSTALL_CLIENTS = [ "claude-code", "cline", "codex",

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/cli/install.js

Tools 44

Each tool and what it can reach — statically extracted from the published source.

  • brand_auditno sensitive capability
  • brand_audit_contentno sensitive capability
  • brand_audit_driftno sensitive capability
  • brand_brandcode_authno sensitive capability
  • brand_brandcode_connectno sensitive capability
  • brand_brandcode_liveno sensitive capability
  • brand_brandcode_statusno sensitive capability
  • brand_brandcode_syncno sensitive capability
  • brand_build_journeyno sensitive capability
  • brand_build_matrixno sensitive capability
Show 34 more tools ↓
  • brand_build_personasno sensitive capability
  • brand_build_themesno sensitive capability
  • brand_checkno sensitive capability
  • brand_check_complianceno sensitive capability
  • brand_clarifyno sensitive capability
  • brand_compileno sensitive capability
  • brand_compile_messagingno sensitive capability
  • brand_connect_repono sensitive capability
  • brand_contextno sensitive capability
  • brand_deepen_identityno sensitive capability
  • brand_enrich_skillno sensitive capability
  • brand_exportno sensitive capability
  • brand_extract_figmano sensitive capability
  • brand_extract_messagingno sensitive capability
  • brand_extract_pdfno sensitive capability
  • brand_extract_siteno sensitive capability
  • brand_extract_visualno sensitive capability
  • brand_extract_webno sensitive capability
  • brand_feedbackno sensitive capability
  • brand_feedback_reviewno sensitive capability
  • brand_feedback_triageno sensitive capability
  • brand_generate_designmdno sensitive capability
  • brand_ingest_assetsno sensitive capability
  • brand_initno sensitive capability
  • brand_preflightno sensitive capability
  • brand_previewno sensitive capability
  • brand_repo_statusno sensitive capability
  • brand_reportno sensitive capability
  • brand_resolve_conflictsno sensitive capability
  • brand_runtimeno sensitive capability
  • brand_set_logono sensitive capability
  • brand_startno sensitive capability
  • brand_statusno sensitive capability
  • brand_writeno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.16.1 latest A 94/100 2 1.13.0 2026-09-08

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 94/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/brandsystem-mcp/badge.svg)](https://mcptrustchecker.com/registry/brandsystem-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/brandsystem-mcp"><img src="https://mcptrustchecker.com/registry/brandsystem-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/brandsystem-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @brandsystem/mcp --online

Use the free API → How scoring works

More in Design & Media