io.github.jmshinhwa/coverage-gate-lint MCP Server
io.github.jmshinhwa/coverage-gate-lint
What this kind of tool is for
- Automate a build, test, or deployment step you repeat by hand.
- Review or refactor code in an existing repository without leaving your agent.
- Bridge an internal service or CLI into the agent toolset.
How to compare servers like this
- Scope of control:
- Repos and CI are hard to undo; prefer tools that ask before anything irreversible.
- Environment fit:
- Match the runtime it expects (Node, Python, a container) to what you actually run.
- Maintenance signal:
- Check the last-commit date — dev tooling that lags upstream breaks first.
- Config surface:
- Prefer tools whose environment-variable or config keys are documented plainly.
This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.
What is the io.github.jmshinhwa/coverage-gate-lint MCP server?
Finds the coverage gates in your repo that can never fail a build
How to install io.github.jmshinhwa/coverage-gate-lint
Copy-paste configuration for popular MCP clients.
{
"mcpServers": {
"coverage-gate-lint": {
"command": "npx",
"args": [
"-y",
"@readystack/coverage-gate-lint",
"--mcp"
]
}
}
}Related MCP servers
Reads your SECURITY.md against the EU Cyber Resilience Act reporting clock that started on 11 Septem
View repository →19 rules over the user documentation that ships with your product: support-period end date, vulnerab
View repository →Flags the lines in your repo that break the EU Cyber Resilience Act - default passwords, disabled TL
View repository →Names every schedule line in the file you have open that fires at the wrong hour, twice, or never at
View repository →Ten checks on the export paragraph of a repository that ships encryption
View repository →Finds the money lines that send the wrong amount to a payment API: the x100 that charges 100x in JPY
View repository →