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

Brandsystem MCP — Brand Guidelines for AI has an HVTrust score of 74.1/100 (Grade B), ranked #237 of 1328 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Brandsystem MCP — Brand Guidelines for AI?

Brandsystem MCP — Brand Guidelines for AI scores 74.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 14 GitHub stars and is categorized under MCP Servers.

Brandsystem MCP — Brand Guidelines for AI

Brandcode-Studio/brandsystem-mcp

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

MCP Servers TypeScript Grade B Listed MIT

74.1/100

Rank #237 of 1328

Compare Brandsystem MCP — Brand Guidelines for AI

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-09-10 · 3d ago

Recent change

Rank +1

Is Brandsystem MCP — Brand Guidelines for AI safe? Brandsystem MCP — Brand Guidelines for AI scores 74.1/100 (Grade B), ranked #237 of 1328 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 7.3/10; 45% of recent commits are signed; last pushed 2026-09-10. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#141 Hunch MCP — 74.4 (B) → #142 MCP Server Trello — 74.2 (B) → #144 Activitypub MCP — 74.1 (B) → #145 Growthbook MCP — 74.1 (B) →

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-09-11

Rank Moved

Rank dropped 18 spots (#219 → #237)

2026-09-07

Rank Moved

Rank dropped 16 spots (#199 → #215)

2026-09-05

Grade Changed

Trust grade D → B

Maintainer Checklist

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for Brandsystem MCP — Brand Guidelines for AI View MCP Servers Report missing data

37.7

Activity sub-score · out of 100

#143

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-13

Activity & Reach

Stars

Forks

Last Push

2026-09-10

3 days ago

Commits (4 wk)

Downloads (7d)

165

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #235

Analysis

HVTrust Dimensions vs MCP Servers

74.1 / 100 · 100.0% confidence

Brandsystem MCP — Brand Guidelines for AI MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

18.9 / 25

8.8 above avg 10.1

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

14.7 / 17

2.6 above avg 12.1

Maintenance60% last-push freshness · 40% commit activity

12.8 / 20

0.7 above avg 12.1

AdoptionLog-scaled stars · package downloads

5.8 / 20

1.2 below avg 7.0

Activity Inputs

37.7 / 100

StarsRepository reach

7.1 / 30

FreshnessLast push recency

24.6 / 25

ActivityRecent commits

6.0 / 25

CommunityFork signal

0.0 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

7.3 / 10

OpenSSF Scorecard · scanned Sep 3, 2026

Signed Commits

45%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 10

SAST 10

Security-Policy 10

Signed-Releases -1

Token-Permissions 9

Vulnerabilities 4

Is Brandsystem MCP — Brand Guidelines for AI safe?

Brandsystem MCP — Brand Guidelines for AI has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Brandsystem MCP — Brand Guidelines for AI publish package provenance?

Yes. Brandsystem MCP — Brand Guidelines for AI's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Brandsystem MCP — Brand Guidelines for AI have an OpenSSF Scorecard?

Brandsystem MCP — Brand Guidelines for AI has an OpenSSF Scorecard score of 7.3/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Brandsystem MCP — Brand Guidelines for AI actively maintained?

Actively maintained. The repository was pushed to within the last 3 day(s).

What license does Brandsystem MCP — Brand Guidelines for AI use?

Brandsystem MCP — Brand Guidelines for AI ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Brandsystem MCP — Brand Guidelines for AI's commits signed?

45% of the last 100 commits to Brandsystem MCP — Brand Guidelines for AI are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

Brandsystem MCP — Brand Guidelines for AI appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

2 tags

Broad capability areas detected.

browser
database

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to Brandsystem MCP — Brand Guidelines for AI's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

Maintain Brandsystem MCP — Brand Guidelines for AI?

For maintainers

HVTrust scores Brandsystem MCP — Brand Guidelines for AI from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-11

Rank Moved

Rank dropped 18 spots (#219 → #237)

2026-09-07

Rank Moved

Rank dropped 16 spots (#199 → #215)

2026-09-05

Grade Changed

Trust grade D → B

2026-09-05

Rank Moved

Rank rose 604 spots (#805 → #201)

2026-09-05

HVTrust Changed

HVTrust up 25.8pts (49.2 → 75.0)

2026-09-04

Rank Moved

Rank dropped 31 spots (#774 → #805)

2026-09-03

Scorecard Added

OSSF Scorecard: 7.3/10

2026-09-03

Rank Moved

Rank rose 230 spots (#1004 → #774)

2026-09-03

HVTrust Changed

HVTrust up 10.4pts (38.8 → 49.2)

2026-09-02

Grade Changed

Trust grade C → D

2026-09-02

Rank Moved

Rank dropped 575 spots (#429 → #1004)

2026-09-02

HVTrust Changed

HVTrust down 20.7pts (59.5 → 38.8)

2026-09-01

Rank Moved

Rank dropped 11 spots (#418 → #429)

2026-08-31

Grade Changed

Trust grade D → C

2026-08-31

Rank Moved

Rank rose 470 spots (#888 → #418)

2026-08-31

HVTrust Changed

HVTrust up 20.7pts (38.9 → 59.6)

2026-08-30

Grade Changed

Trust grade C → D

2026-08-30

Rank Moved

Rank dropped 492 spots (#396 → #888)

2026-08-30

HVTrust Changed

HVTrust down 20.8pts (59.7 → 38.9)

2026-08-29

Rank Moved

Rank dropped 12 spots (#384 → #396)

2026-08-26

Rank Moved

Rank dropped 40 spots (#349 → #389)

2026-08-24

Grade Changed

Trust grade D → C

2026-08-24

Rank Moved

Rank rose 311 spots (#657 → #346)

2026-08-24

HVTrust Changed

HVTrust up 20.6pts (38.7 → 59.3)

2026-08-22

Grade Changed

Trust grade C → D

2026-08-22

Rank Moved

Rank dropped 314 spots (#343 → #657)

2026-08-22

HVTrust Changed

HVTrust down 20.7pts (59.5 → 38.8)

2026-08-19

Grade Changed

Trust grade D → C

2026-08-19

Rank Moved

Rank rose 312 spots (#658 → #346)

2026-08-19

HVTrust Changed

HVTrust up 20.9pts (38.6 → 59.5)

2026-08-18

Rank Moved

Rank dropped 31 spots (#627 → #658)

2026-08-17

Grade Changed

Trust grade C → D

2026-08-17

Rank Moved

Rank dropped 350 spots (#277 → #627)

2026-08-17

HVTrust Changed

HVTrust down 22.9pts (63.2 → 40.3)

2026-08-16

Rank Moved

Rank dropped 29 spots (#248 → #277)

2026-08-15

Rank Moved

Rank dropped 12 spots (#236 → #248)

2026-08-13

Grade Changed

Trust grade D → C

2026-08-13

Rank Moved

Rank rose 347 spots (#581 → #234)

2026-08-13

HVTrust Changed

HVTrust up 22.6pts (42.3 → 64.9)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

2026-08-12

Grade Changed

Trust grade C → D

2026-08-12

Rank Moved

Rank dropped 330 spots (#251 → #581)

2026-08-12

HVTrust Changed

HVTrust down 21.8pts (64.1 → 42.3)

2026-08-10

Rank Moved

Rank dropped 16 spots (#240 → #256)

2026-08-08

Newly Listed

First tracked at rank #227

GitHub → npm: @brandsystem/mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/brandsystem-mcp-brand-guidelines-for-ai.svg)](https://hvtracker.net/agents/brandsystem-mcp-brand-guidelines-for-ai)
            
HTML:
            <a href="https://hvtracker.net/agents/brandsystem-mcp-brand-guidelines-for-ai"><img src="https://hvtracker.net/badge/brandsystem-mcp-brand-guidelines-for-ai.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON