2,500+ MCP servers ready to use
Vinkius

Intruder MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

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.

GitHub Copilot Agent mode brings Intruder data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

The Intruder MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot 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 VS Code Copilot via MCP

Follow these steps to integrate the Intruder MCP Server with VS Code Copilot.

01

Create MCP config

Create a .vscode/mcp.json file in your project root

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

04

Start using Intruder

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

Why Use VS Code Copilot with the Intruder MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Intruder through the Model Context Protocol.

01

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Intruder + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Intruder MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Intruder MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Intruder to VS Code Copilot 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 VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot 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 VS Code Copilot

Common issues when connecting Intruder to VS Code Copilot through the Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Intruder + VS Code Copilot FAQ

Common questions about integrating Intruder MCP Server with VS Code Copilot.

01

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
02

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
03

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
04

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

Connect Intruder to VS Code Copilot

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