Skip to main content
Glama
license-compliance-mcp

license-compliance-mcp

by bighippoman

license-compliance-mcp

MCP server that scans npm project dependencies for license compliance issues. Catch GPL contamination before code ships.

Tools

check-licenses

Scan a project's npm dependencies against a license policy and get a detailed compliance report.

Parameters:

  • path (required) — Absolute path to the project root

  • policy (optional, default: "permissive") — Policy preset or custom SPDX expression

    • "permissive" — Only MIT, ISC, BSD, Apache-2.0, etc.

    • "weak-copyleft" — Adds LGPL, MPL-2.0, EPL-2.0

    • "copyleft" — Adds GPL, AGPL

    • Custom: "(MIT OR Apache-2.0)" — Any valid SPDX expression

explain-license

Get a plain-language explanation of any SPDX license — permissions, conditions, limitations, compatibility, and gotchas.

Parameters:

  • license (required) — SPDX identifier (e.g., "MIT", "GPL-3.0-only", "Apache-2.0")

Related MCP server: License Scanner MCP Server

Install

Claude Code

claude mcp add license-compliance -- npx -y license-compliance-mcp

Claude Desktop / Cursor

Add to your config (claude_desktop_config.json or .cursor/mcp.json):

{
  "mcpServers": {
    "license-compliance": {
      "command": "npx",
      "args": ["-y", "license-compliance-mcp"]
    }
  }
}

How It Works

  1. Scans node_modules using license-checker-rseidelsohn

  2. Normalizes license strings to valid SPDX using spdx-correct

  3. Evaluates each package against the policy using spdx-satisfies

  4. Traces dependency chains to show how problematic packages entered the project

  5. Generates a markdown report grouped by severity (critical > warning > info)

Requirements

  • Node.js >= 18

  • Project must have node_modules installed (npm install)

Available Tools

2 tools
check-licensesCheck License ComplianceA

Scan a project's npm dependencies for license compliance issues. Checks all installed packages against a policy (permissive, weak-copyleft, copyleft, or a custom SPDX expression). Returns a detailed markdown report with any violations, warnings, and dependency chains.

Inputs: path (required), policy.

explain-licenseExplain LicenseA

Explain what a specific SPDX license means in plain language. Covers permissions, conditions, limitations, compatibility with proprietary/open-source/SaaS use, and common gotchas. Supports 15 major licenses plus deprecated SPDX forms.

Inputs: license (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 2 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers