Box Kite
NPM · @BOX-KITE/MCP
Box Kite's React styling engine as tools: props, components, and whether a value writes CSS.
Available components
Last scanned (13 hours ago)
Scores higher than 93% 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 & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to box-kite/box-kite). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1053 tokens (~175/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 +15
- Tool safety: pass → unverified ▼ security
- Stability: 0.67 → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 2.2.18 → 2.3.0 functional
- 3 Nov 26 +1
- Malware scan: unverified → pass ▲ security
- Package version: 2.2.16 → 2.2.18 functional
- Package version: 2.2.16 → 2.2.17 functional
- 2 Nov 26 −15
- Known CVEs: pass → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Dependency health: 0.85 → unverified ▼ functional
- Package version: 2.2.13 → 2.2.16 functional
- Package version: 2.2.13 → 2.2.15 functional
- Package version: 2.2.13 → 2.2.14 functional
- 1 Nov 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.
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −4
- Malware scan: pass → unverified ▼ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
- Package version: 2.2.12 → 2.2.13 functional
- 29 Oct 26 0
- Tool safety: pass → unverified ▼ security
- Stability: 0.47 → unverified ▼ security
- Known CVEs: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → 0.86 ▲ functional
- Dependency health: unverified → 0.85 ▲ functional
- Package version: 2.2.10 → 2.2.12 functional
- Package version: 2.2.10 → 2.2.11 functional
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 5 Nov 2026 · Analysed npm/@box-kite/mcp@2.3.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | box-kite/box-kite |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/box-kite/box-kite/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3689815422 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:730e879f7e7718aa6e6249e62d87655f3559bf535ea53cf8be61b64ef99ba0d2b888cac3f6a22281050019bf28547dad7cb9f5de2663bbca17a2e47f7 |
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 →
check_styles Check props against the engine ~121
Run a prop bag through the real styling engine and get back the CSS each prop writes — or why it wrote none. This is the only way to be sure: an unknown prop and an unaccepted value both produce no rule and no class name, with no warning anywhere. Use it on any prop bag you were not certain about, especially numbers and colour tokens.
| Name | Type | Req | Description |
|---|---|---|---|
| props | object | yes | The props as JSON, exactly as written: {"p": 4, "bgColor": "blue-550", "hover": {"opacity": 1}}. |
No output schema declared.
No examples provided.
get_blocks Installable blocks ~73
Whole sections rather than atoms — a data-grid page, a settings form, a dashboard shell — installed by the shadcn CLI, which also installs the package. Reach for one before composing a large surface by hand.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | A block name for its files and dependencies. Leave out to list them. |
No output schema declared.
No examples provided.
get_component Box Kite component ~112
One component's whole contract: its props and their defaults, its sub-parts, its keyboard map and the ARIA it writes. Ask before composing a Dialog, Menu, Tabs, Combobox, DataGrid or any other behaviour component — the accessible mechanics are already in it.
| Name | Type | Req | Description |
|---|---|---|---|
| include | array | – | Only these sections. Leave out for all of them. |
| name | string | yes | Component name, e.g. "Tabs", "DataGrid", "Popover". A part name works too ("Tabs.Tab"). |
No output schema declared.
No examples provided.
get_props Box style props ~238
The full record for named style props: the CSS they write, every value they accept, and a measured example — plus, for a numeric prop, the scale measured at 1/2/4/8, because the dividers differ per prop (235 props in all). Nesting keys are answered here too: hover, focus, focusVisible, hasFocus, active, valid, hasValid, invalid, hasInvalid, optional, hasChecked, hasRequired, hasDisabled, visited, target, open, placeholderShown, autofill, inRange, outOfRange, inert, rtl, ltr, indeterminate, checked, required, disabled, selected, before, after, placeholder, selection, marker, firstLine, firstLetter, backdrop, fileButton, sm, md, lg, xl, xxl, pointerCoarse, pointerFine, motionReduce, forcedColors, contrastMore, cq, dataAttr, ariaAttr, has, not, nth, group, peer, theme, startingStyle.
| Name | Type | Req | Description |
|---|---|---|---|
| names | array | yes | Prop names, e.g. ["fontSize", "borderRadius", "bgColor"]. |
No output schema declared.
No examples provided.
get_rules Box Kite rules ~79
The 55 rules this library is written by — where the element comes from, where HTML attributes go, how a layer is anchored, how a theme scopes. With no arguments it lists all 55 headings; pass numbers for the ones you need in full.
| Name | Type | Req | Description |
|---|---|---|---|
| numbers | array | – | Rule numbers to read in full. Leave out for the index. |
No output schema declared.
No examples provided.
search_docs Search Box Kite ~116
Find the prop, component, nesting key or rule for what you are trying to build. Ranked across all four, so a goal ("fade in on mount", "sticky header", "right-to-left") finds the answer without knowing its name. Start here.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Narrow to one corpus. Leave out to search all four. |
| limit | integer | – | How many hits (default 12). |
| query | string | yes | What the UI should do, a CSS property, or a name you half-remember. |
No output schema declared.
No examples provided.
How do I install the Box Kite MCP server?
Box Kite runs locally as an npm package, launched with npx -y @box-kite/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 · @box-kite/mcp
claude mcp add box-kite-mcp -- npx -y @box-kite/mcp
What is the Box Kite MCP server?
Box Kite is an MCP server listed in the public MCP registry as io.github.box-kite/mcp. Box Kite's React styling engine as tools: props, components, and whether a value writes CSS. This page covers its npm package (@box-kite/mcp).
Is the Box Kite MCP server safe to use?
Box Kite scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 Box Kite MCP server expose?
Box Kite exposes 6 tools: search_docs, get_props, get_component, check_styles, get_rules, get_blocks. Their descriptions and schemas cost roughly 739 tokens of context every time the server is loaded.
Is the Box Kite MCP server still maintained?
Box Kite is still listed as active in the MCP registry. We last reached this channel on 5 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 Box Kite MCP server under?
Box Kite declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.