2,500+ MCP servers ready to use
Vinkius

SecurityTrails 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 SecurityTrails through the 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 SecurityTrails 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": {
    "securitytrails": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
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.

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

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

Follow these steps to integrate the SecurityTrails 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 SecurityTrails

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

Why Use Cline with the SecurityTrails MCP Server

Cline provides unique advantages when paired with SecurityTrails 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

SecurityTrails + Cline Use Cases

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

01

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

02

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

03

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

04

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

SecurityTrails MCP Tools for Cline (10)

These 10 tools become available when you connect SecurityTrails to Cline 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 Cline

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

Common issues when connecting SecurityTrails 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.

SecurityTrails + Cline FAQ

Common questions about integrating SecurityTrails 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 SecurityTrails to Cline

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