gridwork-license
OfficialClick 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., "@gridwork-license Scan my project dependencies for license conflicts"
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.
gridwork-license
MCP server that scans project dependencies for license compliance issues.
What it does
Scans node_modules and Python requirements for license information
Classifies 60+ licenses by risk level (copyleft, weak-copyleft, permissive, public-domain, proprietary)
Detects conflicts between dependency licenses and your project license
Flags AGPL dependencies in non-AGPL projects (SaaS risk)
Identifies unknown/undeclared licenses
Related MCP server: license-compliance-mcp
Install
npx gridwork-licenseMCP tools
Tool | Description |
| Full license scan with conflict detection |
| Risk breakdown and conflict count |
| Classify any license string |
| Find all copyleft dependencies |
Claude Desktop config
{
"mcpServers": {
"gridwork-license": {
"command": "npx",
"args": ["-y", "gridwork-license"]
}
}
}License
MIT — Gridwork
Available Tools
4 toolsclassify_licenseB
Classify a license string — returns risk level (copyleft, weak-copyleft, permissive, public-domain, proprietary, unknown) and SPDX identifier.
Inputs: license (required).
find_copyleftA
Find all copyleft-licensed dependencies in a project. Useful for quickly identifying viral license obligations.
Inputs: path (required).
quick_checkB
Quick license overview — counts and risk breakdown without full details.
Inputs: path (required).
scan_licensesB
Scan a project's dependencies for license compliance issues. Detects copyleft conflicts, unknown licenses, and proprietary risks. Works with npm (node_modules), Python (requirements.txt), and more.
Inputs: path (required), format.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool targets a distinct operation: license string classification, copyleft discovery, quick overview, and full compliance scan. No functional overlap exists.
Three of four tools follow verb_noun pattern (classify_license, find_copyleft, scan_licenses). quick_check deviates slightly with adjective_noun, but remains clear and predictable.
Four tools cover the core license management tasks without redundancy. The count is well-scoped for the server's purpose.
Covers classification, copyleft identification, overview, and full scan. Minor gaps like license policy configuration or update capabilities could exist, but core workflows are complete.
Related MCP Connectors
Open-source licence risk checks for AI coding agents and dependency trees.
Generate, audit, and maintain legal policies that match what your code actually does.
Evaluates any GitHub repository for license risk, maintenance velocity, stars/forks, and supply-c.
Generate SBOMs, scan vulnerabilities, and analyze dependencies from local projects or Git repos.
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.-
- AlicenseAqualityDmaintenanceScans npm project dependencies for license compliance issues, detecting GPL contamination and generating detailed reports.250 npmMIT
- AlicenseAqualityDmaintenanceAudits project dependency licenses for compatibility issues, flags GPL/AGPL conflicts, and generates compliance reports.153 npmMIT
- AlicenseAqualityCmaintenanceEnables AI coding agents to audit Python and npm dependency licenses against your distribution context before shipping, returning CLEAN, REVIEW, or BLOCK verdicts with plain-language reasons and supporting notice generation.31MIT