updated 2026-08-12 05:02 UTC

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 C Listed MIT
64.0/100
Rank #252 of 1283
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-08-11 · 1d ago
Recent change
Rank +1

Is Brandsystem MCP — Brand Guidelines for AI safe? Brandsystem MCP — Brand Guidelines for AI scores 64.0/100 (Grade C), ranked #252 of 1283 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; no OSSF Scorecard result yet; 40% of recent commits are signed; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#75 CN Scraper MCP — 64.1 (C) → #76 Terraform MCP Server — 64.0 (C) → #78 Cloudflare MCP Server — 63.9 (C) → #79 Cronometer Api MCP — 63.9 (C) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Rank Moved
Rank dropped 16 spots (#240 → #256)
2026-08-08
Newly Listed
First tracked at rank #227
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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
53.0
Activity sub-score · out of 100
#77
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 C 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 →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
10
Forks
0
Last Push
2026-08-11
yesterday
Commits (4 wk)
55
Downloads (7d)
301
npm
HN mentions (30d)
—
Open Issues
3
Rank Change
▼1
was #251

Analysis

HVTrust Dimensions vs MCP Servers

64.0 / 100 · 100.0% confidence

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

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
9.5 / 25
4.5 above avg 5.0
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.7 above avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.8
Maintenance60% last-push freshness · 40% commit activity
18.9 / 20
6.5 above avg 12.4
AdoptionLog-scaled stars · package downloads
5.8 / 20
in line with avg 5.8

Activity Inputs

53.0 / 100
StarsRepository reach
6.2 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
21.8 / 25
CommunityFork signal
0.0 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
—
Not available
Signed Commits
40%
of last 100 commits verified

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?
No OpenSSF Scorecard data is currently published for Brandsystem MCP — Brand Guidelines for AI. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Brandsystem MCP — Brand Guidelines for AI actively maintained?
Actively maintained. The repository was pushed to within the last 1 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?
40% 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
Extensions
Extension based plugin/integration surface 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

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
Listed 1Rank 1
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
HVTrust 64.0 Grade C
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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON