Tailwind V4 Upgrade Blocker Lint runs on your own machine — the client starts it, so there is no endpoint to ping. 135 installs a week from npm. Last commit 2 Nov 2026.
19 rules that find the Tailwind v3 syntax Tailwind v4 removed or silently redefined, in the file you
We read the source, 5 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
этот файл ставится пользователю, но в репозитории его нет
var files = all.filter(function (x) { try { return fs.statSync(path.join(dir, x)).isFile(); } catch (e) { return false; } });
ProcessBuilder pb = new ProcessBuilder(win ? "npx.cmd" : "npx", "-y", NPM, f.toString());
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
o.innerHTML=s+'</table>'};
…S Firebase's defaults, and this list has no **/.* entry. Every dotfile under the public root — .env, .env.production, .npmrc, .git — is uploaded and served.","fix":"Add \"**/.*\" back to the ignore array."},
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
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": {
"command": "npx",
"args": [
"-y",
"@readystack/tailwind-v4-upgrade-blocker-lint"
]
}
}
}
[mcp_servers.tailwind-v4-upgrade-blocker-lint]
command = "npx"
args = ["-y", "@readystack/tailwind-v4-upgrade-blocker-lint"]
{
"mcpServers": {
"tailwind-v4-upgrade-blocker-lint": {
"command": "npx",
"args": [
"-y",
"@readystack/tailwind-v4-upgrade-blocker-lint"
]
}
}
}
{
"servers": {
"tailwind-v4-upgrade-blocker-lint": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@readystack/tailwind-v4-upgrade-blocker-lint"
]
}
}
}
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
18 rules over the accessibility metadata in your .opf: 12 findings in the sample file, 9 of them err
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
Answers built from our own checks of this server.