How do I get Intruder API credentials?

Log in to your Intruder portal, navigate to Settings > API, and click 'Create Access Token'.

Can I start scans with this MCP?

This initial version focuses on listing and retrieving security data. Support for triggering new scans may be added in future updates.

What cloud integrations are supported?

Intruder supports AWS, Azure, and Google Cloud Platform for automated asset discovery.

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

Name: Intruder
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Intruder through the Vinkius — pass the Edge URL in the `mcps` parameter and every Intruder tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Intruder Specialist",
    goal="Help users interact with Intruder effectively",
    backstory=(
        "You are an expert at leveraging Intruder tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Intruder "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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.

When paired with CrewAI, Intruder becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Intruder tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

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

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

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 10 tools from Intruder

Why Use CrewAI with the Intruder MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Intruder through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Intruder + CrewAI Use Cases

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

Automated multi-step research: a reconnaissance agent queries Intruder for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Intruder, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Intruder tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Intruder against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Intruder MCP Tools for CrewAI (10)

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

get_account

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

get_issue

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

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

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

list_cloud_integrations

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

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

list_licences

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

list_scans

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

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

list_teams

Useful for understanding organizational access controls. Lists all organization teams

Example Prompts for Intruder in CrewAI

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

"List all active targets in my Intruder account."

"Show me the latest vulnerability issues found."

"Check the status of my recent scans."

Troubleshooting Intruder MCP Server with CrewAI

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

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Intruder + CrewAI FAQ

Common questions about integrating Intruder MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.