2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 10 Tools Framework

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

Vinkius supports streamable HTTP and SSE.

python
from crewai import Agent, Task, Crew

agent = Agent(
    role="SecurityTrails Specialist",
    goal="Help users interact with SecurityTrails effectively",
    backstory=(
        "You are an expert at leveraging SecurityTrails 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 SecurityTrails "
        "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)
SecurityTrails
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 SecurityTrails MCP Server

Connect your SecurityTrails account to any AI agent and empower your OSINT, bug bounty, and threat intelligence workflows with the world's most comprehensive domain and IP database.

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

What you can do

  • Attack Surface Mapping — Instantly enumerate all subdomains for any target organization to map their external footprint
  • Historical DNS Analysis — Look back in time at DNS records (A, MX, NS, TXT) to find hidden infrastructure, bypassed firewalls, or legacy systems
  • Reverse IP Lookups — Find all domains hosted on a specific IP address to identify shared hosting or related corporate assets
  • Advanced Threat Hunting — Use the SecurityTrails DSL (Domain Specific Language) to query the entire internet for specific tech stacks or vulnerable infrastructure
  • Ownership Intelligence — Access current and historical WHOIS records to track domain ownership changes and unmask hidden threat actors
  • Corporate Associations — Discover domains strongly associated with your primary target to expand your investigation scope

The SecurityTrails 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 SecurityTrails to CrewAI via MCP

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

01

Install CrewAI

Run pip install crewai

02

Replace the token

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

03

Customize the agent

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

04

Run the crew

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

Why Use CrewAI with the SecurityTrails MCP Server

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

01

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

02

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

03

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

04

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

SecurityTrails + CrewAI Use Cases

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

01

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

02

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

03

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

04

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

SecurityTrails MCP Tools for CrewAI (10)

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

01

get_api_usage

Check current SecurityTrails API quota usage

02

get_associated_domains

Great for expanding the scope of an investigation. Find other domains associated with a target domain

03

get_dns_history

Useful for finding old IPs that might still be hosting vulnerable software, or tracking infrastructure migration over time. Retrieve historical DNS records for a domain

04

get_domain_details

Essential for mapping out a target domain's existing infrastructure. Get complete domain intelligence and current DNS records

05

get_domain_tags

Get classification tags for a domain

06

get_domains_by_ip

Essential for understanding shared hosting environments or identifying hidden vhosts. Find all domains pointed to a specific IP address

07

get_subdomains

Critical for attack surface mapping and asset discovery. Returns both active and inactive subdomains. Discover all subdomains for a given domain

08

get_whois

Get current WHOIS information for a domain

09

get_whois_history

Useful for OSINT investigations to uncover historical owners before privacy protection was enabled. Retrieve historical WHOIS records for a domain

10

search_dsl

Examples: `ipv4="1.1.1.1" AND mx="alt1.aspmx.l.google.com"` or `whois_email="admin@example.com"`. Check SecurityTrails docs for full DSL syntax. Advanced search using SecurityTrails DSL

Example Prompts for SecurityTrails in CrewAI

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

01

"Find all subdomains for tesla.com."

02

"Check the historical 'A' records for example.com. Were there any changes in 2021?"

03

"What domains are hosted on the IP 8.8.8.8?"

Troubleshooting SecurityTrails MCP Server with CrewAI

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

01

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

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.

SecurityTrails + CrewAI FAQ

Common questions about integrating SecurityTrails MCP Server with CrewAI.

01

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.
02

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.
03

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.
04

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.
05

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.

Connect SecurityTrails to CrewAI

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