Slingshot brand kit
NPM · @SLINGSHOT-FYI/BRAND-KIT
Slingshot's brand guides, design tokens and an off-brand colour check, for any MCP client.
Available components
Last scanned (12 hours ago)
Scores higher than 40% of npm servers
Category Design and Media
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 16 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 130 tokens (~43/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage78
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 33% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +3
- Stability: unverified → 0.23 ▲ functional
- 15 Oct 26 +28
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 33 functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- 11 Oct 26 38
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Analysed npm/@slingshot-fyi/brand-kit@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
brand_guide Read the Slingshot brand guide ~47
Without a topic, returns the router that says which guide to read for the task. With a topic, returns that guide: every rule with its reason.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | – |
No output schema declared.
No examples provided.
brand_tokens Get the Slingshot design tokens ~35
The brand values: colours, fonts, sizes and spacing, as JSON or as CSS custom properties.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | – |
No output schema declared.
No examples provided.
check_colors Check colours against the brand ~48
Finds every raw colour in a CSS, HTML or JSX snippet and says which are brand tokens written by hand and which are off-brand.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The code or markup to check. |
No output schema declared.
No examples provided.
How do I install the Slingshot brand kit MCP server?
Slingshot brand kit runs locally as an npm package, launched with npx -y @slingshot-fyi/brand-kit. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @slingshot-fyi/brand-kit
claude mcp add fyi-slingshot-brand-kit -- npx -y @slingshot-fyi/brand-kit
What is the Slingshot brand kit MCP server?
Slingshot brand kit is an MCP server listed in the public MCP registry as fyi.slingshot/brand-kit. Slingshot's brand guides, design tokens and an off-brand colour check, for any MCP client. This page covers its npm package (@slingshot-fyi/brand-kit).
Is the Slingshot brand kit MCP server safe to use?
Slingshot brand kit scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Slingshot brand kit MCP server expose?
Slingshot brand kit exposes 3 tools: brand_guide, brand_tokens, check_colors. Their descriptions and schemas cost roughly 130 tokens of context every time the server is loaded.
Is the Slingshot brand kit MCP server still maintained?
Slingshot brand kit is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Slingshot brand kit MCP server under?
Slingshot brand kit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.