Tailwind Shades
NPM · TAILWINDSHADES-MCP · 2 COMPONENTS
Tailwind CSS palettes (50-950) from any color, the closest Tailwind color, and Tailwind's defaults
Available components
Last scanned (19 hours ago)
Scores higher than 98% 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
- 0 of 5 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to bourhaouta/vscode-tailwindshades). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 22 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1209 tokens (~241/item across 5 items; 5 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 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 current MCP spec version (2026-07-28).Pass
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.
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 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.
- 27 Oct 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.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Analysed npm/tailwindshades-mcp@1.6.0
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 | bourhaouta/vscode-tailwindshades |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/bourhaouta/vscode-tailwindshades/.github/workflows/release.yml@refs/tags/v1.6.0 |
| Rekor log index | 3239240299 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:444281dcb3a654fd2c77170e22c385f32fb659cc99afac52be16983dad402f4a61bc7fe76bb65ff6d128b9c3ec88c6ac42c190d887edbfa901460c419 |
Background: How many MCP packages publish verified provenance →
Dependencies 5 packages
| Packages resolved | 5 |
|---|---|
| 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 →
convert_color Convert a color ~119
Converts any CSS color to oklch(), hex and rgb, formatted like Tailwind (oklch() is what Tailwind v4 uses). Colors outside a format are mapped into it: oklch() to Display P3 like Tailwind's palette, hex and rgb to sRGB. Use it for one value; to add a color with all its shades, call generate_palette instead.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | yes | Any CSS color: hex (#db4d53), rgb(), hsl(), oklch() or a named color |
| Name | Type | Req | Description |
|---|---|---|---|
| hex | string | yes | e.g. #db4d53 |
| oklch | string | yes | e.g. oklch(61.6% 0.177 21.62) |
| rgb | string | yes | e.g. rgb(219, 77, 83) |
No examples provided.
find_closest_tailwind_color Find the closest Tailwind color ~135
Finds the shade in Tailwind's default palette that looks most like a given color, e.g. #db4d53 -> red-500. Use it to pick an existing Tailwind class (bg-red-500) instead of an arbitrary value. If the difference is visible, use generate_palette to add the exact color as a custom palette instead.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | yes | Any CSS color: hex (#db4d53), rgb(), hsl(), oklch() or a named color |
| tailwindVersion | number | – | The project's Tailwind CSS major version. Defaults to 4 |
| Name | Type | Req | Description |
|---|---|---|---|
| className | string | yes | Color part of a utility class, e.g. "red-400" for bg-red-400 |
| distance | number | yes | OKLab distance: 0 is identical, under 0.02 is hard to see |
| input | object | yes | The input color |
| name | string | yes | Tailwind color name, e.g. "red" |
| shade | number | yes | Closest shade, e.g. 500 |
| tailwindValue | object | yes | Tailwind's value for that shade |
| tailwindVersion | number | yes | – |
| visiblyDifferent | boolean | yes | True when the Tailwind shade looks different from the input |
No examples provided.
generate_palette Generate a Tailwind palette ~456
Generates a full Tailwind CSS palette (50-950) from one color, ready to paste. Call it whenever you add a color to a Tailwind theme (e.g. "add a brand color #db4d53"), instead of writing a single variable or inventing shades. The input color stays exactly at its best-fit shade, and the other shades follow the closest Tailwind color, so they look like Tailwind's own.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | yes | Any CSS color: hex (#db4d53), rgb(), hsl(), oklch() or a named color |
| format | string | – | Color format. Defaults to oklch for v4 and hex for older versions |
| name | string | – | Color name used in the code, e.g. "brand". Defaults to the closest Tailwind color, which replaces Tailwind's own palette of that name (e.g. red), so pass a name unless that is what the user wants |
| output | string | – | theme: a v4 @theme block for the main CSS file. config: an object for theme.extend.colors in tailwind.config.js. css: plain CSS variables. live (v4 only): for a color picked at runtime (user, tenant… |
| plain | boolean | – | With output live or shopify: a plain :root block instead of @theme, for projects without Tailwind (like the Dawn theme) |
| semantic | boolean | – | With output live or shopify: also add --color-<name>-foreground for text on the color: white or the darkest shade, whichever contrasts more, following the runtime color |
| tailwindVersion | number | – | The project's Tailwind CSS major version. Defaults to 4 |
| Name | Type | Req | Description |
|---|---|---|---|
| avoid | object | – | White text on the input color, when it fails WCAG AA |
| closestTailwindColor | string | yes | Tailwind color whose curve the palette follows |
| code | string | yes | The palette as code, ready to paste |
| format | string | yes | – |
| inputShade | number | yes | Shade that holds the input color unchanged, e.g. 500 |
| name | string | yes | – |
| output | string | yes | – |
| readablePairs | array | – | Text and background pairs that pass WCAG AA. Use them for text and buttons in this color. Not for live and shopify outputs, whose shades change at runtime |
| replacesTailwindColor | boolean | yes | True when the code replaces a default Tailwind palette (default color name, theme or config output) |
| shades | array | yes | – |
| tailwindVersion | number | yes | – |
No examples provided.
get_tailwind_palette Get Tailwind's default colors ~144
Looks up Tailwind's own default colors, exactly as Tailwind defines them: a whole color (e.g. "blue", all shades) or one shade (e.g. "slate-500"), for Tailwind v4, v3, v2 or v1. Use it instead of writing default Tailwind color values from memory. Values are oklch() in v4 and hex in older versions.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | A default Tailwind color, like "blue", or one shade of it, like "blue-500" |
| tailwindVersion | number | – | The project's Tailwind CSS major version. Defaults to 4 |
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Tailwind color name, e.g. "blue" |
| shades | array | yes | All shades, or only the one asked for |
| tailwindVersion | number | yes | – |
No examples provided.
list_tailwind_colors List Tailwind's default colors ~93
Lists the names of Tailwind's default colors for a Tailwind version (e.g. red, slate, mauve in v4), with the shades each one has and its 500 value as a sample. Use it to see which colors exist before calling get_tailwind_palette or picking a utility class.
| Name | Type | Req | Description |
|---|---|---|---|
| tailwindVersion | number | – | The project's Tailwind CSS major version. Defaults to 4 |
| Name | Type | Req | Description |
|---|---|---|---|
| colors | array | yes | – |
| shades | array | yes | Shades every color has, e.g. 50 to 950 |
| tailwindVersion | number | yes | – |
No examples provided.
How do I install the Tailwind Shades MCP server?
Tailwind Shades runs locally as an npm package, launched with npx -y tailwindshades-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 · tailwindshades-mcp
claude mcp add bourhaouta-tailwindshades -- npx -y tailwindshades-mcp
What is the Tailwind Shades MCP server?
Tailwind Shades is an MCP server listed in the public MCP registry as io.github.bourhaouta/tailwindshades. Tailwind CSS palettes (50-950) from any color, the closest Tailwind color, and Tailwind's defaults. This page covers its npm package (tailwindshades-mcp).
Is the Tailwind Shades MCP server safe to use?
Tailwind Shades scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 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 Tailwind Shades MCP server expose?
Tailwind Shades exposes 5 tools: generate_palette, find_closest_tailwind_color, get_tailwind_palette, list_tailwind_colors, convert_color. Their descriptions and schemas cost roughly 947 tokens of context every time the server is loaded.
Is the Tailwind Shades MCP server still maintained?
Tailwind Shades is still listed as active in the MCP registry. We last reached this channel on 4 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 Tailwind Shades MCP server under?
Tailwind Shades declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.