Skip to main content
Glama

Related Servers

Alternatives to license-mcp

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables developers and agents to determine what licenses a project's dependencies use and whether shipping is permitted, combining SPDX parsing, installed metadata, lockfile readers, a compatibility table, and a policy engine whose verdicts always carry reasons.
      MIT
    • 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
    • A
      license
      A
      quality
      C
      maintenance
      Provides authoritative open source license answers: SPDX identification, copyleft classification, and compatibility checks of dependencies against your project's license.
      3
      1
      MIT
    • 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.
      -
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI coding agents to learn, from locally read lockfiles, what changes between the dependency version installed and a target version, which of the user's files that upgrade touches, and which vulnerabilities it resolves. It also performs OSV-matched vulnerability scans, ranks upgrade plans, and stores decision memory, running entirely on the user's machine with no account or API keys.
      11
      412 npm
      Apache 2.0

    TDQS

    A4.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a clearly distinct task: inventory listing, policy verdicts, pairwise license compatibility, plain-language explanations, notice generation, and license-file discovery. The descriptions explicitly clarify boundaries, such as compatibility not reading files and check_policy applying a project policy. An agent should have no trouble selecting the right tool.

    Naming Consistency4/5

    All tool names use consistent snake_case and are readable. Most follow a verb_noun pattern (check_policy, explain_license, generate_notices, find_license_files), while license_inventory is noun_noun and compatibility is a bare noun. Minor deviations only.

    Tool Count5/5

    Six tools is well-scoped for a license-compliance server. Each tool covers a distinct part of the workflow and none appears redundant or like padding.

    Completeness5/5

    The surface covers the core license-compliance lifecycle: discover licenses, check project policy, assess pairwise compatibility, explain licenses, generate third-party notices, and locate license files. No obvious critical gaps remain for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues