explain_license

3 registry entries were observed exposing a tool named explain_license — none of them flagged as a privileged capability.

Spelled explain_license, explain-license in the wild — all one tool for the purposes of this page.

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 12,336 of 40,577 scannable entries (30%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.

  1. io.github.bighippoman/license-complianceMCPcommunitytrust 60/100 · B
    v1.0.2

    Scan npm dependencies for license compliance issues. Catch GPL contamination.

    ClaudeCursorCopilotGemini
    io.github.bighippomanUnknown7mo agonpmGitHubobserved · static extraction
    mcp
  2. io.github.rccaoki-wq/license-guardMCPcommunitylivetrust 60/100 · B
    v1.1.0

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

    ClaudeCursorCopilotChatGPTGemini
    io.github.rccaoki-wqUnknown1mo agoGitHubobserved · static extraction
    mcp
  3. license-guardian-mcpMCPcommunitytrust 60/100 · B
    v0.1.0

    Audit the LICENSE of every npm dependency before you ship. Resolves each dependency's real license from the live npm registry and flags GPL/AGPL/LGPL copyleft, BUSL/SSPL/Elastic source-available, non-commercial and unlicensed packages incompatible with yo

    ClaudeCursorCopilotGemini
    license-guardianMIT3mo agonpmGitHubobserved · static extraction
    mcpmodel-context-protocolnpmlicenselicense-compliancespdx

All indexed toolsSearch the registry for explain_license