# io.github.ahoybuoy/buoy (npm · @buoy-design/cli)

Design tokens and drift checks for coding agents: use the token, not the hardcoded value.

- Trust score: 80/100 (high trust)
- Change this week: −1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-02

## Components

- npm · `@buoy-design/cli`: 80/100 (this document), [markdown](https://verifymcp.io/servers/ahoybuoy-buoy/buoy-design-cli.md), [page](https://verifymcp.io/servers/ahoybuoy-buoy/buoy-design-cli)

## Channel facts

- Registry: `npm`
- Package: `@buoy-design/cli`
- Version: `0.8.7`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-02.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects drizzle-orm 0.38.4, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 109 of 343 dependencies flagged as unhealthy (2 deprecated).
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to ahoybuoy/buoy).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 403 tokens (~100/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add ahoybuoy-buoy -- npx -y @buoy-design/cli
```

### Cursor

```json
{
  "mcpServers": {
    "ahoybuoy-buoy": {
      "command": "npx",
      "args": [
        "-y",
        "@buoy-design/cli"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ahoybuoy-buoy": {
      "command": "npx",
      "args": [
        "-y",
        "@buoy-design/cli"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ahoybuoy-buoy -- npx -y @buoy-design/cli
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ahoybuoy-buoy": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@buoy-design/cli"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ahoybuoy-buoy --command npx --arg -y --arg @buoy-design/cli
```

### Hermes

```yaml
mcp_servers:
  ahoybuoy-buoy:
    command: "npx"
    args: ["-y", "@buoy-design/cli"]
```

### Netclaw

```json
{
  "McpServers": {
    "ahoybuoy-buoy": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@buoy-design/cli"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add ahoybuoy-buoy -t stdio -c npx -a -y @buoy-design/cli
```

### Other

```json
{
  "mcpServers": {
    "ahoybuoy-buoy": {
      "command": "npx",
      "args": [
        "-y",
        "@buoy-design/cli"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-02 (score 80, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-28 (score 76, −5)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 81, +25)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 56)

First indexed and scored.

## MCP tools (4)

### `list_design_tokens` (~125 tokens)

List design tokens

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.

Input parameters:

- `category` (string): Only tokens in this category
- `limit` (integer): Max tokens to return (default 200)
- `query` (string): Case-insensitive substring of the token name

### `find_token_for_value` (~125 tokens)

Find the token for a literal value

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.

Input parameters:

- `category` (string): Restrict to a category such as color or spacing
- `value` (string, required): The literal value, e.g. '#ffffff' or '8px'

### `check_design_drift` (~88 tokens)

Check files for design drift

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.

Input parameters:

- `files` (array): Repository-relative or absolute paths to limit the check to

### `design_system_context` (~65 tokens)

Design system overview

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.

Input parameters:

- `detail` (string): How much to include (default standard)

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/ahoybuoy-buoy/buoy-design-cli#diagnostics

## Score history

- 2026-10-02: 80
- 2026-10-01: 76
- 2026-09-30: 76
- 2026-09-29: 76
- 2026-09-28: 76
- 2026-09-27: 81
- 2026-09-26: 81
- 2026-09-25: 81
- 2026-09-24: 56

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@buoy-design/cli
- Socket report: https://socket.dev/npm/package/@buoy-design/cli
- Repository: https://github.com/ahoybuoy/buoy
- Changelog RSS feed: https://verifymcp.io/servers/ahoybuoy-buoy/buoy-design-cli.xml
- Changelog JSON feed: https://verifymcp.io/servers/ahoybuoy-buoy/buoy-design-cli.json
- HTML version of this page: https://verifymcp.io/servers/ahoybuoy-buoy/buoy-design-cli