How to Use the 42Crunch MCP in Cursor

Q: How do I connect the 42Crunch MCP Server to Cursor?

Create a .cursor/mcp.json file in your project root folder. Paste the Vinkius endpoint configuration under the servers block. Toggle Agent mode on in your chat panel to start calling tools.

Inject live 42Crunch security scores and audit reports via this MCP Server directly into your OpenAPI specs while coding in Cursor.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect 42Crunch MCP to Cursor

Create your Vinkius account to connect 42Crunch to Cursor and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup 42Crunch with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Fix spec vulnerabilities in Cursor

The `get_audit_report` tool downloads the static security analysis for a specific API definition. When you write a new endpoint in your editor, Agent mode fetches the security grade immediately. Cursor reads the vulnerability list and writes the exact YAML fixes into your file. The `trigger_audit` tool runs a fresh check with one command. You save your changes, tell the agent to rescan the file, and wait for the new results. The AI verifies that your new authentication schemas actually resolved the flagged issues.

Explore 42Crunch collections via MCP Server

The `list_collections` tool returns the IDs for every API group your organization manages. You ask Cursor to find the staging environment collection before deploying new code. The agent grabs the metadata to ensure you target the correct workspace. The `list_apis` tool finds specific definitions within a target collection. Your agent pulls all the unique IDs and security scores for that workspace. You use `get_api` to pull detailed metadata for a single service right into your IDE panel.

Debug conformance failures

The `get_scan_report` tool fetches the raw results from dynamic conformance tests against a live target. You open a failing route in your editor and ask the agent why the security check failed. Cursor pulls the exact HTTP response that broke the test suite. The `list_scans` tool retrieves historical runs for review through the MCP Server. Your AI client pulls the timeline of past conformance checks to see when the regression started. You pinpoint the exact commit that introduced the bad parameter validation.

Setup guide

Set up 42Crunch MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the 42Crunch MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent 42Crunch transactions." If the MCP tools are loaded correctly, Cursor will call the 42Crunch tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "42crunch-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by 42Crunch. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect 42Crunch now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about 42Crunch MCP in Cursor

Create a `.cursor/mcp.json` file in your project root folder. Paste the Vinkius endpoint configuration under the servers block. Toggle Agent mode on in your chat panel to start calling tools.

Your agent reads the static analysis report and suggests inline code edits. You accept the diff to apply the missing security headers or parameter constraints. The AI client writes the actual YAML or JSON fixes.

Tell your agent to push the current file using the import tool. It reads your active editor tab and uploads the OpenAPI definition to your target collection. The platform generates a baseline score within seconds.

You instruct the AI to remove deprecated services using the delete tool. It targets the specific API ID and removes it from the platform. The change reflects immediately across your organization.

Your agent transmits OpenAPI definitions and route schemas to the testing platform. Vinkius secures this transit using a zero-trust architecture requiring a single ephemeral token. Your actual backend source code never leaves the local machine.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript