Brandsystem MCP — Brand Guidelines for AI

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

MCP Servers TypeScript Listed MIT

Is Brandsystem MCP — Brand Guidelines for AI safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 7.0 / 10
Provenance Attested
Signed commits 45%
Last push 9d ago
Compare Brandsystem MCP — Brand Guidelines for AI
Suggest a correction

In detail: Brandsystem MCP — Brand Guidelines for AI scores 73.2/100 (Grade B), ranked #259 of 1325 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.0/10; 45% of recent commits are signed; last pushed 2026-09-17. Every point is earned from checkable signals — never paid placement. How scoring works →

How Brandsystem MCP — Brand Guidelines for AI compares in MCP Servers

  1. #154 Hound MCP 73.3 +0.1
  2. #155 Obsidian Sync MCP 73.3 +0.1
  3. #156 Brandsystem MCP — Brand Guidelines for AI 73.2 this agent
  4. #157 Lotus Wisdom 73.1 −0.1
  5. #158 MikroMCP 73.0 −0.2

Bars show each HVTrust score; the tick marks Brandsystem MCP — Brand Guidelines for AI’s 73.2.

Where the 73.2 comes from

HVTrust dimensions vs the MCP Servers average

73.2 / 100 · 100.0% confidence

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

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
18.5 / 25
8.2 above avg 10.3
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.6 above avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
14.4 / 17
2.2 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
12.6 / 20
0.5 above avg 12.1
AdoptionLog-scaled stars · package downloads
5.8 / 20
1.4 below avg 7.2

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-09-25
Rank Moved
Rank rose 12 spots (#270 → #258)
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Redis
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
Maintainer Checklist
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
36.2
Activity sub-score · out of 100
#156

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 →

Signals refreshed 2026-09-26 06:32 UTC · Repo last pushed 9 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
14
Forks
1
Last Push
2026-09-17
9 days ago
Commits (4 wk)
1
Downloads (7d)
164
npm
HN mentions (30d)
—
Open Issues
2
Rank Change
▼1
was #258

Analysis

Activity Inputs

36.2 / 100
StarsRepository reach
7.1 / 30
FreshnessLast push recency
23.8 / 25
ActivityRecent commits
3.8 / 25
CommunityFork signal
1.4 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
7.0 / 10
OpenSSF Scorecard · scanned Sep 21, 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 0

Common questions about Brandsystem MCP — Brand Guidelines for AI

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.0/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?
Maintained. Last push was 9 days ago.
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-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Redis
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
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.

Reputation Timeline

Signal history
Rank 26HVTrust 12Grade 11Listed 2Surface 1Scorecard 1Delisted 1Provenance 1MCP 1Surface 1
2026-09-25
Rank Moved
Rank rose 12 spots (#270 → #258)
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Redis
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 595 spots (#862 → #267)
2026-09-23
HVTrust Changed
HVTrust up 45.3pts (27.5 → 72.8)
2026-09-22
Newly Listed
First tracked at rank #862
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-17
Rank Moved
Rank rose 13 spots (#272 → #259)
2026-09-16
Rank Moved
Rank dropped 13 spots (#259 → #272)
2026-09-14
Rank Moved
Rank dropped 20 spots (#238 → #258)
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

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 73.2 Grade B
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