Tailwind V4 Upgrade Blocker Lint MCP server

by jmshinhwa·io.github.jmshinhwa/tailwind-v4-upgrade-blocker-lint·v1.0.1

19 rules that find the Tailwind v3 syntax Tailwind v4 removed or silently redefined, in the file you

A89/100grade A

What users say

No reviews yet

Safety scan

A89/100

Adoption

New

0 stars

Reviews

Nobody has reviewed Tailwind V4 Upgrade Blocker Lint yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

No tool declarations could be read from the package source. They show once the server is installed.

scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it

no findings

Code scan6 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 0 days ago15/15
Maintainer identityregistry namespace matches repository owner6/10

Overall 89/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

Runs npx -y @readystack/tailwind-v4-upgrade-blocker-lint on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add tailwind-v4-upgrade-blocker-lint -- npx -y @readystack/tailwind-v4-upgrade-blocker-lint

Is Tailwind V4 Upgrade Blocker Lint MCP server safe?: Yes, by our scan: it is graded A (89/100). Read the Tailwind V4 Upgrade Blocker Lint safety report
How do I install Tailwind V4 Upgrade Blocker Lint?: It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does Tailwind V4 Upgrade Blocker Lint need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Tailwind V4 Upgrade Blocker Lint maintained?: The last commit was in the last day (2026-09-19). The latest release is v1.0.1.