Readyorai

io.github.TedoNeObichaJavaScriptPublished by GitHub account TedoNeObichaJavaScriptv0.1.2Updated Oct 24, 2026

Zero-cost MCP server for local code inspection and best-practice recommendations

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Local, zero-cost MCP server that inspects source code for quality, security and best-practice issues and suggests fixes.

What you can do
  • Inspect a single file or a whole directory for code quality issues
  • Get quantitative metrics such as lines of code, complexity and function count
  • Compare two file versions to see fixed, introduced or unchanged findings
  • Get actionable fix suggestions with context for each finding
  • Run structured code review and project health-check prompts
When to use it
Useful when you want an assistant to review local code for clean-code, complexity, naming, duplication and security patterns without sending code to an external service, or to track incremental cleanup against a baseline.
Requirements
Runs as a local stdio process, typically launched with npx from the readyorai npm package, so Node.js and npm are needed. No API keys or environment variables are declared; analysis runs entirely locally.
Before you install
The server reads local source files, so point it only at directories you are comfortable exposing to the assistant. It reports findings but does not modify code. Optional project config and inline suppression comments affect which findings appear.

Installation

In SourceWeft

  1. Open Readyorai 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

ReadyOrAI

Zero-cost MCP server for local code inspection. Analyzes your code for clean code practices, best practices, and gives actionable recommendations — without modifying your code or making API calls.

Features

  • 9 analyzers: complexity, naming, structure, patterns, imports, documentation, security, duplication, AI-generated code detection
  • Multi-language: JS/TS, Python, Go, Rust (deep analysis) + Java, C#, Ruby, PHP, and more (regex-based)
  • Zero-cost: All analysis runs locally — no API keys, no external calls
  • MCP server: Works with Claude Desktop, Claude Code, and VS Code via stdio transport
  • CLI tool: ready @filename and AI terminal commands for standalone use
  • SARIF output: Export results for GitHub Code Scanning integration
  • Watch mode: Continuous re-analysis on file changes
  • Baseline/diff mode: Track incremental adoption — only see new issues
  • Config file: Project-level .readyorai.json for shared settings
  • Inline suppressions: Silence specific findings with // readyorai-ignore comments

Installation

As an MCP Server

Claude Desktop (claude_desktop_config.json):

json
{  "mcpServers": {    "readyorai": {      "command": "npx",      "args": ["-y", "readyorai"]    }  }}

Claude Code:

bash
claude mcp add readyorai -- npx -y readyorai

VS Code (.vscode/mcp.json):

json
{  "servers": {    "readyorai": {      "command": "npx",      "args": ["-y", "readyorai"]    }  }}

As a CLI Tool

bash
npm install -g readyorai

CLI Usage

bash
ready @src/index.ts                          # Inspect a single fileready @src/                                  # Inspect a directoryready @src/index.ts --checks security,naming # Run specific checksready @src/index.ts --json                   # JSON outputready @src/index.ts --sarif                  # SARIF output (GitHub Code Scanning)ready @src/index.ts --severity warning       # Only warnings and errorsready @src/index.ts --watch                  # Re-analyze on file changesready @src/ --baseline baseline.json         # Compare against saved baselineready @src/ --save-baseline baseline.json    # Save current results as baselineAI                                           # Inspect current directoryAI @src/utils.ts                             # Alias with file target

Exit Codes

CodeMeaning
0No issues found
1Warnings found
2Errors found
3Runtime error

Configuration

Create a .readyorai.json in your project root:

json
{  "checks": ["complexity", "naming", "security"],  "severity": "warning",  "exclude": ["dist/**", "node_modules/**"]}

Inline Suppressions

Silence specific findings on a line:

js
eval(code); // readyorai-ignore

MCP Tools

ToolDescription
inspect_fileAnalyze a single file for code quality issues
inspect_directoryBatch analysis of all source files in a directory
get_metricsGet quantitative metrics (LOC, complexity, function count)
compare_filesCompare two file versions and show fixed, introduced, or unchanged findings
suggest_fixesGet actionable fix suggestions with context for each finding

MCP Prompts

PromptDescription
review-codeStructured code review with optional focus area
health-checkProject-level health assessment

Checks

CheckWhat it detects
complexityCyclomatic/cognitive complexity, deep nesting
namingConvention violations, single-letter vars, boolean prefixes
structureLong files/functions, too many parameters, long lines
patternsconsole.log, empty catch, magic numbers, nested ternaries, TODOs
importsUnused imports, wildcard imports, scattered imports
documentationMissing JSDoc/docstrings, low comment ratio
securityHardcoded secrets, eval(), SQL injection, XSS patterns
duplicationDuplicate code blocks, repeated magic strings
ai-detectionDetects patterns common in AI-generated code

Language Support

TierLanguagesAnalysis
1JavaScript, TypeScript, Python, Go, RustFull AST-powered analysis
2Java, C#, Ruby, PHP, Swift, Kotlin, C, C++Regex + heuristic analysis
3Any text fileLine-based checks (length, TODOs, secrets, duplication)

Development

bash
git clone https://github.com/TedoNeObichaJavaScript/ReadyOrAI.gitcd ReadyOrAInpm installnpm run buildnpm test

Support

If you find ReadyOrAI useful, consider supporting the project:

  • Borko — 5 euro

License

MIT

Source: README.md at commit e7d0593

Tools

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

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

50% 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