MCP.Market

License Audit MCP server

by webmoleai·io.github.webmoleai/mcp-license-audit·v0.1.1

Audit dependency licenses for compatibility issues. Flags GPL/AGPL conflicts.

B80/100grade B
What users say
No reviews yet
Be the first
Safety scan
B80/100

full report

Adoption
New

0 stars39 downloads/wk

Reviews

Write one

Nobody has reviewed License Audit yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

License Audit tools (1)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • audit-licenses

    Audit your project's dependency licenses for compatibility issues. Flags GPL/AGPL conflicts and generates compliance reports.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan3 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 174 days ago8/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 80/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How License Audit compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
80/100
higher than 60% of 48,255 servers
Tools
1
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
39
more than 30% of 12,191 servers with a package

What its tools let an agent do: 1 read

Install License Audit in Claude Code, Cursor or VS Code

Runs npx -y mcp-license-audit on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp-license-audit -- npx -y mcp-license-audit
Add to Cursor

What the publisher says

From the License Audit repository's README, as published. We do not edit it. Read it on GitHub

mcp-license-audit

MCP server that audits your project's dependency licenses for compatibility issues. Flags GPL/AGPL conflicts and generates compliance reports.

What It Does

  • Parses a package.json file (dependencies + devDependencies)
  • Fetches license info for each package from the npm registry
  • Classifies licenses: permissive (MIT, Apache, BSD, ISC), copyleft (GPL, AGPL), weak-copyleft (LGPL, MPL), unknown
  • Detects conflicts (e.g., GPL dependency in an MIT-licensed project)
  • Returns a structured JSON report with risk level and summary

Install

npm install -g mcp-license-audit
# or run directly:
npx mcp-license-audit

Configure in Claude Code

Add to your .claude/mcp.json or ~/.claude/mcp.json:

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

Or if installed globally:

{
  "mcpServers": {
    "license-audit": {
      "command": "mcp-license-audit"
    }
  }
}

Tool: audit-licenses

Input: packageJson — the full contents of a package.json file as a string.

Output: JSON report:

{
  "totalDependencies": 15,
  "analyzed": 15,
  "licenses": {
    "MIT": ["express", "lodash"],
    "Apache-2.0": ["typescript"],
    "GPL-3.0": ["some-package"],
    "unknown": ["private-pkg"]
  },
  "conflicts": [
    {
      "package": "some-package",
      "license": "GPL-3.0",
      "issue": "GPL dependency in MIT project — must open-source your code if distributed"
    }
  ],
  "riskLevel": "medium",
  "summary": "15 deps analyzed. 1 GPL conflict found. 1 unknown license."
}

Risk levels: low (no copyleft), medium (weak copyleft or many unknowns), high (GPL/AGPL found).

Limits

  • Analyzes first 20 dependencies for speed
  • Only supports npm packages (no pip/cargo/gem support yet)
  • License data comes from the npm registry — private packages return "unknown"

Build from Source

npm install
npm run build
node dist/index.js

Nothing above is checked by us. What we check is on the safety report.

License Audit: common questions

Is License Audit MCP server safe?
Mostly: it is graded B (80/100). Read the License Audit safety report
How do I install License Audit?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does License Audit need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is License Audit maintained?
The last commit was 211 days ago (2026-04-07). The latest release is v0.1.1.
How does License Audit compare with other MCP servers?
safety score 80/100 (higher than 60% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from webmoleai →