License Compliance
Scan an npm dependency tree for license risks—especially copyleft/GPL leakage—before you ship a commercial SaaS or client deliverable.
Overview
License Compliance is an MCP server for the Ship phase that scans npm dependencies for license compliance issues including GPL contamination.
What is this MCP server?
- Scans npm dependencies for license compliance issues called out in the server description
- Focused on catching GPL-style contamination before it reaches production bundles
- stdio npm package license-compliance-mcp v1.0.2 for agent-driven audits in the repo
- Fits a ship checklist alongside secret scanning and dependency updates
- Server version 1.0.2 on npm identifier license-compliance-mcp
- stdio transport via npm registry package
What problem does it solve?
You cannot confidently ship or sell an npm app when hidden copyleft licenses in node_modules could force source disclosure or block deals.
Who is it for?
Solo builders shipping npm-based SaaS, CLIs, or Electron-style apps who need a quick compliance scan without standing up a separate legal toolchain.
Skip if: Python, Go, or mobile-native stacks unless you also manage licenses there with other tools—this server targets npm as described.
What do I get? / Deliverables
After registration, your agent can surface dependency license problems during ship prep so you remediate or replace packages before release.
- License compliance findings for npm dependency trees
- Actionable flags for packages that may violate your shipping policy
Recommended MCP Servers
Journey fit
How it compares
Agent-callable npm license scanner MCP, not a human legal opinion or full SBOM platform.
Common Questions / FAQ
Who is License Compliance for?
Indie developers and small teams shipping JavaScript/npm products who want agents to flag risky licenses before launch or client handoff.
When should I use License Compliance?
Run it before major releases, after large dependency upgrades, or when an enterprise customer asks about copyleft and open-source obligations.
How do I add License Compliance to my agent?
Add the license-compliance-mcp npm package (v1.0.2) to your MCP client over stdio, point it at your project root, and invoke scans from your agent during ship checks.