BrandCode Studio (Brandcode-Studio/brandsystem-mcp) is an MCP server listed on the M8ven Trust Index. It scores 71 out of 100, grade C. It declares 53 tools. No publisher has claimed this listing.

C
Caution
71/100

BrandCode Studio

Extracts brand identity from websites and Figma files into structured design tokens, brand policies, and AI-consumable guidelines.

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

Brandcode-Studio

Source: PulseMCP · also listed on Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: FIRECRAWL_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
⚠️
Tool descriptions don’t match what handlers do
3 tools describe read intent but their handlers mutate — brand_check (line 822: re.exec(input)); brand_clarify (line 232: hexPattern.exec(answer)); brand_feedback_review (line 20: mkdir(FEEDBACK_DIR, { recursive: true }))
🚨
Known vulnerabilities in dependencies: 2 critical
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 3 credentials: BRANDCODE_MCP_SMOKE_FULL_KEY, BRANDCODE_MCP_SMOKE_READ_KEY, FIRECRAWL_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies2 critical1 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@3.0.0GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

criticalvitest@3.0.0GHSA-9crc-q9x8-hgqq

Vitest allows Remote Code Execution when accessing a malicious website while Vitest API server is listening

lowyaml@2.7.0GHSA-48c2-rrv3-qjmp

yaml is vulnerable to Stack Overflow via deeply nested YAML collections

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configBRANDCODE_MCP_ENV
configBRANDCODE_MCP_SMOKE_ASSET_ID
🔐 secretBRANDCODE_MCP_SMOKE_FULL_KEY"bck_test_..." \
🔐 secretBRANDCODE_MCP_SMOKE_READ_KEY"bck_test_..." \
configBRANDCODE_MCP_SMOKE_SKIP_FEEDBACK
configBRANDCODE_MCP_SMOKE_TIMEOUT_MS
configBRANDCODE_MCP_SMOKE_URL"https://mcp.staging.brandcode.studio/{slug}" \
configBRANDCODE_MCP_TEST_KEYS
configBRANDSYSTEM_TELEMETRY
🔐 secretFIRECRAWL_API_KEY
configMCP_CLIENT
configUCS_API_BASE_URL
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Dependencies

13 dependencies, 1 flagged: puppeteer-core

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

52/52 tools missing one or more hints — list_brand_assets (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_brand_asset (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); capture_taste (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +49 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Descriptions match behaviour

3 tools describe read intent but their handlers mutate — brand_check (line 822: re.exec(input)); brand_clarify (line 232: hexPattern.exec(answer)); brand_feedback_review (line 20: mkdir(FEEDBACK_DIR, { recursive: true }))

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool inputs are validated

Only 0/52 tool handlers declare input schemas (0%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

38/52 tool handlers wrap calls in try/catch (73%)

Wrap each tool handler body in try/catch and return a structured error response.

Tool test coverage

Only 14/52 tools referenced in tests (27%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

16 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Dev dependencies

2 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Domain consistency

npm scope @brandsystem doesn't match GitHub owner brand-system

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

Tool description accuracy

brand_check: description implies read-only but handler writes/deletes/executes; brand_feedback_review: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 10 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/brandcode-studio/brandsystem-mcp?variant=verified)](https://m8ven.ai/mcp/brandcode-studio/brandsystem-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 62d33a65e4b3b765d07ee2b691c22cd2152bdb1c
code hash: 3e7c0365ee8f8c25355f8f0ec678e3a30e3fdabbfd8ffebc11e25eef4d88564b
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client