LicenseGuard

io.github.rccaoki-wq/license-guard · v1.1.0

Check if a dependency's license obligates you, based on how you ship. npm, PyPI, Go.

MCPremotelocal · ocino credentialsTransportLaw & government

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Reachable, 3 tools, protocol 2025-06-18 · checked 2026-10-17

B 80/100

What it does: 3 tools · 3 read, 0 write · Law & government

No tool could be tested safely. Only read-only tools that need no input are called.

How the rating is made

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Remote URL

https://license-guard.rcc-aoki.workers.dev/mcp

Package

registry:   oci
identifier: ghcr.io/rccaoki-wq/license-guard:1.1.0
transport:  stdio

3 tools listed at last check

check_dependency_license Determine whether adding or keeping a single open source dependency creates a legal obligation, given how this project ships. Call this BEFORE adding a new dependency to a project, and when auditing an existing one. A permissive result means no source-disclosure duty; a blocked result means the lice
check_manifest_licenses Scan an entire dependency manifest and report every dependency whose license creates an obligation for this shipping model. Use when reviewing a project as a whole, preparing for due diligence, or after a large dependency change. Pass a package-lock.json when one exists: problematic licenses usually
explain_license Given an SPDX license identifier or expression, explain what it requires across every shipping model at once. Use when the question is about the license itself rather than a specific package — for example when comparing AGPL-3.0 against GPL-3.0 for a hosted service, or deciding what a project may sa

Markdown for your README

[![Connect-MCP](https://clawy.uk/mcp/badge/io.github.rccaoki-wq/license-guard.svg)](https://clawy.uk/mcp/s/io.github.rccaoki-wq/license-guard)