2,500+ MCP servers ready to use
Vinkius

Intruder MCP Server for Cline 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools IDE

Cline is an autonomous AI coding agent inside VS Code that plans, executes, and iterates on tasks. Wire Intruder through Vinkius and Cline gains direct access to every tool. from data retrieval to workflow automation. without leaving the terminal.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Intruder and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "intruder": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Intruder
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Intruder MCP Server

Empower your AI agents to manage your cybersecurity posture with Intruder.io. This MCP server allows you to list security targets, track vulnerability scans, retrieve identified issues, and monitor cloud integrations directly through the Intruder API. Ideal for automating DevSecOps workflows and security auditing.

Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including Intruder tool calls without waiting for prompts between steps. Connect 10 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.

The Intruder MCP Server exposes 10 tools through the Vinkius. Connect it to Cline in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Intruder to Cline via MCP

Follow these steps to integrate the Intruder MCP Server with Cline.

01

Open Cline MCP Settings

Click the MCP Servers icon in the Cline sidebar panel

02

Add remote server

Click "Add MCP Server" and paste the configuration above

03

Enable the server

Toggle the server switch to ON

04

Start using Intruder

Ask Cline: "Using Intruder, help me...". 10 tools available

Why Use Cline with the Intruder MCP Server

Cline provides unique advantages when paired with Intruder through the Model Context Protocol.

01

Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts

02

Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window

03

Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation

04

Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing

Intruder + Cline Use Cases

Practical scenarios where Cline combined with the Intruder MCP Server delivers measurable value.

01

Autonomous feature building: tell Cline to fetch data from Intruder and scaffold a complete module with types, handlers, and tests

02

Codebase refactoring: use Intruder tools to validate live data while Cline restructures your code to match updated schemas

03

Automated testing: Cline fetches real responses from Intruder and generates snapshot tests or mocks based on actual payloads

04

Incident response: query Intruder for real-time status and let Cline generate hotfix patches based on the findings

Intruder MCP Tools for Cline (10)

These 10 tools become available when you connect Intruder to Cline via MCP:

01

get_account

Use to verify identity and account settings. Gets your Intruder account details

02

get_issue

Returns detailed descriptions, remediation advice, and affected targets. Essential for investigating and fixing security flaws. Retrieves details for a specific issue

03

get_scan

Returns the list of targets included, scan duration, and a summary of findings. Use this to audit the results of a specific security assessment. Retrieves details for a specific scan

04

get_target

Returns metadata and associated tags. Use this to deep-dive into the security status of a specific asset. Retrieves details for a specific target

05

list_cloud_integrations

Essential for auditing how Intruder discovers new targets in the cloud infrastructure. Lists all configured cloud integrations (AWS, Azure, Google Cloud)

06

list_issues

Returns issue titles, severity levels (Low, Medium, High, Critical), and status. Use this as the primary tool for security posture auditing. Lists all identified vulnerability issues

07

list_licences

Useful for verifying subscription status and capacity. Lists all account licences

08

list_scans

Includes scan types, timestamps, and IDs. Essential for tracking scan frequency and monitoring ongoing security checks. Lists all vulnerability scans

09

list_targets

Returns target names, IDs, and types. Use this to identify which assets are being scanned for vulnerabilities. Lists all infrastructure and application targets

10

list_teams

Useful for understanding organizational access controls. Lists all organization teams

Example Prompts for Intruder in Cline

Ready-to-use prompts you can give your Cline agent to start working with Intruder immediately.

01

"List all active targets in my Intruder account."

02

"Show me the latest vulnerability issues found."

03

"Check the status of my recent scans."

Troubleshooting Intruder MCP Server with Cline

Common issues when connecting Intruder to Cline through the Vinkius, and how to resolve them.

01

Server shows error in sidebar

Click the server name to see logs. Verify the URL and token are correct.

Intruder + Cline FAQ

Common questions about integrating Intruder MCP Server with Cline.

01

How does Cline connect to MCP servers?

Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.
02

Can Cline run MCP tools without approval?

By default, Cline asks for confirmation before executing tool calls. You can configure auto-approval rules for trusted servers in the settings.
03

Does Cline support multiple MCP servers at once?

Yes. Configure as many servers as needed. Cline can use tools from different servers within the same autonomous task execution.

Connect Intruder to Cline

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.