Skip to main content
Glama
TheoryofShadows

@mcpx-digital/license-scan

by TheoryofShadows
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to @mcpx-digital/license-scan

No user-submitted related servers found.

    Related Servers

    • license-compliance-mcp

      bighippoman
      A
      license
      A
      quality
      F
      maintenance
      Scans npm project dependencies for license compliance issues, detecting GPL contamination and generating detailed reports.
      2
      41 npm
      MIT

    • License Scanner MCP Server

      RyanCadby
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables scanning of project dependencies across multiple package managers (npm, pip, cargo, etc.) and generates comprehensive markdown license reports. Supports automatic license detection from package registries with caching for improved performance.
      -

    • license-guardian

      Baneado98
      -
      license
      Not graded
      quality
      B
      maintenance
      Audits npm dependencies for license compatibility, catching copyleft and source-available traps before shipping.
      -

    • Dependency Checker MCP Server

      djodjonx
      A
      license
      B
      quality
      C
      maintenance
      Enables security scanning for npm dependencies by checking manifest and lockfiles against the OSV.dev and Socket.dev vulnerability databases. It provides tools to detect vulnerabilities in specific packages and retrieve detailed technical reports for identified security issues.
      3
      15 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 3 tools

    Disambiguation4/5

    The tools are mostly distinct: scan_licenses scans a project's dependencies, flag_risky_licenses filters for risky licenses, and classify_license_string handles a single license string. There is some conceptual overlap between scan_licenses and flag_risky_licenses since both operate on the same project data, but their outputs and purposes differ enough to avoid serious confusion.

    Naming Consistency5/5

    All three tools follow a consistent verb-first snake_case pattern: scan_, flag_, classify_. The names clearly describe the action and target, and there is no mixing of conventions or vague verbs.

    Tool Count5/5

    Three tools is well-scoped for a focused license-scanning utility. Each tool serves a distinct step in the workflow—scanning, flagging, and classifying—without unnecessary bloat.

    Completeness4/5

    The toolset covers the core license scanning workflow: scanning a project, flagging risky licenses, and classifying individual strings. A minor gap is the lack of a tool to retrieve full license texts or detailed compliance data, but for the stated advisory purpose the surface is reasonably complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources