io.github.wgd5678/license-sentinel
PYPI · LICENSE-SENTINEL
Audit Python and npm dependency licenses before you ship, judged against how you distribute.
Available components
Last scanned (1 day ago)
Scores higher than 80% of PyPI servers
Category Security
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 28 dependencies flagged as unhealthy. 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 56 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 374 tokens (~124/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 4 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −20
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.63 functional
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 25 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 24 Oct 26 −15
- Malware scan: pass → unverified ▼ security
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 4 Nov 2026 · Analysed pypi/license-sentinel@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 1 |
| 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 →
audit_project ~135
Scan a project's dependencies and report licensing risk. Args: path: Project directory to scan. Defaults to the current directory. context: How you distribute your product. One of ``proprietary`` (closed-source product you distribute), ``saas-backend`` (you only run it, never distribute), ``permissive`` (your own project is MIT/Apache/BSD), ``copyleft-ok`` (your own project is GPL family). Returns: Counts per verdict plus every BLOCK and REVIEW item with the reason.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | – |
| path | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
check_package ~161
Check packages or raw license strings before installing them. Args: names: Package or license strings to check. Accepts the messy real-world forms: ``AGPL-3.0``, ``BUSL-1.1``, ``GPLv3``, ``Apache License 2.0``, ``MIT OR Apache-2.0``, or a comma-separated string of any of these. These are license strings, not package lookups: to audit what is actually installed in a project directory, use ``audit_project``. context: Distribution context, see ``audit_project``. Returns: One line per input with its verdict and the reason.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | – |
| names | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
generate_notices ~78
Write a THIRD-PARTY-NOTICES.md attribution document for client hand-off. Args: path: Project directory to scan. output: Output file. Relative paths are resolved against ``path``. Returns: The absolute path written and how many dependencies were listed.
| Name | Type | Req | Description |
|---|---|---|---|
| output | string | – | – |
| path | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the io.github.wgd5678/license-sentinel MCP server?
io.github.wgd5678/license-sentinel runs locally as a PyPI package, launched with uvx license-sentinel. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · license-sentinel
claude mcp add wgd5678-license-sentinel -- uvx license-sentinel
What is the io.github.wgd5678/license-sentinel MCP server?
io.github.wgd5678/license-sentinel is an MCP server listed in the public MCP registry as io.github.wgd5678/license-sentinel. Audit Python and npm dependency licenses before you ship, judged against how you distribute. This page covers its PyPI package (license-sentinel).
Is the io.github.wgd5678/license-sentinel MCP server safe to use?
io.github.wgd5678/license-sentinel scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. 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.wgd5678/license-sentinel MCP server expose?
io.github.wgd5678/license-sentinel exposes 3 tools: audit_project, check_package, generate_notices. Their descriptions and schemas cost roughly 374 tokens of context every time the server is loaded.
Is the io.github.wgd5678/license-sentinel MCP server still maintained?
io.github.wgd5678/license-sentinel is still listed as active in the MCP registry. We last reached this channel on 4 November 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.wgd5678/license-sentinel MCP server under?
io.github.wgd5678/license-sentinel declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.