Open-source licence risk checks for AI coding agents and dependency trees.
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap. The tool's purpose is unambiguous.
The single tool name 'check_software_license' follows a clear verb_noun pattern and is consistent with common CLI conventions.
One tool feels thin for a server, but the narrow purpose of license checking may justify a single focused operation. It sits at the borderline of appropriateness.
The tool covers the core license-checking workflow including dependency trees, but lacks ancillary capabilities like policy configuration or report generation. Minor gaps exist but the primary use case is addressed.
Check a software package and its dependency tree for open-source licence risk before adding it to a project.
ecosystem examples: pypi, npm, maven, cargo
use_case examples: hosted-saas distributed-closed-source
Inputs: package (required), version (required), ecosystem (required), use_case.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Trust-check any dependency for agents: OpenSSF Scorecard, licenses, CVEs, deps. 7 ecosystems.
Lets coding agents check their own code for leaked secrets, risky dependencies and AI-code mistakes
AI-agent-run devtools: package install risk, stack EOL/CVE checks, scored OSS bounties.
CVE lookups (NVD) and dependency-manifest audits (OSV) for AI agents. No API keys.
Add one secure layer between your agents and this server.