io.github.rccaoki-wq/license-guard

Est-ce que io.github.rccaoki-wq/license-guard est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.rccaoki-wq/license-guard » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 3 outils

• check_dependency_license≈ 629 tokens

  Determine whether adding or keeping a single open source dependency creates a legal obligation, given how this project ships. Call this BEFORE adding a new dependency to a project, and when auditing an existing one. A permissive result means no source-disclosure duty; a blocked result means the license obligates you and the dependency should be replaced or the shipping model reconsidered.

  Paramètres, retour & exemple (5)

  Paramètres

  • name · string · requis
    Package name as written in the manifest, e.g. "express", "requests", "github.com/gin-gonic/gin", or "serde".
  • scope · string · optionnel · runtime | dev | build | test | optional
    Where the dependency sits. Use "dev", "build", or "test" for anything that does not end up in the shipped artifact — those carry no distribution obligation. Defaults to "runtime".
  • version · string · optionnel
    Exact version if known. Omit to use the latest published version, which may differ from what is installed.
  • ecosystem · string · requis · npm | pypi | go | cargo | rubygems | nuget
    Package registry the dependency comes from.
  • distribution_model · string · requis · saas | distributed-binary | on-prem-delivery | internal-only | library-published
    How the software incorporating this dependency reaches its users. This determines the answer: "saas" = users reach it over a network; "distributed-binary" = shipped as an app or binary; "on-prem-delivery" = installed in a customer environment; "internal-only" = never leaves your organization; "library-published" = released for others to depend on.

  Exemple d'appel

  {"name": "check_dependency_license", "arguments": {"name": "texte", "ecosystem": "npm", "distribution_model": "saas"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"license": "texte", "verdict": "allowed", "rationale": "texte", "reference": "texte", "assumption": {}, "obligations": []}}

• check_manifest_licenses≈ 978 tokens

  Scan an entire dependency manifest and report every dependency whose license creates an obligation for this shipping model. Use when reviewing a project as a whole, preparing for due diligence, or after a large dependency change. Pass a package-lock.json when one exists: problematic licenses usually arrive as transitive dependencies rather than ones you added directly, and only a lockfile reveals those.

  Paramètres, retour & exemple (2)

  Paramètres

  • content · string · requis
    Full text of a lockfile, SBOM, or manifest. Accepted: package-lock.json, pnpm-lock.yaml, yarn.lock, go.sum, Cargo.lock, poetry.lock, uv.lock, Gemfile.lock, packages.lock.json, CycloneDX (JSON), SPDX (JSON), package.json, requirements.txt, go.mod, Cargo.toml, .csproj, Directory.Packages.props, packages.config. The format is detected automatically. Prefer a lockfile: it covers transitive dependencies and carries exact versions. package-lock.json is best of all, since it embeds licenses and needs no registry lookups. An SBOM covers several ecosystems in one document, but its licenses are read from the document rather than looked up, so they are only as current as the document.
  • distribution_model · string · requis · saas | distributed-binary | on-prem-delivery | internal-only | library-published
    How the software incorporating this dependency reaches its users. This determines the answer: "saas" = users reach it over a network; "distributed-binary" = shipped as an app or binary; "on-prem-delivery" = installed in a customer environment; "internal-only" = never leaves your organization; "library-published" = released for others to depend on.

  Exemple d'appel

  {"name": "check_manifest_licenses", "arguments": {"content": "texte", "distribution_model": "saas"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"summary": {}, "findings": [], "ecosystem": "texte", "limitations": [], "distributionModel": "texte"}}

• explain_license≈ 507 tokens

  Given an SPDX license identifier or expression, explain what it requires across every shipping model at once. Use when the question is about the license itself rather than a specific package — for example when comparing AGPL-3.0 against GPL-3.0 for a hosted service, or deciding what a project may safely depend on.

  Paramètres, retour & exemple (2)

  Paramètres

  • license · string · requis
    SPDX identifier or expression, e.g. "AGPL-3.0-only", "Apache-2.0", or "(MIT OR GPL-2.0-only)".
  • linkage · string · optionnel · dynamic | static | separate-process
    How the dependency is linked. Matters for LGPL-family licenses. Compiled languages such as Go and Rust normally link statically. Defaults to "dynamic".

  Exemple d'appel

  {"name": "explain_license", "arguments": {"license": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"license": "texte", "linkage": "texte", "devScope": {}, "byDistributionModel": []}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://license-guard.rcc-aoki.workers.dev/mcp