design.brilliant/mcp
NPM · @BRILLIANT-HQ/MCP · SCANNED SEP 21
Local MCP bridge: your coding agent designs on Brilliant's real vector canvas, fully on 127.0.0.1.
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 Security100
- 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
- 0 of 1 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency6
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (UNLICENSED) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 19 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability0
- 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.Unverified
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage0
- Tool coverage not yet verified: this package declared that it provides tools, but our sandbox run could not list them.Unverified
Tool Safety0
- Tool safety not yet verified: this package declared that it provides tools, but our sandbox run could not list them.Unverified
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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. How we score packages →
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.
npm · @brilliant-hq/mcp
claude mcp add design-brilliant-mcp -- npx -y @brilliant-hq/mcp
{
"mcpServers": {
"design-brilliant-mcp": {
"command": "npx",
"args": [
"-y",
"@brilliant-hq/mcp"
]
}
}
} {
"servers": {
"design-brilliant-mcp": {
"command": "npx",
"args": [
"-y",
"@brilliant-hq/mcp"
]
}
}
} codex mcp add design-brilliant-mcp -- npx -y @brilliant-hq/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"design-brilliant-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@brilliant-hq/mcp"
],
"enabled": true
}
}
} openclaw mcp add design-brilliant-mcp --command npx --arg -y --arg @brilliant-hq/mcp
mcp_servers:
design-brilliant-mcp:
command: "npx"
args: ["-y", "@brilliant-hq/mcp"] {
"McpServers": {
"design-brilliant-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@brilliant-hq/mcp"
]
}
}
} assistant mcp add design-brilliant-mcp -t stdio -c npx -a -y @brilliant-hq/mcp
{
"mcpServers": {
"design-brilliant-mcp": {
"command": "npx",
"args": [
"-y",
"@brilliant-hq/mcp"
]
}
}
} 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.
- 21 Sept 26 +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.
- 19 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 +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.
- 10 Sept 26 +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.
- 8 Sept 26 +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.
- 6 Sept 26 +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.
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 21 Sept 2026 · Analysed npm/@brilliant-hq/mcp@0.1.6
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 1 package
| Packages resolved | 1 |
|---|---|
| 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 →
The sandbox run completed and this package exposed no tools.
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.