# io.github.vola-trebla/tailwind-context-resolver-mcp (npm · tailwind-context-resolver-mcp)

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

- Trust score: 67/100 (medium)
- Change this week: +21
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `tailwind-context-resolver-mcp`: 67/100 (this document), [markdown](https://verifymcp.io/servers/vola-trebla-tailwind-context-resolver-mcp/tailwind-context-resolver-mcp.md), [page](https://verifymcp.io/servers/vola-trebla-tailwind-context-resolver-mcp/tailwind-context-resolver-mcp)

## Channel facts

- Registry: `npm`
- Package: `tailwind-context-resolver-mcp`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 89/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (163 of 168), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (163 of 168), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 74 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 716 tokens (~102/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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

### Claude

```bash
claude mcp add vola-trebla-tailwind-context-resolver-mcp -- npx -y tailwind-context-resolver-mcp
```

### Codex

```bash
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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add vola-trebla-tailwind-context-resolver-mcp --command npx --arg -y --arg tailwind-context-resolver-mcp
```

### Hermes

```yaml
mcp_servers:
  vola-trebla-tailwind-context-resolver-mcp:
    command: "npx"
    args: ["-y", "tailwind-context-resolver-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "vola-trebla-tailwind-context-resolver-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "tailwind-context-resolver-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 67, +62)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional] Licence: MIT

### 2026-07-31 (score 5, −23)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 28, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-27 (score 46)

First indexed and scored.

## MCP tools (7)

### `resolve_theme_tokens` (~128 tokens)

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

Input parameters:

- `config_path` (string, required): Absolute path to tailwind.config.js or tailwind.config.ts
- `filter` (string): Optional substring filter on token names
- `namespace` (string, required): Dot-path into the theme (e.g. 'colors', 'colors.brand', 'spacing')

### `validate_class_string` (~132 tokens)

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.

Input parameters:

- `class_string` (string, required): Space-separated Tailwind class string to validate
- `config_path` (string, required): Absolute path to tailwind.config.js or tailwind.config.ts

### `detect_css_conflicts` (~91 tokens)

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.

Input parameters:

- `class_string` (string, required): Space-separated Tailwind class string to check for conflicts
- `config_path` (string, required): Absolute path to tailwind.config.js or tailwind.config.ts

### `get_config_summary` (~70 tokens)

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.

Input parameters:

- `config_path` (string, required): Absolute path to tailwind.config.js or tailwind.config.ts

### `resolve_v4_theme_variables` (~85 tokens)

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(...)).

Input parameters:

- `css_path` (string, required): Absolute path to the CSS file containing the @theme or @import "tailwindcss" directives

### `audit_theme_usage` (~96 tokens)

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.

Input parameters:

- `css_path` (string, required): Absolute path to the CSS file containing the @theme blocks
- `project_root` (string, required): Absolute path to the project root directory
- `scan_dirs` (array): Optional array of subdirectories to scan (defaults to ["src"])

### `simulate_jit_compilation` (~114 tokens)

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.

Input parameters:

- `class_string` (string, required): 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)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/vola-trebla-tailwind-context-resolver-mcp/tailwind-context-resolver-mcp#diagnostics

## Score history

- 2026-08-03: 67
- 2026-08-02: 67
- 2026-08-01: 5
- 2026-07-31: 5
- 2026-07-30: 28
- 2026-07-28: 46
- 2026-07-27: 46

## Links

- npm package: https://www.npmjs.com/package/tailwind-context-resolver-mcp
- Socket report: https://socket.dev/npm/package/tailwind-context-resolver-mcp
- Repository: https://github.com/vola-trebla/tailwind-context-resolver-mcp
- Changelog RSS feed: https://verifymcp.io/servers/vola-trebla-tailwind-context-resolver-mcp/tailwind-context-resolver-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/vola-trebla-tailwind-context-resolver-mcp/tailwind-context-resolver-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/vola-trebla-tailwind-context-resolver-mcp/tailwind-context-resolver-mcp