Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

prodlint

NPM · PRODLINT-MCP · SCANNED AUG 13

Production readiness for vibe-coded apps. 52 checks for security, reliability, and performance.

Available components

npm · prodlint-mcp 78
78 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 40 of 119 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to prodlint/prodlint). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 3 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 132 tokens (~66/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · prodlint-mcp

# add to Claude Code
claude mcp add prodlint-prodlint -- npx -y prodlint-mcp
# add to Codex CLI
codex mcp add prodlint-prodlint -- npx -y prodlint-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "prodlint-prodlint": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "prodlint-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add prodlint-prodlint --command npx --arg -y --arg prodlint-mcp
# ~/.hermes/config.yaml
mcp_servers:
  prodlint-prodlint:
    command: "npx"
    args: ["-y", "prodlint-mcp"]
// mcp.json
{
  "mcpServers": {
    "prodlint-prodlint": {
      "command": "npx",
      "args": [
        "-y",
        "prodlint-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 13 Aug 26 0
    • Security disclosure: unverified → pass ▲ functional
  • 12 Aug 26 0
    • Security disclosure: pass → unverified ▼ functional
  • 11 Aug 26 +7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 9 Aug 26 71

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 13 Aug 2026 · Analysed npm/prodlint-mcp@0.10.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo prodlint/prodlint
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/prodlint/prodlint/.github/workflows/release.yml@refs/tags/v0.10.0
Rekor log index 2388593256
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:cc45214afb3f503f2c43d574c11269871f9c2274417993b00eb5f9372973a2e06cc32a810961cb9d68e08e9b810f856799e990ee76fefc3e6a9086fb7
Dependencies 119 packages
Packages resolved 119
Stale 40
Tree resolution Complete
MCP tools · 2 exposed · ~132 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
scan ~62

Check a vibe-coded project's production readiness. Returns a 0-100 score with findings across security, reliability, performance, and AI quality categories.

NameTypeReqDescription
ignorearray–Glob patterns to ignore
pathstringyesAbsolute path to the project directory to scan

No output schema declared.

No examples provided.

scan-web ~70

Check a deployed website's AI agent-readiness. Returns a 0-100 score across 14 checks including robots.txt AI directives, llms.txt, AgentCard, WebMCP, and more.

NameTypeReqDescription
urlstringyesURL of the website to scan (e.g. https://example.com)

No output schema declared.

No examples provided.