Check Licenses MCP server
Audit dependency licenses for compatibility issues. Flags GPL/AGPL conflicts.
1 stars35 downloads/wk
Reviews
Write oneNobody has reviewed Check Licenses yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Check Licenses tools (1)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
audit-licensesAudit 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
- 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 173 days ago8/15
- Maintainer identityregistry namespace matches repository owner7/10
How Check Licenses 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
- GitHub stars
- 1
- more than 65% of 28,688 servers
- Downloads a week
- 35
- more than 25% of 12,191 servers with a package
What its tools let an agent do: 1 read
Install Check Licenses in Claude Code, Cursor or VS Code
Runs npx -y mcp-check-licenses on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add mcp-check-licenses -- npx -y mcp-check-licenses
What the publisher says
From the Check Licenses 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-auditConfigure 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"
}
}
}Analytics
This server supports MCPcat analytics. To enable usage tracking, session replay, and error monitoring, set the MCPCATPROJECTID environment variable in your MCP client config:
{
"mcpServers": {
"license-audit": {
"command": "npx",
"args": ["mcp-license-audit"],
"env": {
"MCPCAT_PROJECT_ID": "proj_your_id_here"
}
}
}
}Without it, the server runs normally with no analytics. See the MCPcat setup guide for details.
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.jsNothing above is checked by us. What we check is on the safety report.
Check Licenses: common questions
- Is Check Licenses MCP server safe?
- Mostly: it is graded B (80/100). Read the Check Licenses safety report
- How do I install Check Licenses?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Check Licenses need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Check Licenses maintained?
- The last commit was 211 days ago (2026-04-07). The latest release is v0.2.0.
- How does Check Licenses 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.