# design.brilliant/mcp (npm · @brilliant-hq/mcp)

Local MCP bridge: your coding agent designs on Brilliant's real vector canvas, fully on 127.0.0.1.

- Trust score: 47/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- npm · `@brilliant-hq/mcp`: 47/100 (this document), [markdown](https://verifymcp.io/servers/design-brilliant-mcp/brilliant-hq-mcp.md), [page](https://verifymcp.io/servers/design-brilliant-mcp/brilliant-hq-mcp)

## Channel facts

- Registry: `npm`
- Package: `@brilliant-hq/mcp`
- Version: `0.1.6`
- 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-09-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 0 of 1 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 6/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (UNLICENSED) isn't a recognized OSI-approved license.
  - Actively maintained (last published 19 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: this package declared that it provides tools, but our sandbox run could not list them, so the captured schema is incomplete.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this package declared that it provides tools, but our sandbox run could not list them.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: this package declared that it provides tools, but our sandbox run could not list them.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 3 categories.** Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you.

## Install

### How do I install the design.brilliant/mcp server?

design.brilliant/mcp runs locally as an npm package, launched with npx -y @brilliant-hq/mcp. 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 design-brilliant-mcp -- npx -y @brilliant-hq/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "design-brilliant-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@brilliant-hq/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "design-brilliant-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@brilliant-hq/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add design-brilliant-mcp -- npx -y @brilliant-hq/mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add design-brilliant-mcp --command npx --arg -y --arg @brilliant-hq/mcp
```

### Hermes

```yaml
mcp_servers:
  design-brilliant-mcp:
    command: "npx"
    args: ["-y", "@brilliant-hq/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "design-brilliant-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@brilliant-hq/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add design-brilliant-mcp -t stdio -c npx -a -y @brilliant-hq/mcp
```

### Other

```json
{
  "mcpServers": {
    "design-brilliant-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@brilliant-hq/mcp"
      ]
    }
  }
}
```

## 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-09-21 (score 47, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 46, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 45, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 44, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 43, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 42, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 41, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 40, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (0)

The sandbox run completed and this package exposed no tools.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/design-brilliant-mcp/brilliant-hq-mcp#diagnostics

## Score history

- 2026-09-21: 47
- 2026-09-20: 46
- 2026-09-19: 46
- 2026-09-18: 45
- 2026-09-17: 45
- 2026-09-16: 45
- 2026-09-15: 44
- 2026-09-14: 44
- 2026-09-13: 43
- 2026-09-12: 43
- 2026-09-11: 42
- 2026-09-10: 42
- 2026-09-09: 41
- 2026-09-08: 41
- 2026-09-07: 40
- 2026-09-06: 40
- 2026-09-05: 39
- 2026-09-04: 39
- 2026-09-03: 35
- 2026-09-02: 35
- 2026-09-01: 35
- 2026-08-31: 35
- 2026-08-30: 35
- 2026-08-29: 35
- 2026-08-28: 35
- 2026-08-27: 20

## Common questions

### What is the design.brilliant/mcp server?

design.brilliant/mcp is listed in the public MCP registry as design.brilliant/mcp. Local MCP bridge: your coding agent designs on Brilliant's real vector canvas, fully on 127.0.0.1. This page covers its npm package (@brilliant-hq/mcp).

### Is the design.brilliant/mcp server safe to use?

design.brilliant/mcp scores 47 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 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 design.brilliant/mcp server expose?

design.brilliant/mcp exposes no tools. We connected to it and read its tool list, and it was empty, so it offers an MCP client nothing to call.

### Is the design.brilliant/mcp server still maintained?

design.brilliant/mcp is still listed as active in the MCP registry. We last reached this channel on 21 September 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 design.brilliant/mcp server under?

design.brilliant/mcp declares the UNLICENSED licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@brilliant-hq/mcp
- Socket report: https://socket.dev/npm/package/@brilliant-hq/mcp
- Website: https://brilliant.design/
- Changelog RSS feed: https://verifymcp.io/servers/design-brilliant-mcp/brilliant-hq-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/design-brilliant-mcp/brilliant-hq-mcp.json
- HTML version of this page: https://verifymcp.io/servers/design-brilliant-mcp/brilliant-hq-mcp