io.github.bighippoman/license-compliance
NPM · LICENSE-COMPLIANCE-MCP · SCANNED SEP 21
Scan npm dependencies for license compliance issues. Catch GPL contamination.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 49 of 156 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 198 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 201 tokens (~100/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.bighippoman/license-compliance MCP server?
io.github.bighippoman/license-compliance runs locally as an npm package, launched with npx -y license-compliance-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · license-compliance-mcp
claude mcp add bighippoman-license-compliance -- npx -y license-compliance-mcp
{
"mcpServers": {
"bighippoman-license-compliance": {
"command": "npx",
"args": [
"-y",
"license-compliance-mcp"
]
}
}
} {
"servers": {
"bighippoman-license-compliance": {
"command": "npx",
"args": [
"-y",
"license-compliance-mcp"
]
}
}
} codex mcp add bighippoman-license-compliance -- npx -y license-compliance-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bighippoman-license-compliance": {
"type": "local",
"command": [
"npx",
"-y",
"license-compliance-mcp"
],
"enabled": true
}
}
} openclaw mcp add bighippoman-license-compliance --command npx --arg -y --arg license-compliance-mcp
mcp_servers:
bighippoman-license-compliance:
command: "npx"
args: ["-y", "license-compliance-mcp"] {
"McpServers": {
"bighippoman-license-compliance": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"license-compliance-mcp"
]
}
}
} assistant mcp add bighippoman-license-compliance -t stdio -c npx -a -y license-compliance-mcp
{
"mcpServers": {
"bighippoman-license-compliance": {
"command": "npx",
"args": [
"-y",
"license-compliance-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −2
- Stability: pass → 0.83 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 15 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 10 Sept 26 −3
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed npm/license-compliance-mcp@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 156 packages
| Packages resolved | 156 |
|---|---|
| Deprecated | 2 |
| Stale | 48 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check-licenses Check License Compliance ~119
Scan a project's npm dependencies for license compliance issues. Checks all installed packages against a policy (permissive, weak-copyleft, copyleft, or a custom SPDX expression). Returns a detailed markdown report with any violations, warnings, and dependency chains.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute path to the project root (must contain package.json and node_modules) |
| policy | string | – | Policy preset ("permissive", "weak-copyleft", "copyleft") or a custom SPDX expression like "(MIT OR Apache-2.0)" |
No output schema declared.
No examples provided.
explain-license Explain License ~82
Explain what a specific SPDX license means in plain language. Covers permissions, conditions, limitations, compatibility with proprietary/open-source/SaaS use, and common gotchas. Supports 15 major licenses plus deprecated SPDX forms.
| Name | Type | Req | Description |
|---|---|---|---|
| license | string | yes | SPDX license identifier (e.g., "MIT", "GPL-3.0-only", "Apache-2.0") |
No output schema declared.
No examples provided.
What is the io.github.bighippoman/license-compliance MCP server?
io.github.bighippoman/license-compliance is an MCP server listed in the public MCP registry as io.github.bighippoman/license-compliance. Scan npm dependencies for license compliance issues. Catch GPL contamination. This page covers its npm package (license-compliance-mcp).
Is the io.github.bighippoman/license-compliance MCP server safe to use?
io.github.bighippoman/license-compliance scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. 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 io.github.bighippoman/license-compliance MCP server expose?
io.github.bighippoman/license-compliance exposes 2 tools: check-licenses, explain-license. Their descriptions and schemas cost roughly 201 tokens of context every time the server is loaded.
Is the io.github.bighippoman/license-compliance MCP server still maintained?
io.github.bighippoman/license-compliance is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.bighippoman/license-compliance MCP server under?
io.github.bighippoman/license-compliance declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.