Connect-MCP

oasdiff

io.github.oasdiff/oasdiff · v1.0.0

Detect breaking changes, generate changelogs, diff, and validate OpenAPI specs.

MCPremoteno credentials

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 4 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 83/100

What it does: 4 tools · 0 read, 0 write · Files & storage

No tool could be tested safely. Only read-only tools that need no input are called.

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +10
  • Read/write annotations: 0
  • Safe test call: +8
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://api.oasdiff.com/mcp

Tools

4 tools listed at last check
  • oasdiff_breaking_changes 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 chang
  • oasdiff_changelog 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 wheth
  • oasdiff_diff 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
  • oasdiff_validate 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_c

Badge

Connect-MCP badge for io.github.oasdiff/oasdiff

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/io.github.oasdiff/oasdiff.svg)](https://clawy.uk/mcp/s/io.github.oasdiff/oasdiff)