@mcpx-digital/license-scan
Reads license metadata from the public npm registry (no tarball downloads) to fill in missing license fields for dependencies when the lockfile lacks them, enabling classification of dependency licenses as permissive, copyleft (GPL/AGPL/LGPL), or unknown.
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., "@@mcpx-digital/license-scan scan this project's dependency licenses and flag GPL/AGPL/unknown ones"
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.
@mcpx-digital/license-scan
MCP server for dependency license awareness (advisory).
Scan package.json + lockfiles for dependency licenses. When the lockfile has no license field, optionally read the license metadata from the public npm registry (no tarball downloads). Flag GPL/AGPL/unknown licenses for commercial awareness.
ADVISORY ONLY — not legal advice. Metadata can be wrong or incomplete. Verify critical dependencies yourself before shipping.
Install
npx -y @mcpx-digital/license-scanRelated MCP server: Dependency Checker MCP Server
Cursor mcp.json example
{
"mcpServers": {
"license-scan": {
"command": "npx",
"args": ["-y", "@mcpx-digital/license-scan"]
}
}
}Local clone:
{
"mcpServers": {
"license-scan": {
"command": "node",
"args": ["/absolute/path/to/license-scan-mcp/index.js"]
}
}
}Tools
Tool | What it does |
| Full scan of deps with classifications |
| GPL/AGPL/LGPL-family + unknown only |
| Classify one license string |
Example prompts
“Scan licenses in
/path/to/my-app”“Flag copyleft/unknown licenses for this project”
“Is
GPL-3.0-or-latercopyleft?”
Development
git clone https://github.com/TheoryofShadows/license-scan-mcp.git
cd license-scan-mcp
npm install
npm testLicense
MIT
Available Tools
3 toolsclassify_license_stringA
Classify a single license string as permissive / copyleft / unknown / other. ADVISORY ONLY — not legal advice. Uses lockfile metadata and/or the public npm registry license field (no tarball downloads).
Inputs: license (required).
flag_risky_licensesA
Flag GPL/AGPL/LGPL-family and unknown licenses for commercial awareness. ADVISORY ONLY — not legal advice. Uses lockfile metadata and/or the public npm registry license field (no tarball downloads).
Inputs: projectDir (required), includeDev, fetchMissing.
scan_licensesA
Scan package.json (+ lockfile) for dependency licenses; optionally fill gaps via npm registry license field. ADVISORY ONLY — not legal advice. Uses lockfile metadata and/or the public npm registry license field (no tarball downloads).
Inputs: projectDir (required), maxFetch, includeDev, includePeer, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
The tools are mostly distinct: scan_licenses scans a project's dependencies, flag_risky_licenses filters for risky licenses, and classify_license_string handles a single license string. There is some conceptual overlap between scan_licenses and flag_risky_licenses since both operate on the same project data, but their outputs and purposes differ enough to avoid serious confusion.
All three tools follow a consistent verb-first snake_case pattern: scan_, flag_, classify_. The names clearly describe the action and target, and there is no mixing of conventions or vague verbs.
Three tools is well-scoped for a focused license-scanning utility. Each tool serves a distinct step in the workflow—scanning, flagging, and classifying—without unnecessary bloat.
The toolset covers the core license scanning workflow: scanning a project, flagging risky licenses, and classifying individual strings. A minor gap is the lack of a tool to retrieve full license texts or detailed compliance data, but for the stated advisory purpose the surface is reasonably complete.
Maintenance
Related MCP Connectors
Scan packages and lockfiles (npm, PyPI, Go, Maven, Cargo, NuGet) for vulnerabilities and malware.
Detect malicious or vulnerable npm packages: registry search, OSV.dev and GitHub advisory lookups
Check a lockfile for known vulnerabilities and risky licences, and get alerted when new ones appear.
Provide AI-powered real-time analysis and intelligence on NPM packages, including security, depend…
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables scanning of project dependencies across multiple package managers (npm, pip, cargo, etc.) and generates comprehensive markdown license reports. Supports automatic license detection from package registries with caching for improved performance.-
- AlicenseBqualityDmaintenanceEnables security scanning for npm dependencies by checking manifest and lockfiles against the OSV.dev and Socket.dev vulnerability databases. It provides tools to detect vulnerabilities in specific packages and retrieve detailed technical reports for identified security issues.316 npmMIT

gridwork-licenseofficial
AlicenseAqualityDmaintenanceScans project dependencies for license compliance, classifying 60+ licenses and detecting conflicts and copyleft risks.428 npm1MIT- -licenseNot gradedqualityBmaintenanceAudits npm dependencies for license compatibility, catching copyleft and source-available traps before shipping.-