A
licenseA
qualityD
maintenanceMCP server that audits your project's dependency licenses for compatibility issues. Flags GPL/AGPL conflicts and generates compliance reports.
1
35 npm
1
MIT
LicenseGuard
by rccaoki-wq
Related Servers
Alternatives to LicenseGuard
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceDepGuard is an MCP server for real-time dependency safety checks, verifying packages against vulnerability databases, deprecation metadata, and a local cache.2 npmMIT
- AlicenseCqualityAmaintenanceGuardRail MCP is an enterprise agent security server that provides multi-language code analysis, dependency scanning, and container security checks, with RBAC, policy packs, and audit logging.23MIT
- AlicenseNot gradedqualityFmaintenanceA lightweight MCP server for security reviews that injects security requirements before code generation, scans dependencies for CVEs, and verifies generated code without disrupting workflow.68MIT
- AlicenseAqualityBmaintenanceProvides authoritative open source license answers: SPDX identification, copyleft classification, and compatibility checks of dependencies against your project's license.3MIT
gridwork-licenseofficial
AlicenseAqualityDmaintenanceScans project dependencies for license compliance, classifying 60+ licenses and detecting conflicts and copyleft risks.439 npm1MIT
TDQS
A4.2/5.0
Scored across 3 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: explain_license focuses on understanding a license itself, check_dependency_license evaluates a single dependency in context, and check_manifest_licenses scans an entire manifest. There is no overlap or ambiguity between them.
Naming Consistency4/5
All tool names follow a consistent verb_noun pattern (explain_license, check_dependency_license, check_manifest_licenses). The only minor deviation is that two tools start with 'check' while the third uses 'explain', but this is justified by the different action types.
Tool Count4/5
With only 3 tools, the server is slightly on the lean side, but each tool covers a distinct and essential aspect of license management (understanding, single-dependency check, full-manifest scan). The count is appropriate for a focused utility server.
Completeness4/5
The tool surface covers the core workflows: understanding licenses, checking individual dependencies, and scanning entire manifests. A minor gap is the lack of a tool to handle bulk license explanations or compare multiple licenses directly, but the existing tools cover the primary use cases well.
Maintenance
ActivitySlowing
ResponsivenessNo issues