Skip to main content
Glama
bivex

Scancode License Analysis Tool for MCP

by bivex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to Scancode License Analysis Tool for MCP

No user-submitted related servers found.

    Related Servers

    • license-check

      arhancanli
      A
      license
      A
      quality
      B
      maintenance
      Provides authoritative open source license answers: SPDX identification, copyleft classification, and compatibility checks of dependencies against your project's license.
      3
      1
      MIT

    • license-advisor-mcp

      license-advisor
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to scan a project's real dependency tree against a declared shipping intent (e.g. hosted closed-source SaaS) and return contextual license alerts with package paths, rule IDs, and assumptions. Also explains the highest-priority findings, shows resolved license evidence, and updates the shipping intent before rescanning.
      1
      MIT

    • license-sentinel

      wgd5678
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to audit Python and npm dependency licenses against your distribution context before shipping, returning CLEAN, REVIEW, or BLOCK verdicts with plain-language reasons and supporting notice generation.
      3
      1
      MIT

    • Licentia MCP

      LucasHefi
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables searching, comparing, and validating SPDX licenses and exceptions, plus SPDX expression validation and SBOM analysis through a Streamable HTTP endpoint.
      1
      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

    A3.7/5.0

    Scored across 5 tools

    Disambiguation4/5

    Most tools have distinct purposes: analyze_license_file examines a specific file's licenses, compare_license_compatibility checks two licenses, get_license_clause_summary details a single license, and list_high_risk_files and summarize_license_risks both identify high-risk files but with slightly different focuses (listing vs. summarizing). The overlap between list_high_risk_files and summarize_license_risks could cause minor confusion, but descriptions clarify their nuances.

    Naming Consistency5/5

    All tool names follow a consistent pattern with the prefix 'mcp_ScancodeMCP_' and use snake_case for the action-object structure (e.g., analyze_license_file, compare_license_compatibility). This uniformity makes the set predictable and easy to navigate, with no deviations in naming conventions.

    Tool Count5/5

    With 5 tools, the server is well-scoped for license analysis, covering key operations like analysis, comparison, summarization, and risk identification. Each tool serves a clear purpose without redundancy, making the count appropriate for the domain's complexity and typical use cases.

    Completeness4/5

    The tool set covers core aspects of license analysis, including detailed examination, compatibility checks, and risk assessment. A minor gap exists in lacking tools for broader actions like batch processing multiple files or managing license databases, but agents can work around this with the provided tools for most workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources