How do I find my Halo Security API Key?

Log in to your Halo Security account, navigate to **Account Settings** and then to the **API** section. You will be able to generate and copy your unique API key from there.

Can I trigger a new scan through this integration?

Yes! Use the `trigger_scan` tool by providing the unique target ID of the asset you want to assess. Halo Security will initiate the scan immediately.

How are security issues categorized?

Issues are categorized by their severity (e.g., Critical, High, Medium, Low) and type (e.g., Vulnerability, Information, SSL Issue). You can use `list_issues` to see all findings.

Is it possible to add new domains to monitor?

Yes, the `add_target` tool allows you to add new domains or IP addresses to your security perimeter directly from the AI agent.

Halo Security MCP Server for CrewAI 11 tools — connect in under 2 minutes

Name: Halo Security
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 11 Tools Framework

Connect your CrewAI agents to Halo Security through Vinkius, pass the Edge URL in the `mcps` parameter and every Halo Security 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="Halo Security Specialist",
    goal="Help users interact with Halo Security effectively",
    backstory=(
        "You are an expert at leveraging Halo Security 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 Halo Security "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 11 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 Halo Security MCP Server

Connect your Halo Security platform to any AI agent and take full control of your attack surface and vulnerability management through natural conversation.

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

What you can do

Asset Monitoring — List and add targets (domains, IPs, apps) to your security perimeter.
Vulnerability Oversight — Access and inspect discovered security issues, severities, and remediation status.
Scan Management — Review scan history and trigger new on-demand security assessments.
Infrastructure Discovery — List open ports, SSL/TLS certificates, and detected technologies across your assets.
Security Trends — Retrieve risk scores and security trends to monitor your posture over time.
DNS Insights — Access DNS records discovered during the reconnaissance phase.

The Halo Security MCP Server exposes 11 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 Halo Security to CrewAI via MCP

Follow these steps to integrate the Halo Security 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 11 tools from Halo Security

Why Use CrewAI with the Halo Security MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Halo Security 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 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

Halo Security + CrewAI Use Cases

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

Automated multi-step research: a reconnaissance agent queries Halo Security 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 Halo Security, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Halo Security 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 Halo Security against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Halo Security MCP Tools for CrewAI (11)

These 11 tools become available when you connect Halo Security to CrewAI via MCP:

add_target

Add a new target for security monitoring

get_issue

Get detailed information about a specific security issue

get_security_risk

Get overall security risk scores and trends

list_certificates

List SSL/TLS certificates and their status

list_dns_records

List DNS records discovered for monitored targets

list_issues

List all discovered security issues and vulnerabilities

list_open_ports

List all discovered open ports across targets

list_scans

List history of security scans

list_targets

List all monitored targets (assets)

list_technologies

List detected technologies and libraries on targets

trigger_scan

Trigger a new security scan for a target

Example Prompts for Halo Security in CrewAI

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

"List all security issues with 'High' severity."

"Trigger a security scan for target ID 5592."

"Show me the risk score summary for our organization."

Troubleshooting Halo Security MCP Server with CrewAI

Common issues when connecting Halo Security 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

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

Halo Security + CrewAI FAQ

Common questions about integrating Halo Security 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.