LicenseGuard is a remote MCP server that gives an AI agent 3 tools, among them check_dependency_license, check_manifest_licenses, explain_license. It answers at https://license-guard.rcc-aoki.workers.dev/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 23 October 2026, succeeded.
Check if a dependency's license obligates you, based on how you ship. npm, PyPI, Go.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 mean Inputs: ecosystem, name, version, distribution_model, scope |
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 pac Inputs: content, distribution_model |
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 Inputs: license, linkage |
Every block below points at https://license-guard.rcc-aoki.workers.dev/mcp. Pick your client and copy.
claude mcp add --transport http licenseguard https://license-guard.rcc-aoki.workers.dev/mcp
{
"mcpServers": {
"licenseguard": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://license-guard.rcc-aoki.workers.dev/mcp"]
}
}
}{
"mcpServers": {
"licenseguard": {
"url": "https://license-guard.rcc-aoki.workers.dev/mcp"
}
}
}{
"servers": {
"licenseguard": {
"type": "http",
"url": "https://license-guard.rcc-aoki.workers.dev/mcp"
}
}
}{
"context_servers": {
"licenseguard": {
"url": "https://license-guard.rcc-aoki.workers.dev/mcp"
}
}
}{
"mcpServers": {
"licenseguard": {
"serverUrl": "https://license-guard.rcc-aoki.workers.dev/mcp"
}
}
}{
"mcpServers": {
"licenseguard": {
"url": "https://license-guard.rcc-aoki.workers.dev/mcp"
}
}
}name: LicenseGuard
version: 0.0.1
schema: v1
mcpServers:
- name: LicenseGuard
type: streamable-http
url: https://license-guard.rcc-aoki.workers.dev/mcp{
"mcpServers": {
"licenseguard": {
"httpUrl": "https://license-guard.rcc-aoki.workers.dev/mcp"
}
}
}{
"mcpServers": {
"licenseguard": {
"type": "http",
"url": "https://license-guard.rcc-aoki.workers.dev/mcp"
}
}
}{
"mcpServers": {
"licenseguard": {
"url": "https://license-guard.rcc-aoki.workers.dev/mcp"
}
}
}goose://extension?url=https%3A%2F%2Flicense-guard.rcc-aoki.workers.dev%2Fmcp&type=streamable_http&id=licenseguard&name=LicenseGuard
It answered our last check on 23 October 2026 in 291 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
3, as returned by the server's own tools/list on 20 September 2026: check_dependency_license, check_manifest_licenses, explain_license.
It answered our last check on 23 October 2026 in 291 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://license-guard.rcc-aoki.workers.dev/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.rccaoki-wq. Endpoint host: license-guard.rcc-aoki.workers.dev. ARD identifier: urn:air:io.github.rccaoki-wq:mcp:license-guard.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.