validate_openapi_spec — api contract validator MCP Tool
validate_openapi_spec
(validate openapi spec) is one of 5 tools on the
api contract validator
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call validate_openapi_spec from your client
- Claude Code api contract validator validate_openapi_spec run in your project directory
- Claude Desktop api contract validator validate_openapi_spec ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor api contract validator validate_openapi_spec ~/.cursor/mcp.json
- VS Code api contract validator validate_openapi_spec .vscode/mcp.json
- Zed api contract validator validate_openapi_spec ~/.config/zed/settings.json
- Windsurf api contract validator validate_openapi_spec ~/.codeium/windsurf/mcp_config.json
- Cline api contract validator validate_openapi_spec ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI api contract validator validate_openapi_spec ~/.gemini/settings.json
- Grok api contract validator validate_openapi_spec .mcp.json (in your project root)
- ChatGPT api contract validator validate_openapi_spec Settings → Connectors → Advanced → Developer mode
- Claude.ai api contract validator validate_openapi_spec Settings → Connectors → Add custom connector
- LangChain api contract validator validate_openapi_spec pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http api-contract-validator https://api.lazy-mac.com/api-contract-validator/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.