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

production-readiness-scanner-mcp

v1.0.0

Published

MCP server that analyzes code for production readiness, checking error handling, logging, security, testing, and documentation

Downloads

47

Readme

Production Readiness Scanner MCP

An MCP (Model Context Protocol) server that automatically analyzes code for production readiness, identifying missing components that are essential for robust, maintainable, and secure software.

Features

Code Analysis Tools

  • analyze_code: Scan code snippets for production essentials
  • analyze_file: Analyze individual files
  • scan_directory: Comprehensive directory analysis
  • learn_patterns: Learn from existing codebase patterns
  • configure_rules: Customize analysis rules
  • get_fixes: Generate specific code fixes

Multi-Language Support

  • JavaScript/TypeScript: Error handling, Promise patterns, test files
  • Python: Exception handling, logging, type hints
  • Go: Error returns, defer statements (planned)

Production Checks

  • Security: Input validation, SQL injection prevention
  • Error Handling: Try-catch blocks, graceful degradation
  • Testing: Unit tests, test coverage analysis
  • Documentation: Function comments, API documentation
  • Performance: Database optimization, async patterns
  • Logging: Structured logging, error tracking

Installation

npm install production-readiness-scanner-mcp

Usage with Claude Code

Add the MCP server to Claude Code:

claude mcp add production-scanner -s user -- npx production-readiness-scanner-mcp

Or for global installation:

npm install -g production-readiness-scanner-mcp
claude mcp add production-scanner -s user -- production-readiness-scanner

Usage

Once added to Claude Code, you can:

  1. Analyze Code Snippets:

    Use the analyze_code tool to check this function for production readiness
  2. Scan Entire Directories:

    Scan my src/ directory for production readiness issues
  3. Learn Team Patterns:

    Learn patterns from my existing codebase to customize checks
  4. Get Fix Suggestions:

    Get specific fixes for the issues found in my code

Scoring System

Files are scored 0-100 based on production readiness:

  • 100: Perfect production ready
  • 90-99: Minor improvements needed
  • 80-89: Some issues to address
  • 70-79: Significant improvements required
  • <70: Major production readiness concerns

Issue Categories

Issues are categorized by severity and type:

Severity Levels:

  • Critical: Security vulnerabilities, major errors
  • High: Missing error handling, unsafe patterns
  • Medium: Missing tests, documentation gaps
  • Low: Code style, minor optimizations

Categories:

  • Error Handling
  • Security
  • Testing
  • Documentation
  • Performance
  • Logging

Requirements

  • Node.js 16 or higher
  • Claude Code with MCP support

License

MIT

Support

For issues and feature requests, please use the GitHub issues page.