$ ~/registry/skill/composiohq-composio-skills-ip2location-io-automation

SKILL

ip2location-io-automation

Name: ip2location-io-automation
Author: Composio

Automate IP2Location.io lookups and related network data workflows via Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.9k

Summary

This skill appears to be an open-source prompt/workflow document rather than executable code, with no built-in secrets or declared fixed exfiltration endpoints. However, it is designed around external Rube MCP and Composio connectivity, so real use introduces third-party network calls and authorization flow, making it a low-to-moderate caution case rather than high risk.

CredentialsCaution

The material claims 'no API keys needed,' yet it requires an ACTIVE `ip2location_io` connection via `RUBE_MANAGE_CONNECTIONS` and following an auth link, which implies third-party OAuth/account authorization in practice. There is no indication that the skill itself collects or stores secrets, but connection tokens are still sensitive and their scope and handling should be reviewed.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and performing actions through Composio/Ip2location IO tooling, so user inputs and tool arguments are expected to be sent to related third-party services. No additional endpoints are listed and there is no clear sign of unrelated or covert exfiltration, but normal third-party network egress is involved.

Code executionLow risk

The system marks this as `prompt-only`; the material only provides workflow guidance and tool call examples, with no local scripts, install commands, or requests to execute arbitrary code on the host. Any actual action execution would depend on the external MCP environment rather than code embedded in this skill itself.

Data accessCaution

The skill text itself does not claim direct read/write access to local files or system resources, but the dependent MCP tools may process user-supplied data for specific Ip2location IO operations and maintain session/memory parameters. The material does not show excessive local data permissions; the main data-access surface comes from the normal operation of the external toolchain.

Supply chainLow risk

The source is a GitHub open-source repository, and the system provides `open-source` plus strong community trust (64.9k stars) as positive signals, giving it good auditability and source credibility. Although the license is unspecified, maintenance status is unknown, and the README points to external Composio/Rube service docs, the available material does not show clear supply-chain red flags.

Recommendations

Verify the data handling, logging retention, and privacy posture of `rube.app/mcp` and Composio before enabling it.
Review the OAuth/connection scopes during `ip2location_io` authorization and avoid granting access beyond business need.
Provide only the minimum data required for each task and avoid sending sensitive personal or internal confidential information.
Prefer pinned trusted versions/repository snapshots and re-check external docs and connection settings before deployment.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "ip2location-io-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/ip2location-io-automation/SKILL.md
2. Save it as ~/.claude/skills/ip2location-io-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Ip2location IO Automation via Rube MCP

Automate Ip2location IO operations through Composio's Ip2location IO toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/ip2location_io

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["ip2location_io"]
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 Ip2location IO-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `ip2location_io`
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

Automate Icypeas tasks via Rube MCP with schema-aware tool discovery.

ComposioGet→

$ loading_