io.github.ConanMcN/fragments-mcp
NPM · @FRAGMENTS-SDK/MCP · SCANNED SEP 21
Design system MCP with 9 tools for component discovery, rendering, and a11y auditing
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 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
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency58
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to ConanMcN/fragments). View diagnostics → Pass
- License check failed: the license (FSL-1.1-MIT) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 74 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1131 tokens (~188/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 Management97
- Stability observed for 29 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 6 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
How do I install the io.github.ConanMcN/fragments-mcp server?
io.github.ConanMcN/fragments-mcp runs locally as an npm package, launched with npx -y @fragments-sdk/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 · @fragments-sdk/mcp
claude mcp add conanmcn-fragments-mcp -- npx -y @fragments-sdk/mcp
{
"mcpServers": {
"conanmcn-fragments-mcp": {
"command": "npx",
"args": [
"-y",
"@fragments-sdk/mcp"
]
}
}
} {
"servers": {
"conanmcn-fragments-mcp": {
"command": "npx",
"args": [
"-y",
"@fragments-sdk/mcp"
]
}
}
} codex mcp add conanmcn-fragments-mcp -- npx -y @fragments-sdk/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"conanmcn-fragments-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@fragments-sdk/mcp"
],
"enabled": true
}
}
} openclaw mcp add conanmcn-fragments-mcp --command npx --arg -y --arg @fragments-sdk/mcp
mcp_servers:
conanmcn-fragments-mcp:
command: "npx"
args: ["-y", "@fragments-sdk/mcp"] {
"McpServers": {
"conanmcn-fragments-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@fragments-sdk/mcp"
]
}
}
} assistant mcp add conanmcn-fragments-mcp -t stdio -c npx -a -y @fragments-sdk/mcp
{
"mcpServers": {
"conanmcn-fragments-mcp": {
"command": "npx",
"args": [
"-y",
"@fragments-sdk/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 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −2
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −2
- Stability: pass → 0.80 functional
- 8 Sept 26 0
- Stability: 0.97 → pass security
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/@fragments-sdk/mcp@0.5.7
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 | ConanMcN/fragments |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/ConanMcN/fragments/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 941977028 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:06414afd9c52e166d8e86e2f716551232dcc28edbddad0339a7c4220fe5b6f8ac953a465fe27af542b6a4cf725c8a1945d73d14179bbe26c3556e13ad |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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 →
fragments_blocks ~192
Search and retrieve composition blocks — named patterns showing how design system components wire together for common use cases (e.g., "Login Form", "Settings Page"). Returns the block with its code pattern.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category (e.g., "authentication", "marketing", "dashboard", "settings", "ecommerce", "ai") |
| component | string | – | Filter blocks that use a specific component (e.g., "Button") |
| limit | number | – | Maximum number of blocks to return (default: all matching) |
| name | string | – | Exact block name to retrieve (e.g., "Login Form") |
| search | string | – | Free-text search across block names, descriptions, tags, and components |
| verbosity | string | – | Response detail level: "compact" (no code), "standard" (default, code preview for long blocks), "full" (full code) |
No output schema declared.
No examples provided.
fragments_discover ~277
Discover components in the design system. Use with no params to list all components. Use 'useCase' for AI-powered suggestions. Use 'component' to find alternatives. Use 'compact' for a token-efficient overview.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category (e.g., "actions", "forms", "layout") |
| compact | boolean | – | If true, returns minimal output (just component names and categories) |
| component | string | – | Component name to find alternatives for (e.g., "Button") |
| format | string | – | Output format for context mode (default: markdown) |
| includeCode | boolean | – | If true, includes code examples for each variant |
| includeRelations | boolean | – | If true, includes component relationships |
| limit | number | – | Maximum number of results to return (default: 10 for useCase mode) |
| search | string | – | Search term to filter by name, description, or tags |
| status | string | – | Filter by component status |
| useCase | string | – | Description of what you want to build — returns ranked suggestions (e.g., "form for user email input", "button to submit data") |
| verbosity | string | – | Response detail level: "compact" (names only), "standard" (default), "full" (everything including code) |
No output schema declared.
No examples provided.
fragments_graph ~160
Query the component relationship graph. Understand dependencies, impact analysis, composition trees, alternatives, and design system health. Use "health" for an overview, "dependencies"/"dependents" for composition and declared relationships (not code-level imports), "impact" for change analysis, "composition" for compound component trees.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | – | Component name (required for most modes) |
| edgeTypes | array | – | Filter by edge types (imports, hook-depends, renders, composes, parent-of, alternative-to, sibling-of) |
| maxDepth | number | – | Max traversal depth for impact mode (default: 3) |
| mode | string | yes | Query mode |
| target | string | – | Target component for "path" mode |
No output schema declared.
No examples provided.
fragments_implement ~143
One-shot implementation helper. Describe what you want to build and get everything needed in a single call: best-matching component(s) with full props and code examples, relevant composition blocks, and applicable CSS tokens. Saves multiple round-trips.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of components to return (default: 5) |
| useCase | string | yes | What you want to implement (e.g., "login form", "data table with sorting", "streaming chat messages") |
| verbosity | string | – | Response detail level: "compact" (names only), "standard" (default), "full" (all props + examples + full block code) |
No output schema declared.
No examples provided.
fragments_inspect ~209
Get detailed information about a specific component: props, usage guidelines, code examples, accessibility — all in one call. Use 'fields' to request only specific data for token efficiency.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | yes | Component name (e.g., "Button", "Input") |
| fields | array | – | Specific fields to return (e.g., ["meta", "guidelines.when", "contract.propsSummary", "props", "examples"]). If omitted, returns everything. Supports dot notation. Aliases: "usage" → "guidelines". |
| maxExamples | number | – | Maximum number of code examples to return (default: all) |
| maxLines | number | – | Maximum lines per code example (truncates longer examples) |
| variant | string | – | Filter examples to a specific variant name (e.g., "Default", "Primary") |
| verbosity | string | – | Response detail level: "compact" (meta + prop names), "standard" (default), "full" (everything) |
No output schema declared.
No examples provided.
fragments_tokens ~150
List available CSS design tokens (custom properties) by category. Use this when you need to style custom elements or override defaults — no more guessing variable names. Filter by category or search by keyword.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category (e.g., "colors", "spacing", "typography", "surfaces", "shadows", "radius", "borders", "text", "focus", "layout", "code", "component-sizing") |
| limit | number | – | Maximum number of tokens to return per category (default: 25 for search, unlimited for category browsing) |
| search | string | – | Search token names (e.g., "accent", "hover", "padding") |
No output schema declared.
No examples provided.
What is the io.github.ConanMcN/fragments-mcp server?
io.github.ConanMcN/fragments-mcp is listed in the public MCP registry as io.github.ConanMcN/fragments-mcp. Design system MCP with 9 tools for component discovery, rendering, and a11y auditing. This page covers its npm package (@fragments-sdk/mcp).
Is the io.github.ConanMcN/fragments-mcp server safe to use?
io.github.ConanMcN/fragments-mcp scores 85 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. 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 io.github.ConanMcN/fragments-mcp server expose?
io.github.ConanMcN/fragments-mcp exposes 6 tools: fragments_discover, fragments_inspect, fragments_blocks, fragments_tokens, fragments_implement, fragments_graph. Their descriptions and schemas cost roughly 1,131 tokens of context every time the server is loaded.
Is the io.github.ConanMcN/fragments-mcp server still maintained?
io.github.ConanMcN/fragments-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 io.github.ConanMcN/fragments-mcp server under?
io.github.ConanMcN/fragments-mcp declares the FSL-1.1-MIT 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.