What version of OpenAPI does this MCP support?

This MCP is specifically designed to validate OpenAPI 3.x documents.

How do I use this with my AI client?

You connect to the MCP through the Vinkius platform, which hosts it for you. Once connected, you can use it in any MCP-compatible client like Claude, Cursor, or Windsurf.

Can this find unused parts of my API spec?

Yes, the detect_orphaned_components capability specifically identifies schemas or parameters that are defined but never used in your paths.

Will this help me find errors in my path parameters?

Yes, the verify_path_parameter_consistency capability catches mismatches between your path templates and your parameter definitions.

Do I need to host the MCP myself?

No, Vinkius hosts and manages the MCP for you. You just connect your client and start working.

What does this server check?

It performs structural checks using validate_meta_schema, finds unused components with detect_orphaned_components, and verifies path parameters. Capabilities available: your_tool_name.

Does it support Swagger 2.0?

No, this capability is specifically designed for OpenAPI 3.x specifications.

How can I find unused schemas?

Run the detect_orphaned_components capability on the specification content.

An astronaut overseeing a futuristic data hub

Download PDF Markdown Version

Connect OpenAPI Spec Validator to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Catch structural errors and broken API definitions instantly.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

One connector, every AI

OpenAPI Spec Validator works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put OpenAPI Spec Validator to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

678ms average. Fast in production.

OpenAPI Spec Validator is checked daily against the live service.

Daily averagePeak 816ms

Oct 3Today

Fastest day: 497ms
Slowest day: 816ms
14-day trend: Improving-9%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 0 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of OpenAPI Spec Validator, so you can see the experience inside your AI.

It does not authenticate your account with OpenAPI Spec Validator. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

OpenAPI Spec Validator Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_V1QKieQHr04kwSsAMtuL8ZVmEHdjZWhSZII2jPnG/mcp

Claude Desktop

Follow the steps below to connect in seconds.

1In Claude Desktop, open Settings → Connectors.
2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
3Click Add and start a new chat — OpenAPI Spec Validator capabilities are ready to use.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "openapi-spec-validator-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_V1QKieQHr04kwSsAMtuL8ZVmEHdjZWhSZII2jPnG/mcp"
    }
  }
}

Claude
ChatGPT
Cursor
VS Code
Windsurf
Claude Code
JetBrains
Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up OpenAPI Spec Validator in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work OpenAPI Spec Validator owners hand off.

This MCP is built for engineers who need to maintain high-quality API documentation without manual linting.

01
Backend Engineers
They hand off new API specs to the AI to ensure they are production-ready.
02
API Architects
They use the agent to audit large-scale specifications for consistency and bloat.
03
QA Automation Engineers
They use the capabilities to verify that documentation matches the intended implementation.

FAQ

Questions OpenAPI Spec Validator owners ask.

01
What version of OpenAPI does this MCP support?
This MCP is specifically designed to validate OpenAPI 3.x documents.
02
How do I use this with my AI client?
You connect to the MCP through the Vinkius platform, which hosts it for you. Once connected, you can use it in any MCP-compatible client like Claude, Cursor, or Windsurf.
03
Can this find unused parts of my API spec?
Yes, the detect_orphaned_components capability specifically identifies schemas or parameters that are defined but never used in your paths.
04
Will this help me find errors in my path parameters?
Yes, the verify_path_parameter_consistency capability catches mismatches between your path templates and your parameter definitions.
05
Do I need to host the MCP myself?
No, Vinkius hosts and manages the MCP for you. You just connect your client and start working.
06
What does this server check?
It performs structural checks using validate_meta_schema, finds unused components with detect_orphaned_components, and verifies path parameters. Capabilities available: your_tool_name.
07
Does it support Swagger 2.0?
No, this capability is specifically designed for OpenAPI 3.x specifications.
08
How can I find unused schemas?
Run the detect_orphaned_components capability on the specification content.

Explore

More in Developer Tools

Connect OpenAPI Spec Validator to Claude, Cursor, ChatGPT & more

Connect OpenAPI Spec Validator to ChatGPT, Claude and Gemini

Your AI does the work. We keep it safe and sound.