An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect API Contract Breaker Detector to ChatGPT and Claude

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. Stop runtime failures before they hit production.

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.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

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.

A futuristic MCP client docking bay
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.

Curated set · 3 capabilities

We ship only the actions that matter.

Capability set01 / 01

01-03

3 capabilities in this set.

Part of 3 available through API Contract Breaker Detector.

  1. 01

    Check for breaking changes

    This capability compares your current codebase against the stored contract registry. It flags any modifications that violate existing API agreements, letting you know exactly what's broken.

  2. 02

    Query contract details

    Use this capability to pull the full definition of a single contract from the registry. This lets you deep-inspect specific endpoints and verify their required parameters.

  3. 03

    Register API contracts

    This capability establishes your API baseline. It scans your entire codebase and saves the current state of all API definitions into the registry, creating your source of truth.

Real work

What teams actually run

01

Refactoring a Microservice

When you update a core service, run the MCP to ensure your changes haven't broken the contract expected by dependent services.

02

Onboarding New Developers

Use the MCP to quickly generate a validated, up-to-date map of all existing API endpoints for new team members.

03

Pre-Deployment Validation

Before merging a pull request, run the check to guarantee that the new code adheres to the existing API agreements.

04

Debugging Integration Failures

If a service fails mysteriously, query the contract details to verify if the expected parameters or paths were altered.

One connector, every AI

API Contract Breaker Detector 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.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

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

You don't need a client to put API Contract Breaker Detector 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

916ms average. Fast in production.

API Contract Breaker Detector is checked daily against the live service.

Daily averagePeak 994ms
Oct 3Today
Fastest day
740ms
Slowest day
994ms
14-day trend
Stable0%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 3 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 API Contract Breaker Detector, so you can see the experience inside your AI.

It does not authenticate your account with API Contract Breaker Detector. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

API Contract Breaker Detector Connector

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

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

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — API Contract Breaker Detector capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "api-contract-breaker-detector-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_YeJgQHCnSbmKU0xSykEdZnqaw5Tkqwkw63mRpiGy/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 API Contract Breaker Detector in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work API Contract Breaker Detector owners hand off.

This MCP is built for backend engineers and platform architects who manage microservices. If your team relies on multiple interconnected APIs, this capability gives you the safety net you need. It lets you validate changes before they ever reach a staging environment.

  • 01

    Backend Engineer

    Use it to validate local changes against the established API contract registry.

  • 02

    Platform Architect

    Use it to maintain a consistent, verifiable source of truth across multiple services.

  • 03

    DevOps Engineer

    Use it to automate pre-deployment checks, ensuring API stability across the entire stack.

FAQ

Questions API Contract Breaker Detector owners ask.

  • 01

    What kind of APIs does this MCP support?

    It supports multiple modern frameworks, including FastAPI, Express, GraphQL, and TypeScript definitions. This broad coverage means it can analyze most common backend service types.

  • 02

    Does this MCP just list endpoints, or does it check for actual breaks?

    It does more than list them. It uses deterministic AST parsing to build a contract registry. When you check for breaking changes, it actively compares your code against the known baseline to flag violations.

  • 03

    How do I start using this MCP?

    You connect your preferred AI client to the Vinkius catalog. You then start by running the register_api_contracts capability to establish the initial source of truth for your project.

  • 04

    Can I check a single endpoint's requirements?

    Yes. You use the query_contract_details capability. This allows you to retrieve the full definition, including required parameters and expected return types, for deep inspection.

  • 05

    Is this useful for microservices?

    Absolutely. In a microservices environment, API contracts are everything. This MCP prevents runtime failures by ensuring that changes in one service don't break another.

  • 06

    How do I start using this capability?

    First, run register_api_contracts to scan your codebase and create a baseline registry of your current API definitions.

  • 07

    What is considered a breaking change?

    A breaking change includes removing an endpoint, changing a URL path, renaming a parameter, changing a parameter type, or removing a field from a response body.

  • 08

    Does adding a new endpoint trigger a breaking change alert?

    No, adding new endpoints or adding optional parameters are not considered breaking changes.

Explore

More in Developer Tools

Suggestions

Connect API Contract Breaker Detector to Claude, Cursor, ChatGPT & more