# License Compatibility Checker MCP

> License Compatibility Checker MCP allows you to audit software licenses and check for legal conflicts between project dependencies. It simplifies the much harder task of manual license auditing, making it easy to integrate into your AI agent's workflow to ensure compliance with open-source components in your codebase. Use it to validate SPDX identifiers and evaluate risk levels across your entire dependency tree.

## Overview
- **Category:** security
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_suaTXifolVW9InIcZfvX1wlSNsp3Y2H4VthlLzZ1/mcp
- **Tags:** license, spdx, compliance, audit, software, legal-tech

## Description

Checking software licenses manually is a nightmare for developers and legal teams. You spend hours scanning through package managers, digging through nested dependencies, and trying to figure out' if an MIT or GPL license actually conflicts with your project's goals. This MCP changes that by letting your AI agent act as a specialized verification engine. Instead of you hunting down every single file, your agent can instantly check the validity of SPDX IDs and evaluate potential legal risks across your entire dependency tree. You can even ask it to generate high-level audit reports that summarize the compliance risk for your project. Since this MCP is part of the Vinkius catalog, you can connect it once to any compatible client like Claude or Cursor and immediately start auditing your codebases with much more confidence in your legal standing.

## Prompt Examples

**Prompt:** 
```
Is 'MIT' a valid SPDX identifier?
```

**Response:** 
```
Yes, 'MIT' is a recognized and valid SPDX identifier.
```

**Prompt:** 
```
Check compatibility between 'GPL-3.0' and 'Apache-2.0'.
```

**Response:** 
```
The compatibility status is incompatible because GPL-3.0 is a strong copyleft license.
```

**Prompt:** 
```
Summarize the risk for an MIT project with dependencies: ['LGPL-2.1', 'Apache-2.0'].
```

**Response:** 
```
The overall risk score is Medium, and active obligations include Attribution requirement and Library-handling obligations.
```

## Capabilities

### Validate SPDX IDs
Check if a specific license identifier is officially recognized as a valid SPDX ID.

### Detect License Conflicts
It identifies when a project's primary license and its dependencies have incompatible or conflicting legal obligations.

### Generate Audit Reports
Creates a high-level summary of compliance risk levels for your entire dependency tree structure.

###  NIST/SPDX standard compliance check
undefined

## How It Works

1. Connect the License Compatibility Checker MCP to your preferred AI client.
2. Provide your agent with a list of or path to your dependency files (like package.json or requirements.txt).
3. Ask your agent to check for any license conflicts or summarize the scope of ability to use components in your proprietaryetary proprietary proprietary proprietary proprietary proprietary proprietary proprietary proprietary proprietary proprietary proprietary proprietary proprietary proprietary proprietary proprietary proprietary proprietary proprietary proprietary proprietary proprietary proprietary proprietary proprietary proprietary proprietary proprietary proprietary proprietary proprietary

## Frequently Asked Questions

**How do I check if a license is valid?**
Use the `verify_spdx_identifier` tool with the SPDX ID you want to validate. Tools available: `your_tool_name`.

**Can it detect GPL conflicts?**
Yes, `check_pair_compatibility` identifies when strong copyleft licenses create incompatibility.

**Does it support bulk analysis?**
Yes, `summarize_compliance_risk` analyzes an entire list of dependencies at once.