home / skills / composiohq / awesome-claude-skills / ip2whois-automation

ip2whois-automation skill

safe

/ip2whois-automation

This skill automates Ip2whois tasks via Rube MCP, discovering current tool schemas before execution to ensure accurate, up-to-date workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill ip2whois-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: ip2whois-automation
description: "Automate Ip2whois tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Ip2whois Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/ip2whois](https://composio.dev/toolkits/ip2whois)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Ip2whois connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ip2whois`
- 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.

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

## Tool Discovery

Always discover available tools before executing workflows:

```
RUBE_SEARCH_TOOLS
queries: [{use_case: "Ip2whois 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 Ip2whois task"}]
session: {id: "existing_session_id"}
```

### Step 2: Check Connection

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

| Operation | Approach |
|-----------|----------|
| Find tools | `RUBE_SEARCH_TOOLS` with Ip2whois-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ip2whois` |
| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs |
| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` |
| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` |

---
*Powered by [Composio](https://composio.dev)*

Overview

This skill automates Ip2whois operations through Composio's Ip2whois toolkit using the Rube MCP orchestration layer. It provides a safe, repeatable pattern for discovering tools, validating connections, and executing Ip2whois workflows while honoring live tool schemas. The guidance prevents common failures and ensures schema-compliant calls to RUBE_MULTI_EXECUTE_TOOL.

How this skill works

The skill first queries RUBE_SEARCH_TOOLS to fetch current tool slugs, input schemas, and recommended execution plans. It then verifies an active Ip2whois connection via RUBE_MANAGE_CONNECTIONS. Once tools and connection are confirmed, it runs tool actions through RUBE_MULTI_EXECUTE_TOOL (including memory and session handling) or bulk operations via RUBE_REMOTE_WORKBENCH.

When to use it

Automate IP-to-WHOIS lookups across large IP lists
Integrate Ip2whois into automated incident response or enrichment pipelines
Run bulk domain/IP reconnaissance tasks while preserving session state
When tool schemas may change and live discovery is required
When you need to coordinate multiple Composio tools or workflows

Best practices

Always call RUBE_SEARCH_TOOLS first and use returned schemas; never hardcode tool slugs or argument names
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE for the ip2whois toolkit before executing tools
Include a memory object (even {}) in RUBE_MULTI_EXECUTE_TOOL calls and reuse a session_id for related steps
Respect exact field names and types from tool schemas to avoid validation errors
Handle pagination tokens in responses and iterate until completion

Example use cases

Enrich a security event stream by running Ip2whois lookups for each IP and storing results
Batch process a CSV of IP addresses using RUBE_MULTI_EXECUTE_TOOL with discovered tool schemas
Create an automated workbench that runs multiple Ip2whois tasks in sequence via RUBE_REMOTE_WORKBENCH
Onboard new Ip2whois functionality by first calling RUBE_GET_TOOL_SCHEMAS to inspect full schemaRef details

FAQ

Do I need API keys to use Rube MCP?

No API keys are required. Add https://rube.app/mcp as an MCP server in your client and use the Rube MCP endpoints.

What if a tool schema changes mid-workflow?

Always re-run RUBE_SEARCH_TOOLS when starting a new workflow or if an execution returns schema validation errors. Use fresh search results to update arguments.