# How to integrate Ipdata co MCP with Claude Code

```json
{
  "title": "How to integrate Ipdata co MCP with Claude Code",
  "toolkit": "Ipdata co",
  "toolkit_slug": "ipdata_co",
  "framework": "Claude Code",
  "framework_slug": "claude-code",
  "url": "https://composio.dev/toolkits/ipdata_co/framework/claude-code",
  "markdown_url": "https://composio.dev/toolkits/ipdata_co/framework/claude-code.md",
  "updated_at": "2026-05-12T10:16:18.761Z"
}
```

## Introduction

Manage your Ipdata co directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.
You can do this in two different ways:
- Via [Composio Connect](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_connect&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code) - Direct and easiest approach
- Via [Composio SDK](https://docs.composio.dev/docs?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_sdk) - Programmatic approach with more control

## Also integrate Ipdata co with

- [OpenAI Agents SDK](https://composio.dev/toolkits/ipdata_co/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/ipdata_co/framework/claude-agents-sdk)
- [Claude Cowork](https://composio.dev/toolkits/ipdata_co/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/ipdata_co/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/ipdata_co/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/ipdata_co/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/ipdata_co/framework/cli)
- [Google ADK](https://composio.dev/toolkits/ipdata_co/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/ipdata_co/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/ipdata_co/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/ipdata_co/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/ipdata_co/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/ipdata_co/framework/crew-ai)

## TL;DR

- Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
- Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
- Handling Large tool responses out of LLM context to minimize context rot.
- Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

## Connect Ipdata co to Claude Code

### Connecting Ipdata co to Claude Code using Composio
1. Add the Composio MCP to Claude

```bash
claude mcp add --scope user --transport http composio https://connect.composio.dev/mcp
```

## What is Claude Code?

Claude Code is Anthropic's command line developer tool that lets you use Claude directly inside your terminal. Instead of switching between your editor, browser, and chat, you can stay in your project folder and ask Claude to help you build, debug, refactor, and understand code right where you're working.
Key features include:
- Terminal-Native Experience: Work with Claude directly in your command line without switching contexts
- MCP Support: Built-in support for Model Context Protocol servers to extend Claude's capabilities
- Project Context: Claude understands your project structure and can read, write, and modify files
- Interactive Development: Ask questions, debug code, and get help in real-time while coding
- Multi-Platform: Works on macOS, Linux, WSL, and Windows

## What is the Ipdata co MCP server, and what's possible with it?

The Ipdata co MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Ipdata co account. It provides structured and secure access to IP geolocation, carrier, and threat intelligence data, so your agent can perform actions like IP lookups, ASN analysis, carrier identification, and usage monitoring on your behalf.
- Comprehensive IP lookups: Instantly retrieve detailed location, ownership, and threat profile information for any IP address worldwide.
- Advanced ASN intelligence: Dive deep into network data by performing advanced ASN lookups to get prefixes, peer relationships, and registry details for a given ASN number.
- Carrier and telecom insights: Fetch mobile carrier data—including carrier name, MCC, and MNC—for specific IPs to help identify network providers or mobile origins.
- EU-specific IP processing: Ensure data residency compliance by performing IP lookups processed and stored exclusively within the EU.
- API usage monitoring: Easily check your API request counts from the last 24 hours to stay on top of your Ipdata co usage and quotas.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `IPDATA_CO_ADVANCED_ASN_LOOKUP` | Advanced ASN Lookup | Tool to perform advanced ASN lookup returning prefixes, peers, and registry details. Use after confirming ASN number when detailed ASN info is required. |
| `IPDATA_CO_EU_LOOKUP_SPECIFIC_IP` | EU IP Lookup (Specific IP) | Lookup geolocation, threat intel, and network data for a specific IP address using the EU data residency endpoint. Use this tool when: - You need IP lookup with GDPR compliance (data processed and stored only within EU datacenters) - Looking up any IPv4 or IPv6 address for location, ASN, threat, or company information The EU endpoint (eu-api.ipdata.co) ensures all API requests are routed through EU-based servers in Frankfurt, Paris, and Ireland. |
| `IPDATA_CO_FIELD_CALLING_CODE` | IPData: Calling Code | Tool to fetch the international calling_code for an IP's country. Use when you need only the calling code field from ipdata_co. |
| `IPDATA_CO_FIELD_CARRIER` | IPDATA Field Carrier | Retrieve mobile carrier information (name, MCC, MNC) for an IP address. Returns carrier data only for mobile network IPs; non-mobile IPs return null fields. |
| `IPDATA_CO_FIELD_CITY` | Get City from IP | Tool to return only city for an IP. Use when only the city name is required. |
| `IPDATA_CO_FIELD_CONTINENT_CODE` | IPData: Continent Code | Retrieve the continent code for a given IP address. Returns a two-letter code (AF, AN, AS, EU, NA, OC, SA) indicating which continent the IP is geographically located in. Use this when you only need the continent information without full IP geolocation details. |
| `IPDATA_CO_FIELD_CONTINENT_NAME` | Get Continent Name from IP | Tool to return only continent name for an IP. Use when only the continent name is required. |
| `IPDATA_CO_FIELD_COUNT` | IPDATA Field Count | Tool to return only the request count made by your API key in the last 24 hours. Use when monitoring your API usage and you only need the total count. |
| `IPDATA_CO_FIELD_COUNTRY_CODE` | IPData: Country Code | Tool to return only country_code for an IP. Use when only the 2-letter country code is required. |
| `IPDATA_CO_FIELD_COUNTRY_NAME` | Get Country Name from IP | Get the country name for an IP address using ipdata.co geolocation API. Returns only the country name (e.g., 'United States', 'Germany', 'Japan'). Use this lightweight action when you only need the country name without full IP details. |
| `IPDATA_CO_FIELD_CURRENCY` | IPDATA Field Currency | Tool to return only currency object for an IP. Use when currency details are needed. |
| `IPDATA_CO_FIELD_EMOJI_FLAG` | Get Emoji Flag from IP | Tool to return only emoji flag for an IP. Use when only the country flag emoji is required. |
| `IPDATA_CO_FIELD_EMOJI_UNICODE` | Get Emoji Unicode from IP | Tool to return only emoji_unicode for an IP. Use when only the Unicode country flag emoji is required. |
| `IPDATA_CO_FIELD_IP` | IPData: IP | Retrieve the public IP address of the calling client. This action calls the IPData API to determine the caller's external/public IP address. It returns only the IP string with no additional geolocation data. Use this when you need to identify your own public IP address. |
| `IPDATA_CO_FIELD_IS_EU` | IPData: Is EU | Tool to return only is_eu for an IP. Use when you need to determine if an IP's country belongs to the EU. |
| `IPDATA_CO_FIELD_LANGUAGES` | IPData: Languages | Tool to return only the languages array for an IP. Use when only language details for an IP are required. |
| `IPDATA_CO_FIELD_LATITUDE` | IPData: Latitude | Tool to return only the latitude for an IP. Use when only the latitude coordinate is needed. |
| `IPDATA_CO_FIELD_LONGITUDE` | Get Longitude from IP | Tool to return only longitude for an IP. Use when only the longitude value is required. |
| `IPDATA_CO_FIELD_POSTAL` | IPData: Postal Code | Tool to return only postal code for an IP. Use when only the postal code (ZIP/postcode) is required. |
| `IPDATA_CO_FIELD_REGION` | Get Region from IP | Tool to return only region for an IP. Use when only the region name is required. |
| `IPDATA_CO_FIELD_REGION_CODE` | IPData: Region Code | Tool to return only region_code for an IP. Use when only the ISO 3166-2 region code is required. |
| `IPDATA_CO_FIELD_THREAT` | Get Threat for IP | Retrieve threat intelligence data for a specific IP address or the calling IP. Returns indicators such as Tor exit node status, proxy detection, datacenter/cloud provider identification, known attacker/abuser flags, and blocklist appearances. Use this tool when you need to assess the security risk or reputation of an IP address. |
| `IPDATA_CO_FIELD_TIME_ZONE` | IPData: Time Zone | Tool to return only the time_zone object for an IP. Use when only timezone data is required. |
| `IPDATA_CO_IP_DATA_BASIC_ASN_FOR_IP` | IPData Basic ASN for IP | Tool to return basic ASN data for a specific IP. Use when you need ASN number, organization, domain, route, and type details. |
| `IPDATA_CO_IPDATA_BULK_LOOKUP_V1` | IPData Bulk Lookup V1 | Tool to bulk lookup up to 100 IP addresses via ipdata.co. Use when you have multiple IPs and need geolocation and threat data in one call. |
| `IPDATA_CO_IP_DATA_COMPANY_FOR_IP` | Get company data for IP | Tool to retrieve company data for a given IP address. Use when you need the organization name, domain, network prefix, and usage type for an IPv4 or IPv6. |
| `IPDATA_CO_IPDATA_EU_LOOKUP_CALLING_IP` | EU IP Lookup (Calling IP) | Lookup geolocation, network, and threat data for the calling client's IP address using the EU-residency endpoint. Use this action when you need IP data processed and stored entirely within the European Union (GDPR compliance). The EU endpoint routes requests only through EU datacenters (Frankfurt, Paris, Ireland). This action automatically detects and returns data for the IP address making the API request. No IP address parameter is needed. |
| `IPDATA_CO_IP_DATA_LOOKUP_IP_V1` | IPData Lookup IP V1 | Tool to lookup comprehensive IP information (geolocation, network, company, and threat data) in one call. Use when you need all IP insights together. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Ipdata co MCP server is an implementation of the Model Context Protocol that connects Claude Code (and other AI assistants like Claude and Cursor) directly to your Ipdata co account. It provides structured and secure access so Claude can perform Ipdata co operations on your behalf.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

Before starting, make sure you have:
- Claude Pro, Max, or API billing enabled Anthropic account
- Composio API Key
- A Ipdata co account
- Basic knowledge of Python or TypeScript

### 1. Install Claude Code

To install Claude Code, use one of the following methods based on your operating system:
```bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd
```

### 2. Set up Claude Code

Open a terminal, go to your project folder, and start Claude Code:
- Claude Code will open in your terminal
- Follow the prompts to sign in with your Anthropic account
- Complete the authentication flow
- Once authenticated, you can start using Claude Code
```bash
cd your-project-folder
claude
```

### 3. Set up environment variables

Create a .env file in your project root with the following variables:
- COMPOSIO_API_KEY authenticates with Composio (get it from [Composio dashboard](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=api_key&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code))
- USER_ID identifies the user for session management (use any unique identifier)
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
```

### 4. Install Composio library

No description provided.
```python
pip install composio-core python-dotenv
```

```typescript
npm install @composio/core dotenv
```

### 5. Generate Composio MCP URL

No description provided.
```python
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["ipdata_co"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http ipdata_co-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['ipdata_co'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http ipdata_co-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);
```

### 6. Run the script and copy the MCP URL

No description provided.
```python
python generate_mcp_url.py
```

```typescript
node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts
```

### 7. Add Ipdata co MCP to Claude Code

In your terminal, add the MCP server using the command from the previous step. The command format is:
- claude mcp add registers a new MCP server with Claude Code
- --transport http specifies that this is an HTTP-based MCP server
- The server name (ipdata_co-composio) is how you'll reference it
- The URL points to your Composio Tool Router session
- --headers includes your Composio API key for authentication
After running the command, close the current Claude Code session and start a new one for the changes to take effect.
```bash
claude mcp add --transport http ipdata_co-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude
```

### 8. Verify the installation

Check that your Ipdata co MCP server is properly configured.
- This command lists all MCP servers registered with Claude Code
- You should see your ipdata_co-composio entry in the list
- This confirms that Claude Code can now access Ipdata co tools
If everything is wired up, you should see your ipdata_co-composio entry listed:
```bash
claude mcp list
```

### 9. Authenticate Ipdata co

The first time you try to use Ipdata co tools, you'll be prompted to authenticate.
- Claude Code will detect that you need to authenticate with Ipdata co
- It will show you an authentication link
- Open the link in your browser (or copy/paste it)
- Complete the Ipdata co authorization flow
- Return to the terminal and start using Ipdata co through Claude Code
Once authenticated, you can ask Claude Code to perform Ipdata co operations in natural language. For example:
- "Get city and country for this IP address"
- "Check if this IP is from the EU"
- "Find mobile carrier for a given IP"

## Complete Code

```python
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["ipdata_co"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http ipdata_co-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['ipdata_co'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http ipdata_co-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);
```

## Conclusion

You've successfully integrated Ipdata co with Claude Code using Composio's MCP server. Now you can interact with Ipdata co directly from your terminal using natural language commands.
Key features of this setup:
- Terminal-native experience without switching contexts
- Natural language commands for Ipdata co operations
- Secure authentication through Composio's managed MCP
- Tool Router for dynamic tool discovery and execution
Next steps:
- Try asking Claude Code to perform various Ipdata co operations
- Add more toolkits to your Tool Router session for multi-app workflows
- Integrate this setup into your development workflow for increased productivity
You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

## How to build Ipdata co MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/ipdata_co/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/ipdata_co/framework/claude-agents-sdk)
- [Claude Cowork](https://composio.dev/toolkits/ipdata_co/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/ipdata_co/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/ipdata_co/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/ipdata_co/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/ipdata_co/framework/cli)
- [Google ADK](https://composio.dev/toolkits/ipdata_co/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/ipdata_co/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/ipdata_co/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/ipdata_co/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/ipdata_co/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/ipdata_co/framework/crew-ai)

## Related Toolkits

- [Excel](https://composio.dev/toolkits/excel) - Microsoft Excel is a robust spreadsheet application for organizing, analyzing, and visualizing data. It's the go-to tool for calculations, reporting, and flexible data management.
- [21risk](https://composio.dev/toolkits/_21risk) - 21RISK is a web app built for easy checklist, audit, and compliance management. It streamlines risk processes so teams can focus on what matters.
- [Abstract](https://composio.dev/toolkits/abstract) - Abstract provides a suite of APIs for automating data validation and enrichment tasks. It helps developers streamline workflows and ensure data quality with minimal effort.
- [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.
- [Agenty](https://composio.dev/toolkits/agenty) - Agenty is a web scraping and automation platform for extracting data and automating browser tasks—no coding needed. It streamlines data collection, monitoring, and repetitive online actions.
- [Ambee](https://composio.dev/toolkits/ambee) - Ambee is an environmental data platform providing real-time, hyperlocal APIs for air quality, weather, and pollen. Get precise environmental insights to power smarter decisions in your apps and workflows.
- [Ambient weather](https://composio.dev/toolkits/ambient_weather) - Ambient Weather is a platform for personal weather stations with a robust API for accessing local, real-time, and historical weather data. Get detailed environmental insights directly from your own sensors for smarter apps and automations.
- [Anonyflow](https://composio.dev/toolkits/anonyflow) - Anonyflow is a service for encryption-based data anonymization and secure data sharing. It helps organizations meet GDPR, CCPA, and HIPAA data privacy compliance requirements.
- [Api ninjas](https://composio.dev/toolkits/api_ninjas) - Api ninjas offers 120+ public APIs spanning categories like weather, finance, sports, and more. Developers use it to supercharge apps with real-time data and actionable endpoints.
- [Api sports](https://composio.dev/toolkits/api_sports) - Api sports is a comprehensive sports data platform covering 2,000+ competitions with live scores and 15+ years of stats. Instantly access up-to-date sports information for analysis, apps, or chatbots.
- [Apify](https://composio.dev/toolkits/apify) - Apify is a cloud platform for building, deploying, and managing web scraping and automation tools called Actors. It lets you automate data extraction and workflow tasks at scale—no infrastructure headaches.
- [Autom](https://composio.dev/toolkits/autom) - Autom is a lightning-fast search engine results data platform for Google, Bing, and Brave. Developers use it to access fresh, low-latency SERP data on demand.
- [Beaconchain](https://composio.dev/toolkits/beaconchain) - Beaconchain is a real-time analytics platform for Ethereum 2.0's Beacon Chain. It provides detailed insights into validators, blocks, and overall network performance.
- [Big data cloud](https://composio.dev/toolkits/big_data_cloud) - BigDataCloud provides APIs for geolocation, reverse geocoding, and address validation. Instantly access reliable location intelligence to enhance your applications and workflows.
- [Bigpicture io](https://composio.dev/toolkits/bigpicture_io) - BigPicture.io offers APIs for accessing detailed company and profile data. Instantly enrich your applications with up-to-date insights on 20M+ businesses.
- [Bitquery](https://composio.dev/toolkits/bitquery) - Bitquery is a blockchain data platform offering indexed, real-time, and historical data from 40+ blockchains via GraphQL APIs. Get unified, reliable access to complex on-chain data for analytics, trading, and research.
- [Brightdata](https://composio.dev/toolkits/brightdata) - Brightdata is a leading web data platform offering advanced scraping, SERP APIs, and anti-bot tools. It lets you collect public web data at scale, bypassing blocks and friction.
- [Builtwith](https://composio.dev/toolkits/builtwith) - BuiltWith is a web technology profiler that uncovers the technologies powering any website. Gain actionable insights into analytics, hosting, and content management stacks for smarter research and lead generation.
- [Byteforms](https://composio.dev/toolkits/byteforms) - Byteforms is an all-in-one platform for creating forms, managing submissions, and integrating data. It streamlines workflows by centralizing form data collection and automation.
- [Cabinpanda](https://composio.dev/toolkits/cabinpanda) - Cabinpanda is a data collection platform for building and managing online forms. It helps streamline how you gather, organize, and analyze responses.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Ipdata co MCP?

With a standalone Ipdata co MCP server, the agents and LLMs can only access a fixed set of Ipdata co tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Ipdata co and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with Claude Code?

Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Ipdata co tools.

### Can I manage the permissions and scopes for Ipdata co while using Tool Router?

Yes, absolutely. You can configure which Ipdata co scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

### How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Ipdata co data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)