Securitytrails Automation

What This Skill Does

This skill automates Securitytrails operations through Composio's Securitytrails toolkit via Rube MCP. It allows users to programmatically access domain and network intelligence data. It is designed for security professionals and developers who need to integrate threat intelligence into their workflows.

When to Use

• Automate domain reconnaissance tasks.
• Monitor domain name changes.
• Identify potential phishing domains.
• Gather network intelligence data.
• Integrate threat intelligence into security tools.
• Enrich SIEM data with domain information.

Key Features

• Integrates with Rube MCP for tool discovery and execution.
• Requires an active Securitytrails connection.
• Uses RUBE_SEARCH_TOOLS to dynamically discover available tools.
• Checks connection status via RUBE_MANAGE_CONNECTIONS.
• Executes tools using RUBE_MULTI_EXECUTE_TOOL.
• Provides documentation link to Composio's Securitytrails toolkit.

Manual Installation

Automate Securitytrails operations through Composio's Securitytrails toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/securitytrails

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Securitytrails connection via RUBE_MANAGE_CONNECTIONS with toolkit securitytrails Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds Call RUBE_MANAGE_CONNECTIONS with toolkit securitytrails If connection is not ACTIVE, follow the returned auth link to complete setup Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS queries: [{use_case: "Securitytrails operations", known_fields: ""}] session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS queries: [{use_case: "your specific Securitytrails task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["securitytrails"] session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL tools: [{ tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: {/ schema-compliant args from search results /} }] memory: {} session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools Schema compliance: Use exact field names and types from the search results Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}) Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference