Mcp Check Licenses

io.github.webmoleaiPublished by GitHub account webmoleaiv0.2.0Updated Nov 3, 2026

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

The publisher's own server: check.tattoo: tattoo size and placement guide

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A local MCP server that audits project dependency licenses and flags GPL/AGPL compatibility conflicts for an assistant.

What you can do
  • Audit dependency licenses across a project and report compatibility issues.
  • Flag GPL/AGPL conflicts that could affect how a project may be distributed.
  • No individual tools are documented, so the exact commands and output format are not described in the available material.
When to use it
Useful when checking whether a project's third-party dependencies carry licenses that conflict with your intended distribution, especially before releasing or open-sourcing code.
Requirements
Runs as a local process over stdio, installed from the npm package mcp-check-licenses, so Node.js and npm are needed. No authentication, environment variables or headers are declared. Desktop-only; not available as a web executable.
Before you install
It reads dependency and license metadata from your project, so review what it inspects before running it on private code. No tools, permissions or data handling are documented, so verify behavior before relying on its results for compliance decisions.

Installation

In SourceWeft

  1. Open Mcp Check Licenses in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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

bash
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:

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

Or if installed globally:

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

Analytics

This server supports MCPcat analytics. To enable usage tracking, session replay, and error monitoring, set the MCPCAT_PROJECT_ID environment variable in your MCP client config:

json
{  "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:

json
{  "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

bash
npm installnpm run buildnode dist/index.js

Source: README.md at commit 4dca1ce

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Check integrations