An astronaut overseeing a futuristic data hub

Connect 42Crunch 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. Audit your APIs and secure your code via natural conversation.

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 · 10 capabilities

We ship only the actions that matter.

Capability set01 / 03

01-04

4 capabilities in this set.

Part of 10 available through 42Crunch.

  1. 01

    Get audit report

    Downloads the final static security audit report for a specific API definition.

  2. 02

    List scans

    Lists all dynamic conformance scans that have been run against a live API.

  3. 03

    Trigger audit

    Runs a fresh static security audit on an API definition whenever you update the specification.

  4. 04

    Get collection

    Retrieves metadata and the overall security score for a specific API collection.

Capability set02 / 03

05-07

3 capabilities in this set.

Part of 10 available through 42Crunch.

  1. 05

    Delete API

    Removes an API definition from the platform entirely.

  2. 06

    Get API

    Gets detailed metadata and the current security score for a single API.

  3. 07

    List apis

    Lists all API definitions within a collection, showing each one's unique ID and security score.

Capability set03 / 03

08-10

3 capabilities in this set.

Part of 10 available through 42Crunch.

  1. 08

    List collections

    Lists all API collections in the platform, helping you find the ID you need for imports or API listings.

  2. 09

    Get scan report

    Retrieves detailed results from a dynamic conformance scan that was previously run.

  3. 10

    Import API

    Imports a new OpenAPI definition into an existing collection.

Real work

What teams actually run

01

Onboarding a New Service

A backend developer imports a new API spec, triggers an audit, and immediately gets a list of critical vulnerabilities to fix before deployment.

02

Quarterly Security Review

A platform team lists all API collections, checks their aggregated security scores, and identifies which services need immediate attention.

03

Debugging a Failure

A devsecops engineer runs a dynamic conformance scan and uses the resulting report to pinpoint exactly where the API deviates from its documented behavior.

04

Decommissioning an API

Instead of manually deleting records, you use the MCP to delete an API definition from the platform once it's no longer needed.

Automate a task

Put 42Crunch to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

42Crunch 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 42Crunch 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

911ms average. Fast in production.

42Crunch is checked daily against the live service.

Daily averagePeak 1239ms
Oct 3Today
Fastest day
772ms
Slowest day
1239ms
14-day trend
Slowing+5%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 10 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 42Crunch, so you can see the experience inside your AI.

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

42Crunch Connector

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

Connector linkhttps://edge.vinkius.com/vk_preview_Gi3PrK2xNbiurYu9rVegSxEQmPykAdCxogXvksIV/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 — 42Crunch capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "42crunch-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_Gi3PrK2xNbiurYu9rVegSxEQmPykAdCxogXvksIV/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 42Crunch in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work 42Crunch owners hand off.

If you're building or maintaining a microservices platform, this MCP gives you a single place to govern security. DevSecOps Engineers use it to integrate security audits and get immediate remediation steps for vulnerabilities. Platform Teams use it to track security hygiene across dozens of collections and spot uncompliant endpoints. Backend Developers use it to quickly import new specs, run a scan, and track how the security grade changes.

  • 01

    DevSecOps Engineers

    Integrate security audits seamlessly and ask for immediate remediation steps for OWASP vulnerabilities.

  • 02

    Platform Teams

    Govern your microservices ecosystem, track security hygiene across collections, and spot uncompliant endpoints.

  • 03

    Backend Developers

    Quickly import a new spec iteration, trigger a scan, and compare the security grade evolution without context switching.

FAQ

Questions 42Crunch owners ask.

  • 01

    What formats of API specifications does this MCP handle?

    It handles OpenAPI and Swagger definitions. You can import these definitions directly into a collection so the MCP can audit them.

  • 02

    Does this MCP only check my code, or does it check the design too?

    It does both. You can run static security audits that score design risks based on the specification, and dynamic conformance scans that check live behavior.

  • 03

    Can I see the security score for all my APIs at once?

    Yes. You can list all API collections and see their aggregated security scores. You can also list all APIs within a collection and see their individual scores.

  • 04

    If I change my API, do I have to manually run a scan?

    No. You can trigger a fresh static security audit using the MCP after updating a specification. This ensures you get the most current risk assessment.

  • 05

    What is the difference between a static and dynamic audit?

    A static audit checks the design and structure of your OpenAPI file for theoretical risks. A dynamic scan checks the actual, live behavior of the API endpoints.

  • 06

    Can my AI agent explain the vulnerabilities found in a 42Crunch audit?

    Yes. After retrieving an audit report using your agent, you can ask the agent to act as a DevSecOps engineer. It can break down exactly why you received a low score, explain specific OWASP findings, and write the YAML or JSON patch needed to fix your OpenAPI spec instantly.

  • 07

    How do I test a new API update before merging?

    Simply paste your updated OpenAPI definitions into your AI agent's chat context. Ask the agent to import the new API definition into a staging collection. The platform will automatically run a static security audit upon import, and your agent can report back the new security score before you hit merge.

  • 08

    What is the difference between static audits and dynamic conformance scans?

    Audits strictly verify the design of your JSON/YAML contract against security best practices without making network calls. Scans, however, send live HTTP traffic against your implemented endpoint to make sure your back-end truly conforms to what you wrote. Your agent can retrieve both reports for side-by-side comparison.

Connect 42Crunch to Claude, Cursor, ChatGPT & more