Brandsystem MCP — Brand Guidelines for AI
Use existing brand guidelines with AI. Turn websites, PDFs, and Figma into a portable .brand runtime through MCP.
Is Brandsystem MCP — Brand Guidelines for AI safe? Promising trust profile, but some evidence still deserves review.
Compare Brandsystem MCP — Brand Guidelines for AI
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →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
- #154 Hound MCP 73.3 +0.1
- #155 Obsidian Sync MCP 73.3 +0.1
- #156 Brandsystem MCP — Brand Guidelines for AI 73.2 this agent
- #157 Lotus Wisdom 73.1 −0.1
- #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% confidenceBrandsystem MCP — Brand Guidelines for AI MCP Servers average (775 agents)
Quick Trust Read
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
Activity & Reach
Analysis
Activity Inputs
36.2 / 100Supply Chain Trust
Common questions about Brandsystem MCP — Brand Guidelines for AI
Does Brandsystem MCP — Brand Guidelines for AI publish package provenance?
Does Brandsystem MCP — Brand Guidelines for AI have an OpenSSF Scorecard?
Is Brandsystem MCP — Brand Guidelines for AI actively maintained?
What license does Brandsystem MCP — Brand Guidelines for AI use?
Are Brandsystem MCP — Brand Guidelines for AI's commits signed?
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
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 →
- browser
- database
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
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.
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
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/brandsystem-mcp-brand-guidelines-for-ai)
<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
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