# LicenseGuard (remote · license-guard.rcc-aoki.workers.dev)

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

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `license-guard.rcc-aoki.workers.dev`: 83/100 (this document), [markdown](https://verifymcp.io/servers/rccaoki-wq-license-guard/license-guard.md), [page](https://verifymcp.io/servers/rccaoki-wq-license-guard/license-guard)
- oci · `ghcr.io/rccaoki-wq/license-guard:1.1.0`: 53/100, [markdown](https://verifymcp.io/servers/rccaoki-wq-license-guard/ghcr-io-rccaoki-wq-license-guard-1-1-0.md), [page](https://verifymcp.io/servers/rccaoki-wq-license-guard/ghcr-io-rccaoki-wq-license-guard-1-1-0)

## Channel facts

- Endpoint: `https://license-guard.rcc-aoki.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 87/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1548 tokens (~67/item across 23 items; 3 tools + 20 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the LicenseGuard MCP server?

LicenseGuard is a hosted endpoint at https://license-guard.rcc-aoki.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http rccaoki-wq-license-guard 'https://license-guard.rcc-aoki.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "rccaoki-wq-license-guard": {
      "url": "https://license-guard.rcc-aoki.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "rccaoki-wq-license-guard": {
      "type": "http",
      "url": "https://license-guard.rcc-aoki.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.rccaoki-wq-license-guard]
url = "https://license-guard.rcc-aoki.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "rccaoki-wq-license-guard": {
      "type": "remote",
      "url": "https://license-guard.rcc-aoki.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add rccaoki-wq-license-guard --url 'https://license-guard.rcc-aoki.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  rccaoki-wq-license-guard:
    url: "https://license-guard.rcc-aoki.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "rccaoki-wq-license-guard": {
      "Transport": "http",
      "Url": "https://license-guard.rcc-aoki.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add rccaoki-wq-license-guard -t streamable-http -u 'https://license-guard.rcc-aoki.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "rccaoki-wq-license-guard": {
      "type": "http",
      "url": "https://license-guard.rcc-aoki.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 83, +1)

- [security] Stability: 0.97 → pass

### 2026-09-17 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-03 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (3)

### `check_dependency_license` (~285 tokens)

Check one dependency for license obligations

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.

Input parameters:

- `distribution_model` (string, required): How the software incorporating this dependency reaches its users. This determines the answer: "saas" = users reach it over a network; "distributed-binary" = shipped as an app or binary; "on-prem-deli…
- `ecosystem` (string, required): Package registry the dependency comes from.
- `name` (string, required): Package name as written in the manifest, e.g. "express", "requests", "github.com/gin-gonic/gin", or "serde".
- `scope` (string): Where the dependency sits. Use "dev", "build", or "test" for anything that does not end up in the shipped artifact — those carry no distribution obligation. Defaults to "runtime".
- `version` (string): Exact version if known. Omit to use the latest published version, which may differ from what is installed.

Output parameters:

- `assumption` (object)
- `license` (string|null)
- `obligations` (array)
- `rationale` (string)
- `reference` (string)
- `verdict` (string)

### `check_manifest_licenses` (~327 tokens)

Check a whole manifest

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.

Input parameters:

- `content` (string, required): Full text of a lockfile, SBOM, or manifest. Accepted: package-lock.json, pnpm-lock.yaml, yarn.lock, go.sum, Cargo.lock, poetry.lock, uv.lock, Gemfile.lock, packages.lock.json, CycloneDX (JSON), SPDX…
- `distribution_model` (string, required): How the software incorporating this dependency reaches its users. This determines the answer: "saas" = users reach it over a network; "distributed-binary" = shipped as an app or binary; "on-prem-deli…

Output parameters:

- `distributionModel` (string)
- `ecosystem` (string)
- `findings` (array)
- `limitations` (array): What this scan could not establish. Never empty when anything was left unresolved. Read it before treating a result as clean.
- `summary` (object): Counts by verdict. total is every dependency found, not only the ones that were resolved.

### `explain_license` (~151 tokens)

Explain what a license requires

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.

Input parameters:

- `license` (string, required): SPDX identifier or expression, e.g. "AGPL-3.0-only", "Apache-2.0", or "(MIT OR GPL-2.0-only)".
- `linkage` (string): How the dependency is linked. Matters for LGPL-family licenses. Compiled languages such as Go and Rust normally link statically. Defaults to "dynamic".

Output parameters:

- `byDistributionModel` (array): One row per way of shipping. This is where the same license diverges.
- `devScope` (object): The result when the dependency never reaches users (dev, build or test scope). Independent of the shipping model.
- `license` (string)
- `linkage` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/rccaoki-wq-license-guard/license-guard#diagnostics

## Score history

- 2026-09-20: 83
- 2026-09-19: 83
- 2026-09-18: 82
- 2026-09-17: 82
- 2026-09-16: 81
- 2026-09-15: 81
- 2026-09-14: 80
- 2026-09-13: 80
- 2026-09-12: 80
- 2026-09-11: 79
- 2026-09-10: 79
- 2026-09-09: 78
- 2026-09-08: 78
- 2026-09-07: 77
- 2026-09-06: 77
- 2026-09-05: 76
- 2026-09-04: 76
- 2026-09-03: 76
- 2026-09-02: 75
- 2026-09-01: 75
- 2026-08-31: 74
- 2026-08-30: 74
- 2026-08-29: 73
- 2026-08-28: 73
- 2026-08-27: 72
- 2026-08-26: 72
- 2026-08-25: 70
- 2026-08-24: 70
- 2026-08-23: 69
- 2026-08-22: 69

## Common questions

### What is the LicenseGuard MCP server?

LicenseGuard is an MCP server listed in the public MCP registry as io.github.rccaoki-wq/license-guard. Check if a dependency's license obligates you, based on how you ship. npm, PyPI, Go. This page covers its hosted endpoint (https://license-guard.rcc-aoki.workers.dev/mcp).

### Is the LicenseGuard MCP server safe to use?

LicenseGuard scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the LicenseGuard MCP server expose?

LicenseGuard exposes 3 tools: check_dependency_license, check_manifest_licenses, explain_license. Their descriptions and schemas cost roughly 763 tokens of context every time the server is loaded.

### Does the LicenseGuard MCP server require authentication?

No. We connected to LicenseGuard without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the LicenseGuard MCP server still maintained?

LicenseGuard is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://license-guard.rcc-aoki.workers.dev/mcp
- Repository: https://github.com/rccaoki-wq/license-guard
- Website: https://license-guard.rcc-aoki.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/rccaoki-wq-license-guard/license-guard.xml
- Changelog JSON feed: https://verifymcp.io/servers/rccaoki-wq-license-guard/license-guard.json
- HTML version of this page: https://verifymcp.io/servers/rccaoki-wq-license-guard/license-guard