io.github.rccaoki-wq/license-guard · v1.1.0 · developer-tools
LicenseGuard is healthy: it completed an MCP handshake in 854 ms and exposes 3 tools.
Check if a dependency's license obligates you, based on how you ship. npm, PyPI, Go.
Endpoint: https://license-guard.rcc-aoki.workers.dev/mcp (streamable-http)
Repository · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 3 |
| Latency | 854 ms |
| Last checked (UTC) | 2026-10-16T13:30:42.715Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-16T13:30:42.715Z | Healthy | 854 | |
| 2026-10-15T08:20:07.751Z | Healthy | 457 |
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 |