license-compliance-mcp
Related Servers
Alternatives to license-compliance-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAudits project dependency licenses for compatibility issues, flags GPL/AGPL conflicts, and generates compliance reports.126 npmMIT
- -licenseNot gradedqualityBmaintenanceAudits npm dependencies for license compatibility, catching copyleft and source-available traps before shipping.-
- AlicenseAqualityCmaintenanceEnables scanning of package.json and lockfiles to classify dependency licenses and flag GPL/AGPL/unknown ones for commercial awareness, optionally reading license metadata from the public npm registry. Advisory only, not legal advice.3MIT

gridwork-licenseofficial
AlicenseAqualityDmaintenanceScans project dependencies for license compliance, classifying 60+ licenses and detecting conflicts and copyleft risks.426 npm1MIT- AlicenseCqualityDmaintenanceAudits npm package dependencies for security vulnerabilities, providing detailed reports and fix recommendations with MCP integration.148 npm57MIT
- 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.-
TDQS
Scored across 2 tools
The two tools are completely distinct: one scans npm dependencies for compliance, the other explains SPDX licenses. There is no overlap or ambiguity between them.
Both tools follow a verb_noun pattern with hyphenation, but 'check-licenses' uses plural while 'explain-license' uses singular. This minor inconsistency is slightly noticeable but does not hinder readability.
With only 2 tools, the server feels thin for its apparent scope. The tools are focused and useful, but the count is on the borderline of what is considered reasonable for a utility server.
The server covers scanning and explaining, but lacks tools for managing the compliance policy (e.g., setting or updating policy). This is a notable operational gap for a license compliance workflow.