Ip2proxy Automation

What This Skill Does

This skill automates Ip2proxy operations through Composio's Ip2proxy toolkit via Rube MCP. It allows users to programmatically detect proxy and VPN usage. It is designed for developers and security engineers who need to identify and block proxy connections.

When to Use

• Automate proxy detection.
• Integrate proxy detection into applications.
• Batch process IP address data.
• Identify VPN connections.
• Block anonymous users.
• Prevent fraudulent activity.

Key Features

• Connects to Ip2proxy via Rube MCP.
• Discovers available Ip2proxy tools.
• Executes Ip2proxy tools with schema validation.
• Manages Ip2proxy connections.
• Provides error handling and connection status checks.
• Supports dynamic tool discovery.

Manual Installation

• Manual installation.
• View Full Skill Content.
• The complete markdown content that gets installed.
• Ip2proxy Automation via Rube MCP.

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

Toolkit docs: composio.dev/toolkits/ip2proxy

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Ip2proxy connection via RUBE_MANAGE_CONNECTIONS with toolkit ip2proxy 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 ip2proxy 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: "Ip2proxy 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 Ip2proxy task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["ip2proxy"] 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

's Ip2proxy toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/ip2proxy

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

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 ip2proxy If connection is not ACTIVE, follow the returned auth link to complete setup Confirm connection status shows ACTIVE before running any workflows

Always discover available tools before executing workflows:

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

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

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

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

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

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