Skip to content
BEAD

package.json Validator

Validate npm package.json — name, SemVer, scripts, dependencies, license, engines. Preview scripts.

Developer
Errors
0
Warnings
0
Status
Valid
Scripts
npm run devnext dev
npm run buildnext build
npm run testvitest
</>Use this tool programmaticallycurl · JavaScript · MCP

Same tool, callable from any HTTP client or from Claude (via MCP). Anonymous: 100 req/day per IP. Sign up for 1,000 req/day.

curl
curl https://api.b-e-a-d.com/tools/package-json-validator/run \
  -H "Content-Type: application/json" \
  -d '{
  "input": "your input here"
}'
JavaScript (fetch)
const res = await fetch("https://api.b-e-a-d.com/tools/package-json-validator/run", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
  "input": "your input here"
}),
});
const data = await res.json();
console.log(data.result);
MCP (Claude Desktop / Claude Code)
# In Claude Desktop / Claude Code, add to your MCP config:
{
  "mcpServers": {
    "bead": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.b-e-a-d.com"]
    }
  }
}

# Then ask Claude to call:
mcp__bead__bead_package_json_validator

Full reference: developer docs · OpenAPI spec

What we check

  • name — present, valid npm-package-name rules
  • version — SemVer 2.0.0
  • main / module / exports — string or object shape
  • scripts — string values
  • dependencies / devDependencies / peerDependencies — valid SemVer ranges, tag, or URL
  • license — SPDX identifier (warning only if unrecognized)
  • engines — SemVer ranges

Script preview

See every scripts entry at a glance with a one-click copy to paste into your terminal.

You might also like

Used in these workflows