Basiiik
NPM · @BASIIIK/MCP
Design system for coding agents: component specs, rules, tokens, icons and checked React snippets.
Available components
Last scanned (30 minutes ago)
Scores higher than 39% of npm servers
Category Developer Tools
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 Security98
- 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
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 9 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 3017 tokens (~30/item across 98 items; 9 tools + 89 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 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.
- 4 Nov 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.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Schema quality: 2639 → 3017 ▼ functional
- Package version: 0.6.0 → 0.8.0 functional
- Package version: 0.6.0 → 0.7.0 functional
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 64
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 6 Nov 2026 · Analysed npm/@basiiik/mcp@0.8.0
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 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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 →
get_component Get component spec ~106
Full spec for one component: when to use it, when not to, React props and their allowed values, accessibility rules, Figma variants and the tokens it uses. Accepts a slug, name or React component name.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | – | e.g. "button", "Text Field", "TextField" |
| id | string | – | Alias of "component" |
| name | string | – | Alias of "component" |
| slug | string | – | Alias of "component" |
No output schema declared.
No examples provided.
get_component_snippet Get component snippet ~147
Generate an import and JSX usage snippet. Props are validated against the real component API, so invalid props or values return an error listing what is allowed, and a required prop you leave out (such as aria-label on IconButton) is filled with its example value and listed in the notes, so you always get code to adapt.
| Name | Type | Req | Description |
|---|---|---|---|
| children | string | – | Text content, for components that take children |
| component | string | – | e.g. "modal", "Text Field" |
| id | string | – | Alias of "component" |
| name | string | – | Alias of "component" |
| props | object | – | – |
| slug | string | – | Alias of "component" |
No output schema declared.
No examples provided.
get_design_system_guide Design system guide ~39
The rules for generating UI with Basiiik: components first, tokens only, theming, accessibility. Read this before writing UI code.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_icon Get icon ~104
One icon: its SVG, React import and usage, when to use it and when not to, and accessibility notes. Accepts a name ("trash"), a component name ("TrashIcon") or a loose phrase.
| Name | Type | Req | Description |
|---|---|---|---|
| icon | string | – | e.g. "trash", "TrashIcon", "arrow right" |
| id | string | – | Alias of "icon" |
| name | string | – | Alias of "icon" |
| slug | string | – | Alias of "icon" |
No output schema declared.
No examples provided.
get_token Get one token ~89
One token by dotted name ("color.text.primary") or CSS variable ("--color-text-primary" or "var(--color-text-primary)").
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Alias of "token" |
| name | string | – | Alias of "token" |
| slug | string | – | Alias of "token" |
| token | string | – | e.g. "color.text.primary" or "--color-text-primary" |
No output schema declared.
No examples provided.
list_components List components ~53
List Basiiik components (88). Filter by category (actions, agents, data-display, feedback, inputs, navigation, overlays) or implementation status.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
list_tokens List design tokens ~84
List tokens with their CSS variable and Light and Dark values. Filter by layer (semantic tokens are what product code should use), type, dotted-name prefix such as "color.text", or free-text search.
| Name | Type | Req | Description |
|---|---|---|---|
| layer | string | – | – |
| limit | integer | – | – |
| prefix | string | – | – |
| search | string | – | – |
| type | string | – | – |
No output schema declared.
No examples provided.
search_components Search components ~55
Find the right component for a need, e.g. "confirm destructive action" or "show progress". Ranks by name, summary and when-to-use guidance.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
search_icons Search icons ~122
Find an icon for a need or a word, e.g. "delete", "go back" or "warning" (52 icons, 16px outline). Matches names, synonyms and use text. Use this instead of drawing or inventing SVGs. Leave query empty and pass a category (actions, navigation, objects, status) to list one category.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | Default 8 for a query; with no query, every icon (or every icon of the category) |
| query | string | – | – |
No output schema declared.
No examples provided.
How do I install the Basiiik MCP server?
Basiiik runs locally as an npm package, launched with npx -y @basiiik/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 · @basiiik/mcp
claude mcp add shubhankarsd-basiiik -- npx -y @basiiik/mcp
What is the Basiiik MCP server?
Basiiik is an MCP server listed in the public MCP registry as io.github.shubhankarsd/basiiik. Design system for coding agents: component specs, rules, tokens, icons and checked React snippets. This page covers its npm package (@basiiik/mcp).
Is the Basiiik MCP server safe to use?
Basiiik scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 November 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 Basiiik MCP server expose?
Basiiik exposes 9 tools: get_design_system_guide, list_components, search_components, get_component, get_component_snippet, and 4 more. Their descriptions and schemas cost roughly 799 tokens of context every time the server is loaded.
Is the Basiiik MCP server still maintained?
Basiiik is still listed as active in the MCP registry. We last reached this channel on 6 November 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 Basiiik MCP server under?
Basiiik declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Basiiik MCP server?
VerifyMCP ran 15 checks on Basiiik, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Basiiik: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.