Connect oasdiff and your agent gets 4 tools, among them oasdiff_breaking_changes, oasdiff_changelog, oasdiff_diff. It answers at https://api.oasdiff.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 22 October 2026, succeeded.
Detect breaking changes, generate changelogs, diff, and validate OpenAPI specs.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 existin Inputs: base, revision |
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. U Inputs: base, revision |
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 ve Inputs: base, revision |
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 Inputs: spec |
Every block below points at https://api.oasdiff.com/mcp. Pick your client and copy.
claude mcp add --transport http oasdiff https://api.oasdiff.com/mcp
{
"mcpServers": {
"oasdiff": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.oasdiff.com/mcp"]
}
}
}{
"mcpServers": {
"oasdiff": {
"url": "https://api.oasdiff.com/mcp"
}
}
}{
"servers": {
"oasdiff": {
"type": "http",
"url": "https://api.oasdiff.com/mcp"
}
}
}{
"context_servers": {
"oasdiff": {
"url": "https://api.oasdiff.com/mcp"
}
}
}{
"mcpServers": {
"oasdiff": {
"serverUrl": "https://api.oasdiff.com/mcp"
}
}
}{
"mcpServers": {
"oasdiff": {
"url": "https://api.oasdiff.com/mcp"
}
}
}name: oasdiff
version: 0.0.1
schema: v1
mcpServers:
- name: oasdiff
type: streamable-http
url: https://api.oasdiff.com/mcp{
"mcpServers": {
"oasdiff": {
"httpUrl": "https://api.oasdiff.com/mcp"
}
}
}{
"mcpServers": {
"oasdiff": {
"type": "http",
"url": "https://api.oasdiff.com/mcp"
}
}
}{
"mcpServers": {
"oasdiff": {
"url": "https://api.oasdiff.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fapi.oasdiff.com%2Fmcp&type=streamable_http&id=oasdiff&name=oasdiff
It answered our last check on 22 October 2026 in 220 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
4, as returned by the server's own tools/list on 17 September 2026: oasdiff_breaking_changes, oasdiff_changelog, oasdiff_diff, oasdiff_validate.
It answered our last check on 22 October 2026 in 220 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.oasdiff.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.oasdiff. Endpoint host: api.oasdiff.com. ARD identifier: urn:air:io.github.oasdiff:mcp:oasdiff.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.