Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.vola-trebla/tailwind-context-resolver-mcp

NPM · TAILWIND-CONTEXT-RESOLVER-MCP · SCANNED AUG 3

Resolves Tailwind CSS design tokens and validates utility classes against the local project config.

+21 this week 67 Trust /100
Trust breakdown (6 categories)

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 →

Supply Chain Security89
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (163 of 168), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (163 of 168), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · tailwind-context-resolver-mcp

# add to Claude Code
claude mcp add vola-trebla-tailwind-context-resolver-mcp -- npx -y tailwind-context-resolver-mcp
# add to Codex CLI
codex mcp add vola-trebla-tailwind-context-resolver-mcp -- npx -y tailwind-context-resolver-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vola-trebla-tailwind-context-resolver-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "tailwind-context-resolver-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add vola-trebla-tailwind-context-resolver-mcp --command npx --arg -y --arg tailwind-context-resolver-mcp
# ~/.hermes/config.yaml
mcp_servers:
  vola-trebla-tailwind-context-resolver-mcp:
    command: "npx"
    args: ["-y", "tailwind-context-resolver-mcp"]
// mcp.json
{
  "mcpServers": {
    "vola-trebla-tailwind-context-resolver-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "tailwind-context-resolver-mcp"
      ]
    }
  }
}
Changelog

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.

  • 2 Aug 26 +62
    • Provenance: unverified → fail security
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Schema quality: unverified → excellent functional
    • License: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Tool coverage: unverified → 100 functional
    • Licence: MIT functional
  • 31 Jul 26 −23
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −18
    • Malware scan: pass → unverified security
  • 27 Jul 26 46

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 163 packages

163 packages in the resolved dependency tree · 128 deprecated · 64 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 7 exposed · ~716 tokens

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.

Tool Tokens
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.

NameTypeReqDescription
css_pathstringyesAbsolute path to the CSS file containing the @theme blocks
project_rootstringyesAbsolute path to the project root directory
scan_dirsarrayOptional 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.

NameTypeReqDescription
class_stringstringyesSpace-separated Tailwind class string to check for conflicts
config_pathstringyesAbsolute 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.

NameTypeReqDescription
config_pathstringyesAbsolute 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'.

NameTypeReqDescription
config_pathstringyesAbsolute path to tailwind.config.js or tailwind.config.ts
filterstringOptional substring filter on token names
namespacestringyesDot-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(...)).

NameTypeReqDescription
css_pathstringyesAbsolute 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.

NameTypeReqDescription
class_stringstringyesSpace-separated Tailwind class string to compile
config_pathstringOptional path to tailwind.config.js/ts (for Tailwind v3 custom configs)
css_pathstringOptional 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.

NameTypeReqDescription
class_stringstringyesSpace-separated Tailwind class string to validate
config_pathstringyesAbsolute path to tailwind.config.js or tailwind.config.ts

No output schema declared.

No examples provided.