API Tools
oasdiff.com
Analyzes OpenAPI specifications to detect changes, produce changelogs, show diffs, and validate.
ENDPOINT 1
https://api.oasdiff.com/mcp
MCP server metadata
- Name
- oasdiff
- Version
- 1.0.0
Known tools 4
oasdiff_breaking_changesDetect breaking API changes between two OpenAPI specifications.
Inferred read-onlyoasdiff_changelogProduce a full changelog of every detected change between two OpenAPI specifications (base vs revision), down to informational changes.
Inferred read-onlyoasdiff_diffShow the structural diff between two OpenAPI specifications (base vs revision): what was added, removed, or modified.
Inferred read-onlyoasdiff_validateValidate a single OpenAPI specification against the OpenAPI and JSON Schema rules.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.oasdiff]
url = "https://api.oasdiff.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"oasdiff": {
"type": "http",
"url": "https://api.oasdiff.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: oasdiff
Remote MCP URL: https://api.oasdiff.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"oasdiff": {
"url": "https://api.oasdiff.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"oasdiff": {
"type": "http",
"url": "https://api.oasdiff.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "oasdiff",
"transport": "streamable-http",
"url": "https://api.oasdiff.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for oasdiff.com was fetched 2026-07-26T08:52:16.210Z and is being refreshed.
oasdiff.com is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.