io.github.Halo-design-system/halo-ds
NPM · HALO-DS
Props, examples, design tokens and page blocks for the Halo React design system.
Available components
Last scanned (6 hours 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 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- 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 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 491 tokens (~61/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.4.0 → 0.4.1 functional
- 1 Nov 26 68
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 5 Nov 2026 · Analysed npm/halo-ds@0.4.1
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 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
find_component ~48
Find the right Halo component for a need, like "pick a date range", "confirm before deleting" or "show a status".
| Name | Type | Req | Description |
|---|---|---|---|
| need | string | yes | What the UI needs to do |
No output schema declared.
No examples provided.
get_block ~55
The full, working code of one Halo block, like "sign-in", "dashboard" or "settings", to start a screen from.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The block, like "sign-in" or "Customers table" |
No output schema declared.
No examples provided.
get_component ~78
Everything about one Halo component: import line, when to use it, do's and don'ts, how it compares with similar components, every prop, and working code examples.
| Name | Type | Req | Description |
|---|---|---|---|
| examples | boolean | – | Include code examples (default true) |
| name | string | yes | The component, like "Button", "date-picker" or "DataTable" |
No output schema declared.
No examples provided.
get_setup_and_rules ~36
How to install and set up Halo, and the rules for using its components well. Read this first when building UI with Halo.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_skill ~84
Halo's skill files: how to build, review, theme and migrate UI with Halo, with topic guides (components, design, layout, copy, accessibility, a review checklist) and worked examples. Call with no file to list them.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | – | A path or name from the list, like "skills/build-ui/SKILL.md" or "design" |
No output schema declared.
No examples provided.
get_tokens ~65
Halo design tokens (CSS variables) for colour, spacing, radius, type and layout, with light and dark values. Use them instead of hard-coded values.
| Name | Type | Req | Description |
|---|---|---|---|
| search | string | – | Part of a name, like "text", "surface", "spacing" or "radius" |
No output schema declared.
No examples provided.
list_blocks ~42
Ready-made page sections built from Halo components, like sign in, a dashboard, a settings page or pricing. Start a screen from one of these instead of from scratch.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_components ~22
Every Halo component, grouped, with a one-line description of each.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.Halo-design-system/halo-ds MCP server?
io.github.Halo-design-system/halo-ds runs locally as an npm package, launched with npx -y halo-ds 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 · halo-ds
claude mcp add halo-design-system-halo-ds -- npx -y halo-ds mcp
What is the io.github.Halo-design-system/halo-ds MCP server?
io.github.Halo-design-system/halo-ds is an MCP server listed in the public MCP registry as io.github.Halo-design-system/halo-ds. Props, examples, design tokens and page blocks for the Halo React design system. This page covers its npm package (halo-ds).
Is the io.github.Halo-design-system/halo-ds MCP server safe to use?
io.github.Halo-design-system/halo-ds scores 70 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. 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 io.github.Halo-design-system/halo-ds MCP server expose?
io.github.Halo-design-system/halo-ds exposes 8 tools: get_setup_and_rules, list_components, find_component, get_component, list_blocks, and 3 more. Their descriptions and schemas cost roughly 430 tokens of context every time the server is loaded.
Is the io.github.Halo-design-system/halo-ds MCP server still maintained?
io.github.Halo-design-system/halo-ds 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 io.github.Halo-design-system/halo-ds MCP server under?
io.github.Halo-design-system/halo-ds 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 io.github.Halo-design-system/halo-ds MCP server?
VerifyMCP ran 16 checks on io.github.Halo-design-system/halo-ds, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.