Skip to main content
Glama
wgd5678

license-sentinel

by wgd5678
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to license-sentinel

No user-submitted related servers found.

    Related Servers

    • 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-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

    • closeread-verify

      FreeGuy-AI
      A
      license
      A
      quality
      D
      maintenance
      Provides verified dependency-audit verdicts for AI agents, checking installed versions against OSV advisories and splitting direct vs transitive dependencies.
      3
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct stage: audit_project scans an existing project, check_package evaluates individual license strings or packages before install, and generate_notices produces an attribution file. The descriptions explicitly clarify the boundary between audit_project and check_package, so an agent is unlikely to select the wrong tool.

    Naming Consistency5/5

    All three tools follow the same verb_noun snake_case pattern: audit_project, check_package, generate_notices. The naming is predictable and immediately conveys the action and target of each tool.

    Tool Count5/5

    Three tools is a well-scoped count for a focused license-compliance server. Each tool covers a non-overlapping, meaningful workflow step without unnecessary bloat or missing core functionality.

    Completeness4/5

    The toolset covers the main license compliance lifecycle: audit a project, check new dependencies, and generate notices. Minor gaps exist around policy configuration/allowlisting and detailed reporting on all permissive dependencies, but agents can work around these using the provided outputs.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources