OpenAPI Spec Validator Connector for AI agents.
5 live capabilities
Audit and fix broken API specifications automatically.
Waiting for input…
Why people use OpenAPI Spec Validator
Stop breaking API contracts with OpenAPI Spec Validator
With this Connector, your agent does the heavy lifting. It scans the entire document in seconds, pointing out exactly which components are dead weight and where your path parameters don't match their definitions. You get a clean, valid spec without the manual headache.
What Vinkius changes
You stop shipping broken API documentation.
Use it from Claude, ChatGPT, Cursor or another AI client you already have.
One account · 6,100+ Connectors
- Real-world use case 01
Cleaning up legacy specs
You have a massive, messy Swagger file.
- Real-world use case 02
Verifying new endpoints
You just added /users/{id} but forgot the parameter definition.
- Real-world use case 03
Preparing for a breaking change
You're updating schemas and need to ensure no required fields were missed.
Complete set · 5capabilities
The complete OpenAPI Spec Validator capability set.
These are the exact actions your AI can choose when you ask it to work with OpenAPI Spec Validator.
01—03
3 capabilities in this set.
Part of 5 available through OpenAPI Spec Validator.
- 01 Capability
Catch structural errors in OAS files
Identify high-level syntax mistakes that violate OpenAPI 3.x rules.
- 02 Capability
Find unused schemas and parameters
Locate dead code and orphaned components to keep your documentation clean.
- 03 Capability
Match path templates with parameter definitions
Ensure every variable in your URL has a corresponding definition.
04—05
2 capabilities in this set.
Part of 5 available through OpenAPI Spec Validator.
- 04 Capability
Identify missing response definitions
Detect endpoints that lack necessary error or success response documentation.
- 05 Capability
Detect undocumented required fields
Find discrepancies where properties are marked as required but not properly defined.
Set up in minutes
One URL. Then ask OpenAPI Spec Validator to work.
Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use OpenAPI Spec Validator from the conversation.
Choose your client
Live previewAdvanced clients IDE · CLI
Claude · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_V1QKieQHr04kwSsAMtuL8ZVmEHdjZWhSZII2jPnG/mcp - Step 01
Open Connectors
In Claude Web or Claude Desktop, open Settings and choose Connectors.
- Step 02
Add the URL
Choose Add custom connector, name it OpenAPI Spec Validator, and paste the URL above.
- Step 03
Turn it on in chat
Select +, open Connectors, and enable OpenAPI Spec Validator for the conversation.
ChatGPT · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_V1QKieQHr04kwSsAMtuL8ZVmEHdjZWhSZII2jPnG/mcp - Step 01
Open MCP settings
On desktop, open Settings and MCP servers. On web, open your workspace app or connector settings.
- Step 02
Add the URL
Choose Add server with Streamable HTTP, or create a custom MCP app, then paste the OpenAPI Spec Validator URL.
- Step 03
Save and start
Save the connection and enable OpenAPI Spec Validator in your conversation. Desktop may ask you to restart once.
Cursor · IDE configuration
Advanced setup
{
"mcpServers": {
"openapi-spec-validator": {
"url": "https://edge.vinkius.com/vk_preview_V1QKieQHr04kwSsAMtuL8ZVmEHdjZWhSZII2jPnG/mcp"
}
}
}- Step 01
Open MCP Settings
Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"
- Step 02
Add the server config
Paste the JSON configuration above into the mcp.json file that opens
- Step 03
Save the file
Cursor will automatically detect the new Connector
- Step 04
Start using OpenAPI Spec Validator
Open Agent mode in chat and ask: "Using OpenAPI Spec Validator, help me...". 5 tools available
VS Code Copilot · IDE configuration
Advanced setup
{
"mcpServers": {
"openapi-spec-validator": {
"url": "https://edge.vinkius.com/vk_preview_V1QKieQHr04kwSsAMtuL8ZVmEHdjZWhSZII2jPnG/mcp"
}
}
}- Step 01
Create MCP config
Create a .vscode/mcp.json file in your project root
- Step 02
Add the server config
Paste the JSON configuration above
- Step 03
Enable Agent mode
Open GitHub Copilot Chat and switch to Agent mode using the dropdown
- Step 04
Start using OpenAPI Spec Validator
Ask Copilot: "Using OpenAPI Spec Validator, help me...". 5 tools available
Windsurf · IDE configuration
Advanced setup
{
"mcpServers": {
"openapi-spec-validator": {
"url": "https://edge.vinkius.com/vk_preview_V1QKieQHr04kwSsAMtuL8ZVmEHdjZWhSZII2jPnG/mcp"
}
}
}- Step 01
Open MCP Settings
Go to Settings → MCP Configuration or press Cmd+Shift+P and search "MCP"
- Step 02
Add the server
Paste the JSON configuration above into mcp_config.json
- Step 03
Save and reload
Windsurf will detect the new server automatically
- Step 04
Start using OpenAPI Spec Validator
Open Cascade and ask: "Using OpenAPI Spec Validator, help me...". 5 tools available
Cline · IDE configuration
Advanced setup
{
"mcpServers": {
"openapi-spec-validator": {
"url": "https://edge.vinkius.com/vk_preview_V1QKieQHr04kwSsAMtuL8ZVmEHdjZWhSZII2jPnG/mcp"
}
}
}- Step 01
Open Cline MCP Settings
Click the Connectors icon in the Cline sidebar panel
- Step 02
Add remote server
Click "Add Connector" and paste the configuration above
- Step 03
Enable the server
Toggle the server switch to ON
- Step 04
Start using OpenAPI Spec Validator
Ask Cline: "Using OpenAPI Spec Validator, help me...". 5 tools available
Claude Code · Terminal command
Advanced setup
claude mcp add openapi-spec-validator --transport http "https://edge.vinkius.com/vk_preview_V1QKieQHr04kwSsAMtuL8ZVmEHdjZWhSZII2jPnG/mcp"- Step 01
Install Claude Code
Run npm install -g @anthropic-ai/claude-code if not already installed
- Step 02
Add the Connector
Run the command above in your terminal
- Step 03
Verify the connection
Run claude mcp to list connected servers, or type /mcp inside a session
- Step 04
Start using OpenAPI Spec Validator
Ask Claude: "Using OpenAPI Spec Validator, show me...". 5 tools are ready
Where the request belongs
Work OpenAPI Spec Validator can move forward.
Backend engineers and API architects who can't afford to break downstream consumers with invalid specs.
API Engineer
Auditing new endpoints for compliance before merging pull requests.
QA Automation Engineer
Ensuring the spec matches the actual implementation behavior during testing.
Technical Writer
Cleaning up documentation and removing dead code from YAML files.
Build the capability set
Add more capabilities.
Each Connector adds new actions and data without changing how you work.
Browse ConnectorsOpenAPI Validator Engine
Validate any OpenAPI or Swagger spec (2.0, 3.0, 3.1, 3.2) local before generating code from it. Returns version, validity, and every schema error with exact paths. Your spec quality gate.
API Contract Diff Checker
Detect breaking and additive changes in OpenAPI and GraphQL schemas.
OpenAPI Context Window Packer
Prune massive OpenAPI specs to fit within LLM context windows.
SwaggerHub
Connect your AI to SwaggerHub. Read OpenAPI specifications, explore domains, and manage your API design lifecycle natively from the terminal.
JSON Schema Validator
Validate JSON documents and lint schemas for structural integrity.
API Design Prover
An AI agent designed an API with GET /users/create. That single endpoint broke HTTP caching for 200 consumer services. No versioning. No error contract. Raw arrays on one route, wrapped objects on another. This capability forces semantic HTTP verbs, explicit versioning strategy, unified response envelopes, bounded pagination, and RFC 7807 error structures. before any code is written.
Bring your own AI
Change the model, client or framework. Keep OpenAPI Spec Validator connected.
-
Claude -
ChatGPT -
Gemini -
Cursor -
VS Code -
Windsurf -
ZCode -
Cline -
Zed -
Continue -
Kiro -
Roo Code -
Zencoder -
Goose -
Void -
Augment Code -
Amp -
Qodo -
Tabnine -
Pieces -
Sourcegraph Cody -
JetBrains -
Warp -
Amazon Q -
Antigravity -
BoltAI -
Raycast -
Jan -
LM Studio -
AnythingLLM -
Open WebUI -
Msty -
Cherry Studio -
LibreChat -
TypingMind -
Chorus -
5ire -
n8n -
LangChain -
LlamaIndex -
CrewAI -
Vercel AI SDK
Before you connect
Questions about OpenAPI Spec Validator.
The practical details behind the request, access and result.
How can I find unused schemas in my OpenAPI file with OpenAPI Spec Validator?
You can ask your agent to scan the document for components that aren't referenced in any paths. It will list every orphaned schema it finds so you can delete them safely.
Can OpenAPI Spec Validator catch errors in path parameters?
Yes, it specifically checks if the variables you put in your URL templates actually have matching parameter definitions to prevent broken endpoints.
Will this Connector help with my API documentation accuracy?
Absolutely. It audits your specification for missing response definitions and ensures that all required fields are properly documented within your schemas.
Does OpenAPI Spec Validator support Swagger 2.0?
This capability is specifically designed for OpenAPI 3.x documents to ensure you are getting the most accurate structural validation available.
How do I use OpenAPI Spec Validator with Claude or Cursor?
Since it's hosted on Vinkius, you just connect your client once and you can immediately start asking your agent to audit your API files for errors.
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.
One connection away
Give your agent a direct line to OpenAPI Spec Validator.
Connect OpenAPI Spec Validator once. Keep it beside 6,100+ managed Connectors when the next task needs more.
Explore every Connector No credit card required · Free tier available