io.github.ahoybuoy/buoy
NPM · @BUOY-DESIGN/CLI · SCANNED OCT 2
Design tokens and drift checks for coding agents: use the token, not the hardcoded value.
Available components
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects drizzle-orm 0.38.4, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 109 of 343 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to ahoybuoy/buoy). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 403 tokens (~100/item across 4 items; 4 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
How do I install the io.github.ahoybuoy/buoy MCP server?
io.github.ahoybuoy/buoy runs locally as an npm package, launched with npx -y @buoy-design/cli. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @buoy-design/cli
claude mcp add ahoybuoy-buoy -- npx -y @buoy-design/cli
{
"mcpServers": {
"ahoybuoy-buoy": {
"command": "npx",
"args": [
"-y",
"@buoy-design/cli"
]
}
}
} {
"servers": {
"ahoybuoy-buoy": {
"command": "npx",
"args": [
"-y",
"@buoy-design/cli"
]
}
}
} codex mcp add ahoybuoy-buoy -- npx -y @buoy-design/cli
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ahoybuoy-buoy": {
"type": "local",
"command": [
"npx",
"-y",
"@buoy-design/cli"
],
"enabled": true
}
}
} openclaw mcp add ahoybuoy-buoy --command npx --arg -y --arg @buoy-design/cli
mcp_servers:
ahoybuoy-buoy:
command: "npx"
args: ["-y", "@buoy-design/cli"] {
"McpServers": {
"ahoybuoy-buoy": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@buoy-design/cli"
]
}
}
} assistant mcp add ahoybuoy-buoy -t stdio -c npx -a -y @buoy-design/cli
{
"mcpServers": {
"ahoybuoy-buoy": {
"command": "npx",
"args": [
"-y",
"@buoy-design/cli"
]
}
}
} 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.
- 2 Oct 26 +4
- Stability: unverified → 0.27 ▲ functional
- 28 Sept 26 −5
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 +25
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 56
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 2 Oct 2026 · Analysed npm/@buoy-design/cli@0.8.7
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | ahoybuoy/buoy |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/ahoybuoy/buoy/.github/workflows/publish.yml@refs/tags/v0.8.7 |
| Rekor log index | 2937110694 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:9636235f799c8ab34b347fdeae753f27a162726af01c41a87b3c7b3998a13a577e134f8c25858f57c6499da412321cc3e1bc0e3f0d3862b2875062fda |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-gpj5-g38j-94v9 | CVE-2026-39356 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 343 packages
| Packages resolved | 343 |
|---|---|
| Deprecated | 2 |
| Stale | 108 |
| 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 →
check_design_drift Check files for design drift ~88
Run Buoy's drift analysis and return hardcoded values, unknown tokens and inconsistent components, each with the token to use instead when one exists. Pass the files you just edited to check only those; omit files for the whole repository. Run this after editing styles and fix every issue that has a suggestion.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | – | Repository-relative or absolute paths to limit the check to |
No output schema declared.
No examples provided.
design_system_context Design system overview ~65
A Markdown summary of this repository's design system: token categories with example names, the component library, and the anti-patterns Buoy flags. Read it once at the start of a task that touches UI.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | How much to include (default standard) |
No output schema declared.
No examples provided.
find_token_for_value Find the token for a literal value ~125
Given a literal CSS value you are about to write (for example '#1a73e8', '16px', '0.5rem'), return the design tokens in this repository that have exactly that value. Use the token instead of the literal. An empty result means there is no token for it; prefer the nearest token from list_design_tokens over inventing a new value.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Restrict to a category such as color or spacing |
| value | string | yes | The literal value, e.g. '#ffffff' or '8px' |
No output schema declared.
No examples provided.
list_design_tokens List design tokens ~125
The design tokens defined in this repository (CSS custom properties, Tailwind theme, tokens.json, SCSS variables). Call this before writing any CSS, inline style or Tailwind class so you use an existing token instead of a literal value. Filter by category (color, spacing, typography, shadow, border, sizing, motion, zIndex) or a name substring.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Only tokens in this category |
| limit | integer | – | Max tokens to return (default 200) |
| query | string | – | Case-insensitive substring of the token name |
No output schema declared.
No examples provided.
What is the io.github.ahoybuoy/buoy MCP server?
io.github.ahoybuoy/buoy is an MCP server listed in the public MCP registry as io.github.ahoybuoy/buoy. Design tokens and drift checks for coding agents: use the token, not the hardcoded value. This page covers its npm package (@buoy-design/cli).
Is the io.github.ahoybuoy/buoy MCP server safe to use?
io.github.ahoybuoy/buoy scores 80 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 2 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 io.github.ahoybuoy/buoy MCP server expose?
io.github.ahoybuoy/buoy exposes 4 tools: list_design_tokens, find_token_for_value, check_design_drift, design_system_context. Their descriptions and schemas cost roughly 403 tokens of context every time the server is loaded.
Is the io.github.ahoybuoy/buoy MCP server still maintained?
io.github.ahoybuoy/buoy is still listed as active in the MCP registry. We last reached this channel on 2 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 io.github.ahoybuoy/buoy MCP server under?
io.github.ahoybuoy/buoy declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.