LicenseGuard
LicenseGuard is an MCP server that evaluates open-source dependency licenses against your distribution model and returns practical verdicts (allowed, review, blocked) with cited obligations.
Check a single dependency (
check_dependency_license): before adding or auditing one package, providing ecosystem, name, version, dependency scope, and how you ship the software.Scan entire manifests/lockfiles (
check_manifest_licenses): audit package-lock.json, pnpm-lock.yaml, yarn.lock, go.sum, Cargo.lock, poetry.lock, uv.lock, package.json, requirements.txt, go.mod, Cargo.toml and more, including transitive dependencies.Explain any license (
explain_license): get what a license requires across every shipping model at once, with optional linkage (dynamic/static/separate-process) for LGPL-family licenses.Choose a distribution model for each check: SaaS, distributed binary, on-prem delivery, internal-only, or library-published.
Use scope awareness for dependencies: runtime vs dev/build/test/optional, so build-time and dev dependencies that never ship are not treated as obligations.
Get actionable output: each check returns the license, verdict, obligations list, rationale, and a reference citation.
Works through the MCP protocol for coding agents and also exposes the same policy engine via a hosted HTTP endpoint and JSON API.
Checks npm package licenses against the project's distribution model, scanning package.json and package-lock.json files and resolving licenses from the npm registry.
Reviews .NET dependency licenses from packages.lock.json, .csproj, Directory.Packages.props, and packages.config, resolving license information from NuGet.
Audits Python dependency licenses using manifests such as requirements.txt, pyproject.toml, poetry.lock, and uv.lock, resolving package licenses from PyPI.
Scans Gemfile.lock and checks Ruby gem licenses against the selected distribution model using RubyGems registry data.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@LicenseGuard Can I use AGPL-3.0 in our commercial SaaS?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
LicenseGuard
A tool that determines whether the licenses of your OSS dependencies create legal obligations for your distribution model.
Production: https://license-guard.rcc-aoki.workers.dev
What's different
Existing license compliance products fall into two camps: "deep analysis but requires a sales call (FOSSA / Black Duck)" or "self-serve but shallow analysis (Snyk)"—and no product exists at the intersection.
The core differentiator is the analysis layer. The same license can lead to completely opposite conclusions depending on context.
Usage | AGPL-3.0 consequences |
Provided externally as a SaaS | Disclosure obligation applies |
Used only in internal systems | No obligation |
Delivered or distributed to customers | Disclosure obligation applies |
devDependency (not included in the deliverable) | No obligation |
The last row is decisive. Most existing tools don't distinguish between dev and runtime dependencies, so they raise warnings that cry wolf and get ignored.
Related MCP server: gridwork-license
Using it from an agent
The need for this product arises not when you're searching the browser, but when you're adding a dependency. So the primary placement isn't search results—it's the agent's toolset.
claude mcp add licenseguard --transport http https://license-guard.rcc-aoki.workers.dev/mcpStateless Streamable HTTP, no authentication required. Tools provided:
Tool | Purpose |
| Call before adding a single dependency |
| Audit an entire manifest |
| Explain what a license requires across all distribution models |
The JSON API returns the same analysis.
curl "https://license-guard.rcc-aoki.workers.dev/api/pkg/pypi/pyload-ng?model=saas"
# => {"license":"AGPL-3.0-only","verdict":"blocked", ...}The agent-facing entry point is consolidated at /llms.txt.
Current phase
Phase 0 (validating willingness to pay) — MCP server and free web tool are published. Since the main battlefield is agent workflows rather than search, the validation metric isn't CTA click-through rate but MCP adoption and sustained call volume. The GitHub App (Phase 1) will be started after reviewing the validation results.
Supported ecosystems: npm / PyPI / Go modules / crates.io (Rust)
Format | Transitive dependencies | External lookup |
| Yes | Not needed (includes licenses) |
| Yes | Needed (amortized via shared cache) |
| Yes | Needed |
| Yes | Needed |
| ✗ direct dependencies only | Needed |
Passing a lock file lets you analyze transitive dependencies too (package-lock.json / pnpm-lock.yaml / yarn.lock).
Of these, package-lock.json includes license information, so no external lookup is needed at all. Lock files
include license information, so no external lookup is needed at all, and the exact versions actually installed
can be used as-is. Problematic licenses are more likely to sneak in as dependencies of dependencies than as directly added dependencies, so this is the real main event.
curl -X POST https://license-guard.rcc-aoki.workers.dev/api/scan -H 'content-type: application/json' -d "$(jq -Rs '{content: ., distributionModel: "saas"}' package-lock.json)"Development
npm install
npm test # 全テスト
npm run typecheck
npm run smoke # 実レジストリへの疎通確認
npm run e2e # 本番に対する E2E 6種
# ui Playwright で実ブラウザ
# a11y アクセシビリティ
# mcp 公式 MCP SDK クライアント
# load 並列実行時の一貫性
# adversarial 敵対的入力・境界値
# correctness 既知の正解との突き合わせ
# operational 経路間の一致・HTTP・キャッシュ
npm run dev # http://localhost:8787Even if all unit tests pass, some defects only surface when you run real data.
smoke and e2e run against production-equivalent external dependencies, so be sure to run them before every release.
Deployment:
npm run db:migrate
npm run deployDocumentation
Design spec: docs/specs/2026-08-19-license-guard-design.md
Phase 0 implementation plan: docs/superpowers/plans/2026-08-19-phase0-free-web-tool.md
Dependency OSS
Given the subject matter this product itself handles, all dependencies are limited to MIT / Apache-2.0 families. No disclosure obligation arises for our own SaaS.
Role | OSS | License |
SPDX expression parsing |
| MIT |
Web framework |
| MIT |
Go license data | ClearlyDefined API | Apache-2.0 |
Disclaimer
This tool presents information based on published license texts and dependency manifests—not legal advice. No attorney-client relationship is established by its use. The analysis is based on the license information declared in the manifest and does not cover all obligations or violations.
Available Tools
3 toolscheck_dependency_licenseCheck one dependency for license obligationsAInspect
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 license obligates you and the dependency should be replaced or the shipping model reconsidered.
Inputs: name (required), ecosystem (required), distribution_model (required), scope, +1 more. Returns: license, verdict, rationale, reference, +1 more
check_manifest_licensesCheck a whole manifestAInspect
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 arrive as transitive dependencies rather than ones you added directly, and only a lockfile reveals those.
Inputs: content (required), distribution_model (required).
explain_licenseExplain what a license requiresAInspect
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 safely depend on.
Inputs: license (required), linkage.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: explain_license focuses on understanding a license itself, check_dependency_license evaluates a single dependency in context, and check_manifest_licenses scans an entire manifest. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern (explain_license, check_dependency_license, check_manifest_licenses). The only minor deviation is that two tools start with 'check' while the third uses 'explain', but this is justified by the different action types.
With only 3 tools, the server is slightly on the lean side, but each tool covers a distinct and essential aspect of license management (understanding, single-dependency check, full-manifest scan). The count is appropriate for a focused utility server.
The tool surface covers the core workflows: understanding licenses, checking individual dependencies, and scanning entire manifests. A minor gap is the lack of a tool to handle bulk license explanations or compare multiple licenses directly, but the existing tools cover the primary use cases well.
Maintenance
Related MCP Connectors
Open-source licence risk checks for AI coding agents and dependency trees.
Zero-log MCP server with 49 tools for AI guardrails, secret scanning, MCP linting & EU compliance.
Scan any MCP server for tool-poisoning, security, auth & license. Trust score before install.
Remote MCP for tool license checks, vendor policy review, alternatives, and license receipts.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceDepGuard is an MCP server for real-time dependency safety checks, verifying packages against vulnerability databases, deprecation metadata, and a local cache.MIT

gridwork-licenseofficial
AlicenseAqualityDmaintenanceScans project dependencies for license compliance, classifying 60+ licenses and detecting conflicts and copyleft risks.428 npm1MIT- AlicenseNot gradedqualityBmaintenanceA lightweight MCP server for security reviews that injects security requirements before code generation, scans dependencies for CVEs, and verifies generated code without disrupting workflow.73MIT
- AlicenseCqualityCmaintenanceGuardRail MCP is an enterprise agent security server that provides multi-language code analysis, dependency scanning, and container security checks, with RBAC, policy packs, and audit logging.23MIT