Tailwind V4 Upgrade Blocker Lint runs on your own machine — the client starts it, so there is no endpoint to ping. 158 installs a week from npm. Last commit 22 Sep 2026.
19 rules that find the Tailwind v3 syntax Tailwind v4 removed or silently redefined, in the file you
Today is the operative word: we check Tailwind V4 Upgrade Blocker Lint every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add tailwind-v4-upgrade-blocker-lint -- npx -y @readystack/tailwind-v4-upgrade-blocker-lint
{
"mcpServers": {
"tailwind-v4-upgrade-blocker-lint": {
"args": [
"-y",
"@readystack/tailwind-v4-upgrade-blocker-lint"
],
"command": "npx"
}
}
}
[mcp_servers.tailwind-v4-upgrade-blocker-lint]
command = "npx"
args = ["-y", "@readystack/tailwind-v4-upgrade-blocker-lint"]
{
"mcpServers": {
"tailwind-v4-upgrade-blocker-lint": {
"args": [
"-y",
"@readystack/tailwind-v4-upgrade-blocker-lint"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"tailwind-v4-upgrade-blocker-lint": {
"args": [
"-y",
"@readystack/tailwind-v4-upgrade-blocker-lint"
],
"command": "npx"
}
}
}
Reads security headers and CSP line by line in your config file and names the lines that silently do
Finds the Java lines the new LTS removed — 18 rules; 23 findings in one 64-line fixture
Names every schedule line in the file you have open that fires at the wrong hour, twice, or never at
Finds the coverage gates in your repo that can never fail a build
Find the package.json lines that stop vsce before you run the release build
Finds the credential in your release workflow that expires before your next release
Finds retired API versions and removed sfdx force:* commands in your DX repo before a deploy or a CI
32 checks for Angular APIs that were removed or deprecated, plus the support window on your version
Answers built from our own checks of this server.