npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

review-ready-mcp

v0.1.0

Published

MCP server for Review Ready — run pre-PR checks (debug statements, secrets, TODO debt, complexity) from Claude

Readme

review-ready-mcp

MCP server for Review Ready — run pre-PR checks from Claude.

Ask Claude to check your code before opening a pull request. Claude will scan your changed files and flag debug statements, hardcoded secrets, TODO debt, and complexity spikes.

Quick Start

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "review-ready": {
      "command": "npx",
      "args": ["review-ready-mcp"]
    }
  }
}

Claude Code

Add to your project's .mcp.json or global MCP settings:

{
  "mcpServers": {
    "review-ready": {
      "command": "npx",
      "args": ["review-ready-mcp"]
    }
  }
}

Then ask Claude: "Check my changes before I push" or "Run review-ready on /path/to/my/repo"

Tools

check_changes

Runs all checks on the changed files in a git repository.

Input:
  repo_path: string          — Absolute path to the git repo root
  base_sha?: string          — Optional base commit SHA (for CI use)
  head_sha?: string          — Optional head commit SHA (for CI use)
  complexity_threshold?: number  — Branch count threshold (default: 10)

check_content

Checks a code snippet directly — no git required.

Input:
  content: string            — The code to check
  filename: string           — Filename for language-specific rules (e.g., "auth.ts")
  complexity_threshold?: number  — Branch count threshold (default: 10)

What it checks

| Check | What it catches | |-------|----------------| | Debug statements | console.log, debugger, print(), puts, fmt.Print, println!, var_dump, dd() | | TODO/FIXME debt | TODO, FIXME, HACK, XXX, TEMP, WTF, BUG in new code | | Secrets | AWS keys, GitHub PATs, OpenAI keys, Slack tokens, hardcoded credentials | | Large files | Files over 500KB accidentally staged | | Missing tests | Source files changed without a test file (via check_changes) | | Complexity | High cyclomatic complexity in changed JS/TS code |

Example usage in Claude

You: Check my changes before I push. The repo is at /home/me/my-project.

Claude: (calls check_changes with repo_path="/home/me/my-project")

Found 2 errors, 1 warning, 0 info

✗ [no-debug-statements] Debug statement found: console.log(userData) [src/auth.ts:42] ✗ [no-secrets] Possible API key detected [src/config.ts:8] ⚠ [no-todo-in-changes] Unresolved marker: // TODO: validate token expiry [src/auth.ts:67]


Also available as:

  • GitHub Action: uses: yurukusa/[email protected]
  • VS Code Extension: Search "Review Ready" in the marketplace
  • npm library: npm install review-ready

Source: github.com/yurukusa/vscode-review-ready