Coverage Gate Lint

io.github.jmshinhwaPublished by GitHub account jmshinhwav1.0.3Updated Oct 24, 2026

Finds the coverage gates in your repo that can never fail a build

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local MCP server that finds coverage gates in a repository which can never fail a build.

What you can do
The manifest lists no tools, so its capabilities come from the description and README. It is described as finding coverage gates in a repository that can never fail a build. The README, however, presents it as a VS Code theme package, which does not match that description.
When to use it
Possibly relevant if you want an assistant to check whether coverage thresholds in a repository are configured so they can actually fail a build. Given the mismatch between the description and README, confirm what it does before relying on it.
Requirements
Runs locally as a process started with npx from the npm package @readystack/coverage-gate-lint. No authentication, environment variables or headers are declared. Desktop only; not executable on the web.
Before you install
The registry description and the README describe different things, so the package's actual behavior is unclear. It runs as a local process on your machine, so review what it executes before installing.

Installation

In SourceWeft

  1. Open Coverage Gate Lint in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

readystack-themes

Made by ReadyStack · free calculators and templates at getreadystack.com VS Code themes by ReadyStack

Source: README.md at commit ee1c884

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.3LatestSep 19, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.