io.github.oasdiff/oasdiff

Est-ce que io.github.oasdiff/oasdiff est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.oasdiff/oasdiff » 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 4 outils

• oasdiff_breaking_changes≈ 238 tokens

  Detect breaking API changes between two OpenAPI specifications. Pass the base (old) and revision (new) specs as YAML or JSON; returns the breaking and warning-level changes. Use this when the question is whether an API change breaks existing clients. Use oasdiff_changelog instead to list every change including non-breaking and informational ones, oasdiff_diff for the raw added/removed/modified structure, or oasdiff_validate to check a single spec rather than compare two. Both specs must be valid, self-contained OpenAPI (external $ref URLs or files are not resolved).

  Paramètres, retour & exemple (2)

  Paramètres

  • base · string · requis
    the base (old) OpenAPI specification, as YAML or JSON
  • revision · string · requis
    the revision (new) OpenAPI specification, as YAML or JSON

  Exemple d'appel

  {"name": "oasdiff_breaking_changes", "arguments": {"base": "texte", "revision": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• oasdiff_changelog≈ 224 tokens

  Produce a full changelog of every detected change between two OpenAPI specifications (base vs revision), down to informational changes. Pass both specs as YAML or JSON. Use this when you want the complete set of changes at every severity. Use oasdiff_breaking_changes instead when you only care whether the change is breaking (less noise), or oasdiff_diff for the raw structural diff without a backward-compatibility judgment. Both specs must be valid, self-contained OpenAPI (external $ref URLs or files are not resolved).

  Paramètres, retour & exemple (2)

  Paramètres

  • base · string · requis
    the base (old) OpenAPI specification, as YAML or JSON
  • revision · string · requis
    the revision (new) OpenAPI specification, as YAML or JSON

  Exemple d'appel

  {"name": "oasdiff_changelog", "arguments": {"base": "texte", "revision": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• oasdiff_diff≈ 209 tokens

  Show the structural diff between two OpenAPI specifications (base vs revision): what was added, removed, or modified. Pass both specs as YAML or JSON. Use this when you want the raw structural changes rather than a backward-compatibility verdict. Use oasdiff_breaking_changes to judge whether changes break clients, or oasdiff_changelog for a severity-classified changelog. Both specs must be valid, self-contained OpenAPI (external $ref URLs or files are not resolved).

  Paramètres, retour & exemple (2)

  Paramètres

  • base · string · requis
    the base (old) OpenAPI specification, as YAML or JSON
  • revision · string · requis
    the revision (new) OpenAPI specification, as YAML or JSON

  Exemple d'appel

  {"name": "oasdiff_diff", "arguments": {"base": "texte", "revision": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• oasdiff_validate≈ 166 tokens

  Validate a single OpenAPI specification against the OpenAPI and JSON Schema rules. Pass the spec as YAML or JSON; returns the findings (empty when the spec is valid). Use this when you have one spec and want to check it is well-formed. For comparing two specs, use oasdiff_breaking_changes, oasdiff_changelog, or oasdiff_diff instead. The spec must be self-contained (external $ref URLs or files are not resolved).

  Paramètres, retour & exemple (1)

  Paramètres

  • spec · string · requis
    the OpenAPI specification to validate, as YAML or JSON

  Exemple d'appel

  {"name": "oasdiff_validate", "arguments": {"spec": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

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://api.oasdiff.com/mcp