Atlas / MCP servers / yajihum / Design System

Design SystemSAFE

mcp/yajihum/design-system
Verdict
SAFE
Grade
B
Trust score
89 /100
Exposed tools
2 2r · 0w · 0d
Transport
stdio
License
—
Stars
25
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

This project includes an MCP (Model Context Protocol) server that provides information about component props and design tokens.

MCP Server Features

The MCP server offers two main tools:

  • getComponentProps: Retrieves information about component properties
  • getTokens: Retrieves design token information from token files

Debugging the MCP Server

To debug the MCP server:

  1. Run the in-memory debug script:
$ deno task debug-mcp

This script:

  • Creates an in-memory client-server connection
  • Makes sample calls to retrieve component props and tokens
  • Displays the results in the console

You can modify the debug script to test different components or specific token requests.

Design Token Generation

Design tokens are stored as JSON files in the src/design-system/tokens directory:

  • color.json: Color palette and theme colors
  • typography.json: Font families, sizes, weights
  • spacing.json: Spacing scale
  • radius.json: Border radius values

Token Generation Process

Tokens are processed using Style Dictionary with the following workflow:

  1. Define token values in JSON files in the tokens directory
  2. Style Dictionary processes these tokens according to the configuration in src/design-system/style-dictionary/config.json
  3. Output formats include:
  4. CSS variables (tokens.css)
  5. JavaScript module (tokens.js)
  6. TypeScript declarations (tokens.d.ts)

To generate tokens:

$ deno task build-tokens

The generated files are placed in the src/design-system/style-dictionary/dist directory and can be imported into your components.

Read from source at commit 87e060715823OBSERVED · 2026-10-09
Advertisement
02

Exposed tools (2)

2 read · 0 write · 0 destructive.

ToolRiskDescription
getComponentPropsread
getTokensread
03

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codePASS
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
none-observed
Network
none-observed
Shell
none-observed
Dependencies
pinned
Secrets in source
none-found

Findings (1)

LOWInventory / provenance · inv.no_license · CWE-1104
Why it matters. no LICENSE file and no repo licence
Fix. add a licence

Gates applied: no_behavioural_pass, no_license.

Audited 2026-10-09 · audit v0.4.1 · source sha 87e060715823full audit observations/trust-audit/mcp-server/yajihum__design-system.json · Report an issue / request a re-scan
04

Audit history

Every audit this server has had. A grade with a past is a grade somebody is still checking.

DateSourceVerdictGradeScoreChange
2026-10-0987e060715823SAFEB89first audit
05

Questions

What tools does Design System expose?

2 in total: 2 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.

Is Design System safe to connect to an agent?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.

What credentials does Design System need?

No credential environment variables were found in its source, so it appears to need none.

How does Design System run?

It speaks stdio, so it runs as a local process your client starts.

How current is this page?

The grade is for one exact copy of the source (87e060715823), read on 2026-10-09. The repository is watched and re-audited when it changes.

Advertisement