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

SKILL

ip2location-automation

Name: ip2location-automation
Author: Composio

Automate IP2Location lookups and geolocation workflows through 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-only wrapper with no stated local code execution, file access, or direct secret requirement, and its high community adoption lowers overall risk. However, it is explicitly designed to connect to remote Rube MCP and Composio/Ip2location tooling, so actual use introduces third-party network access and account authorization considerations.

CredentialsCaution

The material states that the skill itself requires no keys, but it does require activating an `ip2location` connection via `RUBE_MANAGE_CONNECTIONS` and completing authorization through a returned auth link. This means credentials likely live in the third-party connection layer rather than in the skill itself. No explicit credential theft behavior is described, but users should review the scope of access granted to Rube/Composio.

Network egressCaution

The README explicitly instructs users to add the remote MCP endpoint `https://rube.app/mcp` and references Composio toolkit docs. Although the top-level metadata says there are no remote hosts, the documentation clearly shows that it connects to Rube and may further interact with the Ip2location toolchain. This is normal remote MCP behavior, but users should verify what query inputs, session IDs, and business data are sent outward.

Code executionLow risk

The system flags this as `prompt-only`, and the material does not describe downloading binaries, executing shell/scripts locally, or requesting elevated system privileges. The visible content is limited to instructions for invoking remote MCP tools, with no apparent local code execution red flags.

Data accessLow risk

The material does not state any ability to read or write local files, databases, clipboard contents, or other host resources, nor does it request broad data access permissions. The observable data surface is mainly task inputs and connection/session data sent to remote tools, rather than excessive local access.

Supply chainLow risk

The source is an open GitHub repository with very high community adoption (64.9k stars), which materially lowers supply-chain risk. The visible content looks more like skill documentation than a closed-source executable component. Remaining caveats are the undeclared license, unknown maintenance status, and reliance on external Rube/Composio services that are not fully auditable from this repository alone.

Recommendations

Before connecting to `https://rube.app/mcp`, verify its privacy policy, data retention practices, and data flows involving Composio/Ip2location.
Grant only the minimum required permissions when authorizing the `ip2location` connection, and avoid submitting unnecessary sensitive data in tool arguments.
Test in an isolated environment first to observe what fields are sent externally during `RUBE_SEARCH_TOOLS`, connection setup, and execution.
Monitor the repository's maintenance status and confirm that the external service endpoints and documentation remain official and verifiable.

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-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/ip2location-automation/SKILL.md
2. Save it as ~/.claude/skills/ip2location-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Ip2location Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/ip2location

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["ip2location"]
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-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `ip2location`
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 Geoapify geocoding, place search, and map data workflows via Rube MCP

ComposioGet→

$ loading_