readyorai
Exports analysis results in SARIF format for GitHub Code Scanning integration.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@readyoraianalyze src/utils.ts for code quality issues"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 @filenameandAIterminal commands for standalone useSARIF 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.jsonfor shared settingsInline suppressions: Silence specific findings with
// readyorai-ignorecomments
Related MCP server: Risk Audit MCP
Installation
As an MCP Server
Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"readyorai": {
"command": "npx",
"args": ["-y", "readyorai"]
}
}
}Claude Code:
claude mcp add readyorai -- npx -y readyoraiVS Code (.vscode/mcp.json):
{
"servers": {
"readyorai": {
"command": "npx",
"args": ["-y", "readyorai"]
}
}
}As a CLI Tool
npm install -g readyoraiCLI Usage
ready @src/index.ts # Inspect a single file
ready @src/ # Inspect a directory
ready @src/index.ts --checks security,naming # Run specific checks
ready @src/index.ts --json # JSON output
ready @src/index.ts --sarif # SARIF output (GitHub Code Scanning)
ready @src/index.ts --severity warning # Only warnings and errors
ready @src/index.ts --watch # Re-analyze on file changes
ready @src/ --baseline baseline.json # Compare against saved baseline
ready @src/ --save-baseline baseline.json # Save current results as baseline
AI # Inspect current directory
AI @src/utils.ts # Alias with file targetExit Codes
Code | Meaning |
| No issues found |
| Warnings found |
| Errors found |
| Runtime error |
Configuration
Create a .readyorai.json in your project root:
{
"checks": ["complexity", "naming", "security"],
"severity": "warning",
"exclude": ["dist/**", "node_modules/**"]
}Inline Suppressions
Silence specific findings on a line:
eval(code); // readyorai-ignoreMCP Tools
Tool | Description |
| Analyze a single file for code quality issues |
| Batch analysis of all source files in a directory |
| Get quantitative metrics (LOC, complexity, function count) |
| Compare two file versions and show fixed, introduced, or unchanged findings |
| Get actionable fix suggestions with context for each finding |
MCP Prompts
Prompt | Description |
| Structured code review with optional focus area |
| Project-level health assessment |
Checks
Check | What it detects |
| Cyclomatic/cognitive complexity, deep nesting |
| Convention violations, single-letter vars, boolean prefixes |
| Long files/functions, too many parameters, long lines |
| console.log, empty catch, magic numbers, nested ternaries, TODOs |
| Unused imports, wildcard imports, scattered imports |
| Missing JSDoc/docstrings, low comment ratio |
| Hardcoded secrets, eval(), SQL injection, XSS patterns |
| Duplicate code blocks, repeated magic strings |
| Detects patterns common in AI-generated code |
Language Support
Tier | Languages | Analysis |
1 | JavaScript, TypeScript, Python, Go, Rust | Full AST-powered analysis |
2 | Java, C#, Ruby, PHP, Swift, Kotlin, C, C++ | Regex + heuristic analysis |
3 | Any text file | Line-based checks (length, TODOs, secrets, duplication) |
Development
git clone https://github.com/TedoNeObichaJavaScript/ReadyOrAI.git
cd ReadyOrAI
npm install
npm run build
npm testSupport
If you find ReadyOrAI useful, consider supporting the project:
Borko — 5 euro
License
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
AI-powered codebase analysis — call graphs, security, dead code, complexity. 150+ tools.
Deep security scans of repos you own from your editor: dependency CVEs, SAST, git-history secrets.
Detects database migration table locks, terraform cost leaks, and OWASP API flaws.
1Read-only AI coding tools for change verification, release readiness, capacity, and guidance.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables comprehensive code analysis including quality assessment, security vulnerability detection, refactoring suggestions, complexity calculations, and automatic documentation generation for multiple programming languages.57 npmMIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables security scanning of code projects to identify common vulnerabilities like XSS, injections, SSRF, and path traversal issues. Provides local, offline scanning with severity-grouped results and actionable fix suggestions for improving code security.38 npm-
- AlicenseNot gradedqualityCmaintenanceEnables AI-powered code safety analysis including risk detection, secret scanning, dependency checking, and code snapshot management. Works offline for basic features with optional cloud integration for advanced ML analysis and team collaboration.6 npm1Apache 2.0
- AlicenseAqualityAmaintenanceEnables AI assistants and developers to analyze code for language-specific best practices and idiomatic patterns across programming languages, CI automation, and configuration formats.162MIT