What it does
Check if a dependency's license obligates you, based on how you ship. npm, PyPI, Go.
- Connects Computer or cloud
- Account or key No key needed
- Category Developer tools
Use together with
Skills that teach the AI this kind of work; they work alongside this one
andrej-karpathy-skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Why it ranks here
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 7/12 | Full marks for a release or code change within 30 days |
| Still answering | 8/8 | The cloud endpoint answered at the last check |
| Usage score | 15/100 |
Quality: Passed 5/5 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Install
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install LicenseGuard. Follow https://mcp.popnx.com/i/rccaoki-wq-license-guard.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 5/5 checks · What you ask goes through the maker’s server (license-guard.rcc-aoki.workers.dev) · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude · about 2 min
No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
Open Claude’s Connectors page
CustomizeConnectors
Click “Add” → “Custom” → “Web” and fill in these 2 fields
Copy each value into the field with the same name in Claude, then click Continue
Name · NameLicenseGuardRemote MCP server URL · Addresshttps://license-guard.rcc-aoki.workers.dev/mcpClick Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add
Turn it on in a chat
+ConnectorsLicenseGuard
Try it
Use LicenseGuard and tell me what you can do for me, then show me one thing✓ If Claude says it is using LicenseGuard or shows a LicenseGuard tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with ChatGPT, depending on your plan
Full MCP: ChatGPT Business, Enterprise or Edu on the web · Pro: connects with read/fetch permissions, so tools that change data may not work · Plus: not confirmed in OpenAI’s docs; if you see an add-custom-MCP option on the Plugins page you can try these steps · web only
Open ChatGPT’s add-MCP page on the web
Plugins+Add custom MCP server
Fill in the name and address
Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin
Name · NameLicenseGuardConnection · Addresshttps://license-guard.rcc-aoki.workers.dev/mcpPick LicenseGuard in a chat
Start a new chat and pick LicenseGuard from your plugins before typing
Try it
Use LicenseGuard and tell me what you can do for me, then show me one thing✓ If ChatGPT says it is using LicenseGuard or shows a LicenseGuard tool in the answer, you are connected
Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Claude Code · about 2 min
No key, nothing to install
Open Terminal
Mac: press Command+Space and type Terminal · Windows: open PowerShell
Paste this command and press Enter
claude mcp add --transport http --scope user license-guard https://license-guard.rcc-aoki.workers.dev/mcpType /mcp in Claude Code
You should see LicenseGuard listed as connected
Try it
Use LicenseGuard and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using LicenseGuard or shows a LicenseGuard tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor · about 2 min
No key, nothing to install
Open the AI chat in Cursor in Agent mode
Try it
Use LicenseGuard and tell me what you can do for me, then show me one thing✓ If Cursor says it is using LicenseGuard or shows a LicenseGuard tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code · about 2 min
No key, nothing to install
Open the AI chat in VS Code in Agent mode
Try it
Use LicenseGuard and tell me what you can do for me, then show me one thing✓ If VS Code says it is using LicenseGuard or shows a LicenseGuard tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
Address for apps that connect over the web
https://license-guard.rcc-aoki.workers.dev/mcpJSON settings are under “For developers” below
For developers: Terminal commands and JSON settings
Over the web
Claude Code
claude mcp add --transport http --scope user license-guard https://license-guard.rcc-aoki.workers.dev/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"license-guard": {
"url": "https://license-guard.rcc-aoki.workers.dev/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"license-guard": {
"type": "http",
"url": "https://license-guard.rcc-aoki.workers.dev/mcp"
}
}
}Installed on your computer
Claude Code
claude mcp add --scope user license-guard -- docker run -i --rm ghcr.io/rccaoki-wq/license-guard:1.1.0Claude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"license-guard": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/rccaoki-wq/license-guard:1.1.0"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"license-guard": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/rccaoki-wq/license-guard:1.1.0"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"license-guard": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/rccaoki-wq/license-guard:1.1.0"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
At a glance
Which apps can use it
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Related guides
What it can do
Tool names and descriptions exactly as the server reported them on Nov 15, 2026. The maker wrote them, not us; we show them as plain text.
check_dependency_licenseDetermine 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 r
check_manifest_licensesScan 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: problema
explain_licenseGiven 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 w
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account rccaoki-wq, which owns the repo
- ✓ Pass
Still maintained
Code last changed 3 months ago
- ✓ Pass
Has a licence
Uses Apache-2.0
- ✓ Pass
Endpoint responds
Responded in 99 ms (HTTP 200)
- – Not applicable
Sign-in with OAuth
No sign-in needed
- ✓ Pass
No hidden instructions in tool descriptions
Read 3 tool descriptions and found no hidden instructions to the AI
Published vulnerabilities (OSV.dev)
Not checked: only npm and PyPI packages with a version can be checked
Makers: ask for a re-check or report wrong info
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/rccaoki-wq-license-guard)Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
User reviews
No reviews yet
Compared with others in Developer toolsi
- More stars than 0% of the other 6182 servers in this category
- Published to the registry more recently than 27% of the other 6182 servers in this category
- Basic checks equal to or better than 99% of the other 6182 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is LicenseGuard safe?
It passed 5 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
Either way works: install it on your computer or connect to the cloud version.
Is it still maintained?
The GitHub repo last changed 3 months ago, and the latest version (1.1.0) reached the registry 3 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).
What can I use instead?
In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Similar alternatives
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Cloudflare MCP
Cloudflare MCP servers
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| This one LicenseGuard | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Runs where | Cloud or install on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Cloud or install on your computer |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | Yes | No | No |
| Basic checks | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| License | Apache-2.0 | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
LicenseGuard
*English | 日本語*
Also listed on mcpservers.org, Smithery, the TensorBlock MCP Index, and the Docker MCP catalog.
**Does this dependency's license create an obligation for the way *you* ship software?**
Generic license scanners answer a different question — "what license is this?" — and then warn on everything. LicenseGuard evaluates the license against your distribution model, so the same license produces different verdicts depending on how the software reaches its users.
Live: https://licenseguard.tenchorooms.com
The workers.dev origin below is the same deployment, kept as the stable endpoint the MCP catalogs point at.
Why does the distribution model decide it?
| How you ship | AGPL-3.0 dependency |
|---|---|
| SaaS (network-accessible) | blocked — §13 network clause |
| Internal use only | allowed |
| Distributed binary / on-prem | blocked — inherited GPL distribution terms |
| devDependency (never in the artifact) | allowed |
That last row is the whole point. A build-time linter under AGPL never ships, so it triggers nothing — but tools that warn on it anyway train people to ignore every warning they produce.
The same split runs through the rest of the license landscape, and the distinctions are not interchangeable:
- GPL obligations attach to *distribution*. Running GPL code as a network service is not distribution.
- AGPL adds §13, which attaches to *network interaction* — a separate trigger from GPL's distribution terms. Citing §13 for a distribution case is simply wrong, and LicenseGuard doesn't.
- MPL / EPL / CDDL are file-scoped and linkage-independent. MPL-2.0 §3.3 explicitly permits distributing a Larger Work under your own terms. Applying LGPL's relinking logic to them produces false positives.
- LGPL is the one that actually depends on linkage: static linking carries a relinking obligation, dynamic linking does not.
Verdicts are stated as facts with the clause cited. LicenseGuard does not tell you what to do.
Common questions
Does the GPL apply if I only host the software and never distribute it? No. GPL-3.0 triggers its obligations on distribution. Hosted SaaS is not distribution, so no obligation arises *today* — but shipping the same software later, as an on-prem deployment, a binary, or a published library, would trigger whole-work source disclosure.
Does the AGPL apply if I only host the software as a SaaS? Yes. AGPL-3.0 §13 requires that users interacting with a modified version over a network be offered the corresponding source of the whole work. This is the clause that makes AGPL behave differently from GPL for hosted services, and it is the entire practical difference between the two.
Do build-time and dev dependencies create license obligations? No. A dev dependency is not part of the artifact you ship, so distribution-triggered obligations do not arise. Tools that *emit code into your output*, such as code generators, are a separate case worth checking individually.
Is MIT safe for commercial use? Yes, in every distribution model. MIT asks for attribution and nothing more. Apache-2.0 reaches the same result while adding a patent grant and a NOTICE requirement — obligations, but ones that do not vary by how you ship.
Does static linking change the answer? Only for LGPL, and only for compiled languages. LGPL's design is that you may use the library in a proprietary work provided the user can replace it, which dynamic linking gives you and static linking does not. Go and Rust link statically by default, and nothing in Cargo.lock or go.sum says so.
Why does the same license give different answers for different projects? Because copyleft obligations attach to *events* — distributing, or letting users interact over a network — not to the presence of the code. Whether those events happen is a fact about your business, not about your repository, which is why a scanner that only reads your lockfile cannot decide it.
Use it from your coding agent
You need this when you are adding a dependency, not when you are searching the web. So the primary surface is an MCP tool, not a search result.
Hosted — nothing to install:
claude mcp add licenseguard --transport http https://license-guard.rcc-aoki.workers.dev/mcp
Local (stdio) — your manifest never leaves your machine. Only package names and versions are sent to public registries to look up licenses:
claude mcp add licenseguard -- docker run -i --rm ghcr.io/rccaoki-wq/license-guard:1.1.0
The image is published on every release and declared as an OCI package in the official MCP registry, so clients that read the registry can install it without any of this. To build it yourself instead: docker build -t licenseguard . && docker run -i --rm licenseguard.
Both paths run the same policy engine. They cannot disagree — an end-to-end suite (npm run e2e:stdio) pins them together.
Stateless Streamable HTTP, no authentication, no session state.
| Tool | When to call it |
|---|---|
check_dependency_license | Before adding a single dependency |
check_manifest_licenses | To audit a whole manifest or lockfile |
explain_license | To see what a license requires across every distribution model |
Use it from anything else
The JSON API returns the same verdicts:
curl "https://license-guard.rcc-aoki.workers.dev/api/pkg/pypi/pyload-ng?model=saas"
=> {"license":"AGPL-3.0-only","verdict":"blocked", ...}
Scan a whole lockfile:
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)"
An agent-facing index lives at /llms.txt.
Supported manifests
Ecosystems: npm · PyPI · Go modules · crates.io · RubyGems · NuGet
| Format | Transitive deps | Registry lookups |
|---|---|---|
package-lock.json | yes | none — licenses are embedded |
pnpm-lock.yaml, yarn.lock | yes | yes (amortized by a shared cache) |
go.sum | yes | yes |
Cargo.lock, poetry.lock, uv.lock | yes | yes |
Gemfile.lock | yes | yes |
packages.lock.json | yes | yes |
package.json, requirements.txt, pyproject.toml, go.mod, Cargo.toml | direct only | yes |
.csproj, Directory.Packages.props, packages.config | direct only | yes |
| CycloneDX (JSON), SPDX (JSON) | yes | only where the document has no license |
Problem licenses usually arrive as a dependency of a dependency, not as something you added on purpose — so the lockfile path is the one that matters. package-lock.json v2/v3 embeds a license for every entry, which means a full transitive audit with zero network lookups and the exact versions that will actually be installed.
An incomplete scan is never reported as clean. Dependencies that could not be resolved appear as not-checked or review and are counted in the summary. They never become allowed.
A single scan performs at most 300 registry lookups, which bounds what one request can cost. Cached packages don't consume that budget, so the ceiling only binds on packages nobody has looked up yet — a first scan of a ~1000-crate Cargo.lock typically leaves a few dozen entries marked not-checked, and scanning again resolves them (measured: servo's 1043 crates reach zero unresolved published crates on the second pass). The result says so explicitly rather than quietly showing a shorter list.
Git dependencies and members of the workspace being scanned are reported as not-published instead, across every format that identifies them — Cargo.lock's source field, yarn's workspace: and git+ protocols, pnpm's tarball URLs, and package-lock.json's resolved. No public registry has license data for them, so they are never looked up. That is a different situation from hitting the lookup limit: re-scanning will not resolve them, and the result says so.
This matters for more than speed. A workspace member named after a package that also exists publicly — utils, core, or anything else generic — would otherwise be resolved against that unrelated public package and reported as allowed, because the workspace version (0.0.0-use.local) matches nothing and the lookup falls back to the latest release. Marking the origin is what stops a private package from inheriting a stranger's license.
Private registries are the deliberate exception. A resolved URL pointing somewhere other than npmjs is just as likely to be a transparent Artifactory or Nexus proxy serving the real public package, and nothing in the lockfile distinguishes the two — so those are still looked up, and still reported as unresolved if they fail.
SBOMs
CycloneDX and SPDX are read in JSON, including GitHub's {"sbom": …} envelope, so the response of gh api repos/OWNER/REPO/dependency-graph/sbom can be pasted unmodified. A license recorded in the document is used as-is; components without one are looked up. NOASSERTION, NONE, and LicenseRef-* are not treated as declarations, because they are the document saying it does not know.
Two things about real SBOMs are reported rather than smoothed over, because both change what the result means:
Most components carry no usable license. Across five published GitHub SBOMs, the document supplied the license for 8 of 44 components in expressjs/express and 1 of 51 in tokio-rs/tokio. The rest were resolved against a registry today. The result states the split instead of claiming the licenses came from the document.
A version range is not a version. GitHub's dependency-graph export writes the manifest range — ^2.0.0, >= 0.2.42,< 0.3.0 — into the purl *and* the version field: 36 of 44 components in express, 50 of 51 in tokio. There is no release under that string, so a scanner that passes it through resolves against the latest release while displaying a version that is not in your artifact. Ranges are not accepted as versions, and the result says how many components were affected. A lockfile does not have this problem, which is the practical reason to prefer one.
Components that are left out are counted and named rather than dropped, and the reason matters more than the count. GitHub Actions are not a gap. They run in CI, never enter the artifact, and so cannot create a distribution or network obligation — which is why they are excluded, and the result says exactly that instead of filing them under "unsupported". This is the difference between a fact about your software and a limitation of the tool, and it is not a rounding error: 52 of the 194 components across those five SBOMs are githubactions, the second-largest type after cargo. Package types the scan genuinely cannot read (maven, deb, …) are reported separately.
A document where *nothing* is checkable is rejected with the reason, not returned as an empty clean report — and the two reasons differ. gorilla/mux's SBOM is 100% GitHub Actions, so the answer is that the document contains nothing you ship; looking for a different scanner will not change that.
Status
Phase 0 — validating willingness to pay. The MCP server and the free web too