dependency-license-change-mcp
PulseGate's liveness check found it on 24 Sep 2026; it has been in the index since 24 Sep 2026. How this is checked
dependency-license-change-mcp is an MCP-based developer tool that performs local analysis of dependency license changes. It helps developers and compliance teams inspect software dependencies and identify licensing changes while keeping analysis within local privacy boundaries.
Inferred · not functionally tested
Overview
6 featuresPurpose: Detecting and analyzing license changes in software dependencies before they create compliance or release risks.
Inferred · not functionally tested
Audience: software developers and open-source compliance teams
Inferred · not functionally tested
Functions: data_extraction
Inferred · not functionally tested
Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)
Recorded constraints: pricing: unknown · license: Proprietary · platforms: CLI, WEB · deployment: browser, cli, api_only, self_hosted
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: github.com. These links do not verify the individual claims.
dependency-license-change-mcp is an Other dev tools project. Inferred · not functionally tested: It focuses on detecting and analyzing license changes in software dependencies before they create compliance or release risks. Inferred · not functionally tested: It is built as an open-source project for software developers and open-source compliance teams. Basis unknown · not verified: It ships for the web, the command line, and API, and it can be self-hosted.
It is developed by mrfentmen. Inferred · not functionally tested: Among its 6 catalogued features are dependency analysis, license change detection, and local analysis. Inferred · not functionally tested: Catalogued interfaces include an MCP server.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Dependency analysis
- License change detection
- Local analysis
- Privacy boundaries
- MCP server
- NPM installation
Topics: Inferred · not functionally tested
Built with & integrations
Trust & compliance
Indexing history
1What PulseGate has recorded for this listing
- Indexed21 Sep · 20:55 UTCio.github.mrfentmen/dependency-license-change-mcp seen via MCP Registry (official)Source: MCP Registry (official) · Open
Frequently asked questions about dependency-license-change-mcp
- What does dependency-license-change-mcp do?
- Inferred · not functionally tested: Dependency-license-change-mcp focuses on detecting and analyzing license changes in software dependencies before they create compliance or release risks. It is catalogued under Other dev tools on PulseGate.
- Who should use dependency-license-change-mcp?
- Inferred · not functionally tested: dependency-license-change-mcp is an open-source project built for software developers and open-source compliance teams.
- What platforms does dependency-license-change-mcp run on?
- Basis unknown · not verified: dependency-license-change-mcp runs on the web, the command line, and API. It can also be self-hosted.
- Is dependency-license-change-mcp still active?
- PulseGate's liveness check found it on 24 Sep 2026.
- What are alternatives to dependency-license-change-mcp?
- Similar projects tracked by PulseGate include license-boundary-mcp, dependency-compat-mcp, and runtime-support-mcp.license-boundary-mcpdependency-compat-mcpruntime-support-mcp
- Who makes dependency-license-change-mcp?
- dependency-license-change-mcp is developed by mrfentmen.
- Does dependency-license-change-mcp have an API or integrations?
- Inferred · not functionally tested: Yes — dependency-license-change-mcp exposes an MCP server.
Similar projects
Closest matches by what these projects do