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

SKILL

ipinfo-io-automation

Name: ipinfo-io-automation
Author: Composio

Automate Ipinfo IO lookups and network intelligence tasks through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill is primarily a prompt-style workflow guide, but it is designed around remote Rube MCP and Composio capabilities for tool discovery, connection management, and execution. Because the materials do not fully specify Ipinfo IO credential handling, remote data flows, or the exact privilege scope of the downstream tools, the overall posture is caution rather than high risk.

CredentialsCaution

The material claims 'no API keys needed,' but also requires an ACTIVE `ipinfo_io` connection via `RUBE_MANAGE_CONNECTIONS` and an authorization link, indicating third-party account authorization or token handling in practice. Credentials appear to be managed by the external MCP/platform, while storage, least-privilege scope, and revocation details are not described.

Network egressCaution

The skill explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and performing actions through Composio/Ipinfo IO tools. User inputs, session IDs, tool arguments, and possibly business data may be sent to the declared remote service. The endpoint is related to the stated function, but the material does not explain data minimization, retention, or whether data is further relayed to Ipinfo IO.

Code executionLow risk

There are no local install scripts, shell commands, dependency downloads, or instructions to execute code on the host. The document is mainly a workflow guide for invoking remote MCP tools. Based on the provided material, it does not show direct local code-execution capability.

Data accessCaution

The skill itself does not declare local file read/write access, but it performs `ipinfo_io`-related operations through remote tools and maintains sessions and a memory parameter. The effective data scope depends on the specific tools exposed by Rube/Composio and the connected account’s permissions; the document does not provide fine-grained boundaries, so the access surface warrants caution.

Supply chainLow risk

The source is an open-source GitHub repository with strong community adoption (64.7k stars), which materially lowers supply-chain risk. The visible content is mainly README/prompt-style material rather than an executable binary. The missing license declaration and unknown maintenance status are worth noting, but not enough on their own to justify a high-risk rating.

Recommendations

Before connecting to `https://rube.app/mcp`, verify its privacy policy, log retention, and data-sharing scope, especially whether query contents are forwarded to Composio or Ipinfo IO.
Use a least-privilege account for the `ipinfo_io` connection, and confirm that granted authorization can be revoked or rotated at any time.
For initial use, stick to tool discovery and read-only queries before running bulk or write operations without understanding the exact schemas and side effects.
Limit the context exposed to this skill on the client side, and avoid sending unnecessary sensitive information to the remote MCP.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Ipinfo IO Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/ipinfo_io

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["ipinfo_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 Ipinfo IO-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `ipinfo_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 AbuseIPDB lookups, reporting, and threat intel workflows via Rube MCP.

ComposioGet→

$ loading_