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., "@prodlint scan my vibe-coded app for security 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.
Production readiness for vibe-coded apps.
Static analysis for vibe-coded apps. Flags the security, reliability, performance, and AI quality issues that Cursor, v0, Bolt, and Copilot create — hallucinated imports, missing auth, hardcoded secrets, unvalidated server actions, and more. Zero config, no LLM, 52 rules.
npx prodlint prodlint v0.10.0
Scanned 148 files · 2 critical · 5 warnings · 1 info
src/app/api/checkout/route.ts
12:1 INFO No rate limiting — anyone could spam this endpoint and run up your API costs rate-limiting
28:5 WARN Empty catch block silently swallows error shallow-catch
src/actions/submit.ts
5:3 CRIT Server action uses formData without validation next-server-action-validation
↳ Validate with Zod: const data = schema.safeParse(Object.fromEntries(formData))
src/lib/db.ts
1:1 CRIT Package "drizzle-orm" is imported but not in package.json hallucinated-imports
Scores
security 72 ████████████████░░░░ (8 issues)
reliability 85 █████████████████░░░ (4 issues)
performance 95 ███████████████████░ (1 issue)
ai-quality 90 ██████████████████░░ (3 issues)
Overall: 82/100 (weighted)
2 critical · 5 warnings · 4 infoVibe coding is the fastest way to build. Shipping fast means knowing your code is production-ready — not just that it compiles. Hardcoded secrets, hallucinated packages, missing auth, and XSS vectors pass type-checks and look correct — but they aren't ready for production.
prodlint checks what TypeScript and ESLint don't: whether your vibe-coded app is ready for production.
Related MCP server: open-code-review
npx prodlint # Run directly (no install)
npx prodlint ./my-app # Scan specific path
npx prodlint --json # JSON output for CI
npx prodlint --sarif # SARIF 2.1.0 for GitHub Code Scanning
npx prodlint --summary # Quick pass/fail + top 3 blockers
npx prodlint --profile startup # Only critical findings
npx prodlint --profile strict # All findings including info
npx prodlint --baseline .prodlint-baseline.json # Only new findings
npx prodlint --ignore "*.test.ts" # Ignore patterns
npx prodlint --min-severity warning # Only warnings and criticals
npx prodlint --quiet # Suppress badge outputOr install it:
npm i -D prodlint # Project dependency
npm i -g prodlint # Global installRule | What it checks |
| API keys, tokens, passwords hardcoded in source |
| API routes with no authentication |
|
|
| Request body used without validation |
|
|
|
|
| String-interpolated SQL queries (ORM-aware) |
| User input passed to |
| API routes with no rate limiter |
| Packages in node_modules but missing from package.json |
| Session cookies missing httpOnly/secure/sameSite |
|
|
|
|
| Server actions using formData without Zod/schema validation |
| Security-sensitive env vars with hardcoded fallback values |
| Error stack traces or messages leaked in API responses |
| Webhook routes without signature verification |
| Server actions with mutations but no auth check |
|
|
|
|
| User-controlled URLs passed to fetch in server code |
| File system operations with unsanitized user input |
| File upload handlers without type or size validation |
|
|
| OAuth Implicit Grant (response_type=token) |
| JWT tokens signed without an expiration |
| Password comparisons or auth logic in client components |
Rule | What it checks |
| Imports of packages not in package.json |
| Async operations without try/catch |
| Floating promises with no await or .catch |
| Empty catch blocks that swallow errors |
| Client components that fetch without a loading state |
| Route layouts without a matching error.tsx |
| Multiple Prisma writes without |
|
|
| Server actions with DB mutations but no |
| useEffect with subscriptions/timers but no cleanup return |
|
|
Rule | What it checks |
|
|
| Database calls inside loops |
|
|
|
|
| Server components fetching their own API routes |
| Fetch/axios calls without timeout or AbortController |
Rule | What it checks |
|
|
| Lorem ipsum, example emails, "your-api-key-here" left in production code |
|
|
|
|
| Functions over 80 lines, deep nesting, too many parameters |
| Mixed naming conventions across the project |
| Exported functions that nothing imports |
|
|
prodlint avoids common false positives:
AST parsing — Babel-based analysis for 12 rules (imports, catch blocks, redirects, SSRF, path traversal, JWT, HTML injection, hydration, transactions, env leaks, loops, SQL) with regex fallback
Monorepo support — npm/yarn/pnpm workspace dependencies resolved automatically
Framework awareness — Prisma, Drizzle, Supabase, Knex, and Sequelize whitelists prevent false SQL injection flags
Middleware detection — Clerk, NextAuth, Supabase middleware detected — auth findings downgraded
Block comment awareness — patterns inside /* */ are ignored
Path alias support — @/, ~/, and tsconfig paths aren't flagged as hallucinated imports
Route exemptions — auth, webhook, health, and cron routes are exempt from auth/rate-limit checks
Test/script file awareness — lower severity for non-production files
Fix suggestions — findings include actionable fix hints with remediation code
Each category starts at 100. Deductions per finding:
Severity | Deduction | Per-rule cap |
critical | -8 | max 1 |
warning | -2 | max 2 |
info | -0.5 | max 3 |
Diminishing returns: after 30 points deducted in a category, further deductions are halved; after 50, quartered.
Weighted overall: security 40%, reliability 30%, performance 15%, ai-quality 15%. Floor at 0. Exit code 1 if any critical findings exist.
Add to .github/workflows/prodlint.yml:
name: Prodlint
on: [pull_request]
jobs:
scan:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: prodlint/prodlint@v1
with:
threshold: 50Posts a score breakdown as a PR comment and fails the build if below threshold.
Input | Default | Description |
|
| Path to scan |
|
| Minimum score to pass (0-100) |
| Comma-separated glob patterns to ignore | |
|
| Post PR comment with results |
Output | Description |
| Overall score (0-100) |
| Number of critical findings |
Upload prodlint results to GitHub's Security tab:
- name: Run prodlint
run: npx prodlint --sarif > prodlint.sarif
- name: Upload SARIF
uses: github/codeql-action/upload-sarif@v4
with:
sarif_file: prodlint.sarif
category: prodlintAdopt prodlint gradually without drowning in pre-existing findings:
# Save current state as baseline
npx prodlint --baseline-save .prodlint-baseline.json
# CI only fails on NEW findings
npx prodlint --baseline .prodlint-baseline.jsonUse prodlint inside Cursor, Claude Code, or any MCP-compatible editor:
Claude Code:
claude mcp add prodlint -- npx -y -p prodlint prodlint-mcpCursor / Windsurf:
{
"mcpServers": {
"prodlint": {
"command": "npx",
"args": ["-y", "-p", "prodlint", "prodlint-mcp"]
}
}
}-p prodlint runs the MCP server straight from the prodlint package, so you always get
the current scanner.
Ask your AI: "Run prodlint on this project" and it calls the scan tool directly.
Check any deployed website for AI agent-readiness — 14 checks covering emerging standards like llms.txt, TDMRep, AgentCard, AI-Disclosure, HTTP Signatures (RFC 9421), and more.
npx prodlint --web example.com
npx prodlint --web example.com --json # JSON output prodlint site score
example.com · 14 checks
Score: 42 C ████████░░░░░░░░░░░░
✗ AI-Disclosure Header 0/10 No AI-Disclosure header found.
✗ Content-Usage Directives 0/10 No Content-Usage directives found.
✗ TDMRep 0/10 No TDMRep found.
✗ A2A AgentCard 0/5 No agent-card.json found.
✗ ai.txt 0/5 No ai.txt found at site root.
! llms.txt 2/5 llms.txt found but missing key sections.
✓ robots.txt 10/10 robots.txt found with 15 rules.
✓ Sitemap 10/10 Valid sitemap with 42 URLs.
✓ Structured Data 10/10 Found JSON-LD structured data.
✓ OpenGraph 10/10 Complete OpenGraph tags found.
✓ Page Speed 5/5 Loaded in 0.8s.
✓ AI Bot Directives 5/5 AI-specific bot rules found.
✓ WebMCP Tools 0/5 No WebMCP tools detected.
7 passed · 5 failed · 1 warnings
Full results: https://prodlint.com/score?url=example.comOr check your score interactively at prodlint.com/score.
LLM-friendly docs: prodlint.com/llms.txt — concise project summary for LLMs
Full reference: prodlint.com/llms-full.txt — all 52 rules with details
MCP setup guide: prodlint.com/mcp — detailed editor setup for Claude Code, Cursor, Windsurf
prodlint is designed specifically for AI-generated code patterns. Every rule checks for production issues that AI coding tools consistently create — not style nits.
Suppress a single line:
// prodlint-disable-next-line secrets
const key = "sk_test_example_for_docs"Suppress an entire file (place at top):
// prodlint-disable secretsimport { scan } from 'prodlint'
const result = await scan({ path: './my-project' })
console.log(result.overallScore) // 0-100
console.log(result.findings) // Finding[][](https://prodlint.com)MIT
This server cannot be deployed
AI-powered codebase analysis — call graphs, security, dead code, complexity. 150+ tools.
Zero-config MCP security scanner for AI-generated apps. 25K+ vulnerability patterns.
Code intelligence platform for AI agents. 20 tools for architecture, security & impact analysis.
Deep security scans of repos you own from your editor: dependency CVEs, SAST, git-history secrets.
