Coverage Gate Lint runs on your own machine — the client starts it, so there is no endpoint to ping. 143 installs a week from npm. Last commit 2 Nov 2026.
Finds the coverage gates in your repo that can never fail a build
Today is the operative word: we check Coverage Gate 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 coverage-gate-lint -- npx -y @readystack/coverage-gate-lint
{
"mcpServers": {
"coverage-gate-lint": {
"command": "npx",
"args": [
"-y",
"@readystack/coverage-gate-lint"
]
}
}
}
[mcp_servers.coverage-gate-lint]
command = "npx"
args = ["-y", "@readystack/coverage-gate-lint"]
{
"mcpServers": {
"coverage-gate-lint": {
"command": "npx",
"args": [
"-y",
"@readystack/coverage-gate-lint"
]
}
}
}
{
"servers": {
"coverage-gate-lint": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@readystack/coverage-gate-lint"
]
}
}
}
Find the cheapest AI model that passes your tests: audit repo models, build evals, routing, sizing
Finds the credential in your release workflow that expires before your next release
Team secrets your AI agent can use but never read: encrypted in the repo, value-blind tools.
Local-first MCP that scores your codebase's build readiness. Your code never leaves your machine.
Names every image, font, badge and embed in your docs that sends an EU reader's IP outside the EEA
Find what a repository's CI is missing, and which security checks cannot fail the build.
Skills and Scars for AI agents - your agent records its failures and never repeats them.
Build a branch name from an issue title and number, in the repo's naming convention.
Answers built from our own checks of this server.