oasdiff
REMOTE · API.OASDIFF.COM · SCANNED SEP 20
Detect breaking changes, generate changelogs, diff, and validate OpenAPI specs.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 596 tokens (~149/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the oasdiff MCP server?
oasdiff is a hosted endpoint at https://api.oasdiff.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.oasdiff.com
claude mcp add --transport http oasdiff-oasdiff 'https://api.oasdiff.com/mcp'
{
"mcpServers": {
"oasdiff-oasdiff": {
"url": "https://api.oasdiff.com/mcp"
}
}
} {
"servers": {
"oasdiff-oasdiff": {
"type": "http",
"url": "https://api.oasdiff.com/mcp"
}
}
} [mcp_servers.oasdiff-oasdiff] url = "https://api.oasdiff.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"oasdiff-oasdiff": {
"type": "remote",
"url": "https://api.oasdiff.com/mcp",
"enabled": true
}
}
} openclaw mcp add oasdiff-oasdiff --url 'https://api.oasdiff.com/mcp' --transport streamable-http
mcp_servers:
oasdiff-oasdiff:
url: "https://api.oasdiff.com/mcp" {
"McpServers": {
"oasdiff-oasdiff": {
"Transport": "http",
"Url": "https://api.oasdiff.com/mcp"
}
}
} assistant mcp add oasdiff-oasdiff -t streamable-http -u 'https://api.oasdiff.com/mcp'
{
"mcpServers": {
"oasdiff-oasdiff": {
"type": "http",
"url": "https://api.oasdiff.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://api.oasdiff.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.oasdiff.com | CN=WR3,O=Google Trust Services,C=US | 7 Sept 2026 | 6 Dec 2026 | RSA 2048 | SHA256-RSA | c1270fdfbce96cc10a5116a87af9f81c |
| SANs: api.oasdiff.com | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.oasdiff.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| oasdiff.com. | present | 63370 | 8 | Verified |
| api.oasdiff.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.oasdiff.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.oasdiff.com/mcp | HTTPS enforced | 302 | https://api.oasdiff.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
oasdiff_breaking_changes ~169
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).
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | yes | the base (old) OpenAPI specification, as YAML or JSON |
| revision | string | yes | the revision (new) OpenAPI specification, as YAML or JSON |
No output schema declared.
No examples provided.
oasdiff_changelog ~157
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).
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | yes | the base (old) OpenAPI specification, as YAML or JSON |
| revision | string | yes | the revision (new) OpenAPI specification, as YAML or JSON |
No output schema declared.
No examples provided.
oasdiff_diff ~148
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).
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | yes | the base (old) OpenAPI specification, as YAML or JSON |
| revision | string | yes | the revision (new) OpenAPI specification, as YAML or JSON |
No output schema declared.
No examples provided.
oasdiff_validate ~122
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).
| Name | Type | Req | Description |
|---|---|---|---|
| spec | string | yes | the OpenAPI specification to validate, as YAML or JSON |
No output schema declared.
No examples provided.
What is the oasdiff MCP server?
oasdiff is an MCP server listed in the public MCP registry as io.github.oasdiff/oasdiff. Detect breaking changes, generate changelogs, diff, and validate OpenAPI specs. This page covers its hosted endpoint (https://api.oasdiff.com/mcp).
Is the oasdiff MCP server safe to use?
oasdiff scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the oasdiff MCP server expose?
oasdiff exposes 4 tools: oasdiff_breaking_changes, oasdiff_changelog, oasdiff_diff, oasdiff_validate. Their descriptions and schemas cost roughly 596 tokens of context every time the server is loaded.
Does the oasdiff MCP server require authentication?
No. We connected to oasdiff without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the oasdiff MCP server still maintained?
oasdiff is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.