# LicenseGuard

- Registry name: `io.github.rccaoki-wq/license-guard` · version 1.1.0
- Categories (automatic, keyword rules): Government & law
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.rccaoki-wq%2Flicense-guard
- Server page: https://mcpstation.net/s/io.github.rccaoki-wq--license-guard.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

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

## Tools (as reported by the server, not verified)

- `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

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html