
Dependency License Change Mcp
io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.1Updated Oct 24, 2026
Compare local license evidence across two snapshots without returning package names, text,...
Overview
A local MCP server that compares license evidence between two snapshots of a project's dependencies without returning package names or license text.
- What you can do
- Compare license evidence recorded in two local snapshots of a project's dependencies and report what changed between them. The comparison is designed to avoid returning package names, license text and similar raw details, so results stay summarized rather than exposing the underlying entries. It runs as a local process on the user's machine over stdio.
- When to use it
- Useful when you want an assistant to check whether dependency licensing shifted between two points in a project, for example before a release or after a dependency update, while keeping package names and license text out of the conversation.
- Requirements
- Runs as a local process started on the user's machine over stdio, installed from the npm package dependency-license-change-mcp, so a Node.js runtime is needed. Desktop only; no authentication, environment variables or headers are declared. Two local license snapshots are needed to compare.
Installation
In SourceWeft
- Open Dependency License Change Mcp in the dashboard and add it to a workspace.
- 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
dependency-license-change-mcp
Dependency License Change compares license evidence across two local snapshots and reports category changes without exposing package names or license text.
Quick start
Set LICENSE_CHANGE_ROOT, then call compare_license_evidence with before and after snapshot paths.
Limits
Only aggregate categories and counts are returned. Classification is conservative and is not legal advice.
Source: README.md at commit e6291d3
Tools
0Version history
1- v1.0.1LatestSep 22, 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.