Vsix Publish Lint runs on your own machine — the client starts it, so there is no endpoint to ping. 62 installs a week from npm. Last commit 2 Nov 2026.
Find the package.json lines that stop vsce before you run the release build
Today is the operative word: we check Vsix Publish 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 vsix-publish-lint -- npx -y @readystack/vsix-publish-lint
{
"mcpServers": {
"vsix-publish-lint": {
"command": "npx",
"args": [
"-y",
"@readystack/vsix-publish-lint"
]
}
}
}
[mcp_servers.vsix-publish-lint]
command = "npx"
args = ["-y", "@readystack/vsix-publish-lint"]
{
"mcpServers": {
"vsix-publish-lint": {
"command": "npx",
"args": [
"-y",
"@readystack/vsix-publish-lint"
]
}
}
}
{
"servers": {
"vsix-publish-lint": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@readystack/vsix-publish-lint"
]
}
}
}
Find the lines your bank will refuse before you send the batch
Finds the credential in your release workflow that expires before your next release
Finds the lines KSeF will reject in a Polish structured invoice XML, before you send it
Finds the lines that make Google Play reject your release - target API below 36, Billing Library bel
16 checks on a system-security-plan JSON, in your editor, before a validator returns the package
Finds the coverage gates in your repo that can never fail a build
Local-first MCP that scores your codebase's build readiness. Your code never leaves your machine.
Find the cheapest AI model that passes your tests: audit repo models, build evals, routing, sizing
Answers built from our own checks of this server.