io.github.vola-trebla/tailwind-context-resolver-mcp
NPM · TAILWIND-CONTEXT-RESOLVER-MCP · SCANNED SEP 20
Resolves Tailwind CSS design tokens and validates utility classes against the local project config.
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
- 66 of 164 dependencies flagged as unhealthy. View diagnostics → Partial
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 122 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 716 tokens (~102/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 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 7 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
How do I install the io.github.vola-trebla/tailwind-context-resolver-mcp server?
io.github.vola-trebla/tailwind-context-resolver-mcp runs locally as an npm package, launched with npx -y tailwind-context-resolver-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 · tailwind-context-resolver-mcp
claude mcp add vola-trebla-tailwind-context-resolver-mcp -- npx -y tailwind-context-resolver-mcp
{
"mcpServers": {
"vola-trebla-tailwind-context-resolver-mcp": {
"command": "npx",
"args": [
"-y",
"tailwind-context-resolver-mcp"
]
}
}
} {
"servers": {
"vola-trebla-tailwind-context-resolver-mcp": {
"command": "npx",
"args": [
"-y",
"tailwind-context-resolver-mcp"
]
}
}
} codex mcp add vola-trebla-tailwind-context-resolver-mcp -- npx -y tailwind-context-resolver-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vola-trebla-tailwind-context-resolver-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"tailwind-context-resolver-mcp"
],
"enabled": true
}
}
} openclaw mcp add vola-trebla-tailwind-context-resolver-mcp --command npx --arg -y --arg tailwind-context-resolver-mcp
mcp_servers:
vola-trebla-tailwind-context-resolver-mcp:
command: "npx"
args: ["-y", "tailwind-context-resolver-mcp"] {
"McpServers": {
"vola-trebla-tailwind-context-resolver-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"tailwind-context-resolver-mcp"
]
}
}
} assistant mcp add vola-trebla-tailwind-context-resolver-mcp -t stdio -c npx -a -y tailwind-context-resolver-mcp
{
"mcpServers": {
"vola-trebla-tailwind-context-resolver-mcp": {
"command": "npx",
"args": [
"-y",
"tailwind-context-resolver-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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 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 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 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.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 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 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 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 20 Sept 2026 · Analysed npm/tailwind-context-resolver-mcp@0.2.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 164 packages
| Packages resolved | 164 |
|---|---|
| Stale | 66 |
| 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 →
audit_theme_usage ~96
Identifies dead design tokens by scanning the project files. Checks each CSS custom property defined in @theme blocks to see if it is referenced anywhere in the source code.
| Name | Type | Req | Description |
|---|---|---|---|
| css_path | string | yes | Absolute path to the CSS file containing the @theme blocks |
| project_root | string | yes | Absolute path to the project root directory |
| scan_dirs | array | – | Optional array of subdirectories to scan (defaults to ["src"]) |
No output schema declared.
No examples provided.
detect_css_conflicts ~91
Detects conflicting Tailwind utility classes in a className string — e.g. applying both 'flex' and 'grid', or multiple position utilities. Use to prevent silent CSS bugs before generating or reviewing component code.
| Name | Type | Req | Description |
|---|---|---|---|
| class_string | string | yes | Space-separated Tailwind class string to check for conflicts |
| config_path | string | yes | Absolute path to tailwind.config.js or tailwind.config.ts |
No output schema declared.
No examples provided.
get_config_summary ~70
Returns a compact overview of the project's Tailwind configuration: version, prefix, which theme sections have been customized, and what plugins are active. Use first to understand the project's design system before querying specific tokens.
| Name | Type | Req | Description |
|---|---|---|---|
| config_path | string | yes | Absolute path to tailwind.config.js or tailwind.config.ts |
No output schema declared.
No examples provided.
resolve_theme_tokens ~128
Queries the resolved Tailwind CSS theme for a specific namespace and returns all design tokens. Use before generating components to discover what colors, spacing, or font values actually exist in this project. Example namespaces: 'colors', 'colors.brand', 'spacing', 'fontFamily', 'fontSize', 'screens'.
| Name | Type | Req | Description |
|---|---|---|---|
| config_path | string | yes | Absolute path to tailwind.config.js or tailwind.config.ts |
| filter | string | – | Optional substring filter on token names |
| namespace | string | yes | Dot-path into the theme (e.g. 'colors', 'colors.brand', 'spacing') |
No output schema declared.
No examples provided.
resolve_v4_theme_variables ~85
Parses the project's root CSS file (Tailwind CSS v4) and extracts all design tokens defined in @theme blocks. Returns a flat map of CSS custom properties (e.g., --color-primary-500 -> oklch(...)).
| Name | Type | Req | Description |
|---|---|---|---|
| css_path | string | yes | Absolute path to the CSS file containing the @theme or @import "tailwindcss" directives |
No output schema declared.
No examples provided.
simulate_jit_compilation ~114
Validates Tailwind utility classes against the JIT engine by programmatically compiling them. Supports complex arbitrary values, JIT modifiers, and custom plugin classes. Returns the generated CSS rules.
| Name | Type | Req | Description |
|---|---|---|---|
| class_string | string | yes | Space-separated Tailwind class string to compile |
| config_path | string | – | Optional path to tailwind.config.js/ts (for Tailwind v3 custom configs) |
| css_path | string | – | Optional path to the project's CSS entry file (for Tailwind v4 custom theme styles) |
No output schema declared.
No examples provided.
validate_class_string ~132
Validates a Tailwind CSS className string against the project's actual config. Returns valid_classes, invalid_classes (hallucinated tokens), possibly_valid_classes (plugin-generated — cannot verify without PostCSS), and conflict warnings. Handles variants (hover:, dark:, lg:), important (!), opacity modifiers (/50), negative values (-mt-4), and arbitrary values ([32rem]). Use to catch hallucinated design tokens before writing code.
| Name | Type | Req | Description |
|---|---|---|---|
| class_string | string | yes | Space-separated Tailwind class string to validate |
| config_path | string | yes | Absolute path to tailwind.config.js or tailwind.config.ts |
No output schema declared.
No examples provided.
What is the io.github.vola-trebla/tailwind-context-resolver-mcp server?
io.github.vola-trebla/tailwind-context-resolver-mcp is listed in the public MCP registry as io.github.vola-trebla/tailwind-context-resolver-mcp. Resolves Tailwind CSS design tokens and validates utility classes against the local project config. This page covers its npm package (tailwind-context-resolver-mcp).
Is the io.github.vola-trebla/tailwind-context-resolver-mcp server safe to use?
io.github.vola-trebla/tailwind-context-resolver-mcp scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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.vola-trebla/tailwind-context-resolver-mcp server expose?
io.github.vola-trebla/tailwind-context-resolver-mcp exposes 7 tools: resolve_theme_tokens, validate_class_string, detect_css_conflicts, get_config_summary, resolve_v4_theme_variables, and 2 more. Their descriptions and schemas cost roughly 716 tokens of context every time the server is loaded.
Is the io.github.vola-trebla/tailwind-context-resolver-mcp server still maintained?
io.github.vola-trebla/tailwind-context-resolver-mcp is still listed as active in the MCP registry. We last reached this channel on 20 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.vola-trebla/tailwind-context-resolver-mcp server under?
io.github.vola-trebla/tailwind-context-resolver-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.