@mcpx-digital/license-scan
Related Servers
Alternatives to @mcpx-digital/license-scan
No user-submitted related servers found.
Related Servers
- AlicenseAqualityFmaintenanceScans npm project dependencies for license compliance issues, detecting GPL contamination and generating detailed reports.215 npmMIT

gridwork-licenseofficial
AlicenseAqualityDmaintenanceScans project dependencies for license compliance, classifying 60+ licenses and detecting conflicts and copyleft risks.418 npm1MIT- 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.-
- AlicenseNot gradedqualityAmaintenanceEnables auditing npm, Yarn, and pnpm lockfiles in local project directories or remote Git repositories to surface dependency vulnerabilities. Exposes a tool that supports severity thresholds, registry overrides, optional dev-dependency skipping, and text or JSON reports.21 npmMIT
- -licenseNot gradedqualityBmaintenanceAudits npm dependencies for license compatibility, catching copyleft and source-available traps before shipping.-
- AlicenseBqualityCmaintenanceEnables 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.32 npmMIT
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.