# How to integrate Ipinfo io MCP with Vercel AI SDK v6 ```json { "title": "How to integrate Ipinfo io MCP with Vercel AI SDK v6", "toolkit": "Ipinfo io", "toolkit_slug": "ipinfo_io", "framework": "Vercel AI SDK", "framework_slug": "ai-sdk", "url": "https://composio.dev/toolkits/ipinfo_io/framework/ai-sdk", "markdown_url": "https://composio.dev/toolkits/ipinfo_io/framework/ai-sdk.md", "updated_at": "2026-05-12T10:16:20.672Z" } ``` ## Introduction This guide walks you through connecting Ipinfo io to Vercel AI SDK v6 using the Composio tool router. By the end, you'll have a working Ipinfo io agent that can get geolocation details for this ip address, check if this ip is using a vpn or proxy, find the company behind this ip address through natural language commands. This guide will help you understand how to give your Vercel AI SDK agent real control over a Ipinfo io account through Composio's Ipinfo io MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Ipinfo io with - [OpenAI Agents SDK](https://composio.dev/toolkits/ipinfo_io/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/ipinfo_io/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/ipinfo_io/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/ipinfo_io/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/ipinfo_io/framework/codex) - [OpenClaw](https://composio.dev/toolkits/ipinfo_io/framework/openclaw) - [Hermes](https://composio.dev/toolkits/ipinfo_io/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/ipinfo_io/framework/cli) - [Google ADK](https://composio.dev/toolkits/ipinfo_io/framework/google-adk) - [LangChain](https://composio.dev/toolkits/ipinfo_io/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/ipinfo_io/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/ipinfo_io/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/ipinfo_io/framework/crew-ai) ## TL;DR Here's what you'll learn: - How to set up and configure a Vercel AI SDK agent with Ipinfo io integration - Using Composio's Tool Router to dynamically load and access Ipinfo io tools - Creating an MCP client connection using HTTP transport - Building an interactive CLI chat interface with conversation history management - Handling tool calls and results within the Vercel AI SDK framework ## What is Vercel AI SDK? The Vercel AI SDK is a TypeScript library for building AI-powered applications. It provides tools for creating agents that can use external services and maintain conversation state. Key features include: - streamText: Core function for streaming responses with real-time tool support - MCP Client: Built-in support for Model Context Protocol via @ai-sdk/mcp - Step Counting: Control multi-step tool execution with stopWhen: stepCountIs() - OpenAI Provider: Native integration with OpenAI models ## What is the Ipinfo io MCP server, and what's possible with it? The Ipinfo io MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Ipinfo io account. It provides structured and secure access to IP address intelligence, so your agent can perform actions like geolocating IPs, retrieving company and carrier details, detecting privacy risks, and fetching abuse contacts automatically. - Bulk IP address lookups: Perform high-volume geolocation or information retrieval for up to 1,000 IPs or URLs in a single request for audits, analytics, or security reviews. - Comprehensive IP geolocation and details: Instantly fetch precise geolocation, ASN, and network data for any IP address—including your own—helping with network diagnostics and user profiling. - Company and carrier information retrieval: Ask your agent to identify the organization or mobile carrier behind an IP address for enhanced business intelligence or fraud analysis. - Abuse contact identification: Quickly retrieve the correct abuse reporting contact for any IP, streamlining incident response or reporting suspicious activity. - Privacy and anonymization detection: Let your agent check if an IP is using VPNs, proxies, Tor, or hosting services to identify anonymized or risky traffic for extra security and compliance. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `IPINFO_IO_BATCH_LITE_LOOKUP` | Batch Lite Lookup | Perform bulk Lite IP lookups for up to 1000 IPs in a single request. Returns lightweight IP information including ASN (Autonomous System Number), AS organization details, and geolocation (country and continent). Use cases: - Look up geolocation for multiple IPs at once - Identify the ISP/organization owning IP addresses - Detect bogon/private IPs (192.168.x.x, 10.x.x.x, etc.) - Retrieve specific fields only (e.g., '8.8.8.8/country' returns just the country) Supports both IPv4 and IPv6 addresses. | | `IPINFO_IO_BATCH_LOOKUP` | Batch IP Lookup | Perform batch IP lookups to retrieve geolocation and ASN information for multiple IPs in a single request. Use this tool when you need to look up multiple IP addresses efficiently. Supports up to 1000 IPs per request. IMPORTANT: For free tier API tokens, prefix each IP with 'lite/' (e.g., 'lite/8.8.8.8'). Bare IPs without the 'lite/' prefix require a paid subscription. | | `IPINFO_IO_GET_ABUSE_CONTACT` | Get Abuse Contact | Retrieve abuse contact and organization information for an IP address. Use this tool when you need to identify who owns an IP address or find contact information for reporting malicious activity. Note: Full abuse contact details (email, phone, name) require IPinfo Enterprise tier. For standard tiers, returns organization info (org, country, city, region) which can be used to identify the IP owner. | | `IPINFO_IO_GET_CARRIER_INFO` | Get IP Carrier Info | Retrieves mobile carrier information for a given IP address. Returns the carrier name, Mobile Country Code (MCC), and Mobile Network Code (MNC) for mobile network IPs. For non-mobile IPs (e.g., datacenter, ISP), returns the organization/ASN name with empty MCC/MNC values. Useful for identifying if an IP belongs to a mobile carrier network and which carrier it is. | | `IPINFO_IO_GET_CITY_BY_IP` | Get City by IP | Retrieve the city name for a specific IP address. Returns the city name as plain text for any IPv4 or IPv6 address. | | `IPINFO_IO_GET_COMPANY_INFO` | Get Company Info for an IP | Retrieve company/organization information for an IP address. Returns the company name, domain, and type (business, ISP, hosting, etc.) associated with the IP. Supports both IPv4 and IPv6 addresses. | | `IPINFO_IO_GET_CORE_FIELD_BY_ME` | Get Core Field by Me | Retrieve a specific field from core IP information about the current IP. Use this tool when you need just one specific piece of information (like city, country, hostname, or AS details) about the caller's IP address instead of fetching the complete IP profile. | | `IPINFO_IO_GET_COUNTRY_BY_IP` | Get Country by IP | Retrieve the two-letter ISO 3166 country code for an IP address. Use when you need to quickly identify which country an IP address is located in without requesting full geolocation details. | | `IPINFO_IO_GET_CURRENT_IP` | Get Current IP | Retrieve the current public/external IP address. Use this tool when you need to determine the caller's public IP address. | | `IPINFO_IO_GET_CURRENT_IP_INFO` | Get Current IP Information | Retrieve comprehensive IP information about the caller's current IP address. Returns geolocation (city, region, country, coordinates, postal code, timezone), ASN details, company info, privacy detection flags (VPN/proxy/Tor), carrier info for mobile IPs, and abuse contact information. Use this when you need to identify and analyze the caller's IP address without specifying an IP parameter. | | `IPINFO_IO_GET_CURRENT_LOC` | Get Current Location | Retrieve geographic coordinates for the current IP address. Returns the latitude and longitude of the caller's IP address as a comma-separated string in the format 'latitude,longitude'. Use this when you need quick location coordinates without full geolocation details. | | `IPINFO_IO_GET_CURRENT_REGION` | Get Current Region | Retrieve the region/state for the caller's current IP address. Use this tool when you need to identify the geographic region or state where the current IP address is located. Returns a plain text region name. | | `IPINFO_IO_GET_GEO_BY_IP` | Get Geo by IP | Get geolocation data only for an IP address. Returns city, region, country, continent, coordinates, timezone, and postal code. Use this when you need detailed geographic location information for an IP address. | | `IPINFO_IO_GET_HOSTNAME_BY_IP` | Get Hostname by IP | Retrieve the hostname (reverse DNS) for an IP address. Use this tool to look up the hostname associated with any IPv4 or IPv6 address. Returns the hostname as a string. If no hostname is available, returns an empty string. | | `IPINFO_IO_GET_IP_BY_IP` | Get IP by IP | Retrieve the IP address for a specified IP as plain text. Use this tool to echo back an IP address from the IPInfo API. This endpoint returns the IP address as plain text (not JSON). Useful for verifying IP address formatting or testing connectivity. | | `IPINFO_IO_GET_IP_INFO` | Get IP Information | Retrieve geolocation and ASN information for an IP address. Use this tool to look up country, continent, and Autonomous System (AS) details for any IPv4 or IPv6 address. Pass 'me' or omit the ip parameter to get information about the caller's own IP address. For private/reserved (bogon) IP addresses like 192.168.x.x or 10.x.x.x, only the ip and bogon fields will be populated. | | `IPINFO_IO_GET_IP_INFO_BY_IP` | Get Comprehensive IP Information | Retrieve comprehensive information about a specified IP address. Returns geographic location (city, region, country, coordinates), ASN details, company/organization info, privacy detection flags (VPN, proxy, Tor), carrier information for mobile IPs, and associated domain names. Supports both IPv4 and IPv6 addresses. | | `IPINFO_IO_GET_LITE_FIELD_BY_IP` | Get Lite Field By IP | Retrieve a specific field from lightweight IP information. Use this tool to get a single piece of information about an IP address (e.g., just the country, or just the ASN) without fetching the full IP data. This is more efficient when you only need one specific field. Supported fields: ip, asn, as_name, as_domain, country_code, country, continent_code, continent. | | `IPINFO_IO_GET_LOCATION_BY_IP` | Get Location by IP | Retrieve geographic coordinates (latitude, longitude) for an IP address. Returns location as comma-separated text in the format 'latitude,longitude'. Use when you need precise geolocation coordinates for IPv4 or IPv6 addresses. | | `IPINFO_IO_GET_ORG_BY_IP` | Get Organization by IP | Retrieve ASN and organization name for an IP address as plain text. Use this tool when you need to quickly identify which organization or ASN owns a specific IP address. Returns a plain text string containing the Autonomous System Number (ASN) and organization name (e.g., 'AS15169 Google LLC'). | | `IPINFO_IO_GET_PLUS_FIELD_BY_ME` | Get Plus Field for Current IP | Retrieve a specific field from plus IP information about the current IP. Use this tool to get individual fields from IPInfo's Plus API for your current IP address. This includes detailed geographic data (city, region, coordinates), AS information, mobile carrier details, and privacy flags. Each field returns its specific data type (string, number, boolean, or object). Note: This endpoint requires a Plus API subscription. Returns 403 if the subscription doesn't include Plus features. | | `IPINFO_IO_GET_POSTAL_BY_IP` | Get Postal Code by IP | Retrieve the postal/zip code for an IP address. Use this when you need to identify the geographic postal code associated with an IPv4 or IPv6 address. | | `IPINFO_IO_GET_PRIVACY_DETAILS` | Get IP Privacy Details | Retrieve privacy/anonymous IP detection flags for an IP address. Returns whether the IP is associated with VPN, proxy, Tor, relay, or hosting services. Use this to detect potentially anonymous or masked traffic from an IP address. Note: This endpoint requires a Privacy Detection API subscription. If privacy data is unavailable for your subscription level, the action will return default values (all flags set to False). | | `IPINFO_IO_GET_REGION_BY_IP` | Get Region by IP | Retrieve the region/state for a specified IP address. Use this tool when you need to identify the geographic region or state where a specific IPv4 or IPv6 address is located. Returns a plain text region name. | | `IPINFO_IO_GET_TIMEZONE_BY_IP` | Get Timezone by IP | Retrieve the IANA timezone for a given IP address. Use this tool when you need to determine the local timezone of an IP address location for scheduling, time conversion, or geographic analysis purposes. | | `IPINFO_IO_GET_TOKEN_INFO` | Get Token Information | Retrieve API service request limit information by access token. Returns usage statistics, request limits, remaining quota, and available API features. Use this to check your token's rate limits, current usage, and feature access before making other API calls. | | `IPINFO_IO_MAP_IPS` | Map IP Addresses | Create an IPinfo map visualization from a list of IP addresses. Use this tool to generate an interactive map showing the geographic locations of multiple IP addresses. The tool accepts up to 500,000 IPs and returns a link to a visual map where all IP locations are plotted. Useful for visualizing the geographic distribution of network traffic, analyzing user locations, or investigating security incidents across multiple IP addresses. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Ipinfo io MCP server is an implementation of the Model Context Protocol that connects your AI agent to Ipinfo io. It provides structured and secure access so your agent can perform Ipinfo io operations on your behalf through a secure, permission-based interface. 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 you begin, make sure you have: - Node.js and npm installed - A Composio account with API key - An OpenAI API key ### 1. Getting API Keys for OpenAI and Composio OpenAI API Key - Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key. You'll need credits to use the models, or you can connect to another model provider. - Keep the API key safe. Composio API Key - Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Navigate to your API settings and generate a new API key. - Store this key securely as you'll need it for authentication. ### 2. Install required dependencies First, install the necessary packages for your project. What you're installing: - @ai-sdk/openai: Vercel AI SDK's OpenAI provider - @ai-sdk/mcp: MCP client for Vercel AI SDK - @composio/core: Composio SDK for tool integration - ai: Core Vercel AI SDK - dotenv: Environment variable management ```bash npm install @ai-sdk/openai @ai-sdk/mcp @composio/core ai dotenv ``` ### 3. Set up environment variables Create a .env file in your project root. What's needed: - OPENAI_API_KEY: Your OpenAI API key for GPT model access - COMPOSIO_API_KEY: Your Composio API key for tool access - COMPOSIO_USER_ID: A unique identifier for the user session ```bash OPENAI_API_KEY=your_openai_api_key_here COMPOSIO_API_KEY=your_composio_api_key_here COMPOSIO_USER_ID=your_user_id_here ``` ### 4. Import required modules and validate environment What's happening: - We're importing all necessary libraries including Vercel AI SDK's OpenAI provider and Composio - The dotenv/config import automatically loads environment variables - The MCP client import enables connection to Composio's tool server ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Composio } from "@composio/core"; import * as readline from "readline"; import { streamText, type ModelMessage, stepCountIs } from "ai"; import { createMCPClient } from "@ai-sdk/mcp"; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!process.env.OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set"); if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set"); if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set"); const composio = new Composio({ apiKey: composioAPIKey, }); ``` ### 5. Create Tool Router session and initialize MCP client What's happening: - We're creating a Tool Router session that gives your agent access to Ipinfo io tools - The create method takes the user ID and specifies which toolkits should be available - The returned mcp object contains the URL and authentication headers needed to connect to the MCP server - This session provides access to all Ipinfo io-related tools through the MCP protocol ```typescript async function main() { // Create a tool router session for the user const session = await composio.create(composioUserID!, { toolkits: ["ipinfo_io"], }); const mcpUrl = session.mcp.url; ``` ### 6. Connect to MCP server and retrieve tools What's happening: - We're creating an MCP client that connects to our Composio Tool Router session via HTTP - The mcp.url provides the endpoint, and mcp.headers contains authentication credentials - The type: "http" is important - Composio requires HTTP transport - tools() retrieves all available Ipinfo io tools that the agent can use ```typescript const mcpClient = await createMCPClient({ transport: { type: "http", url: mcpUrl, headers: session.mcp.headers, // Authentication headers for the Composio MCP server }, }); const tools = await mcpClient.tools(); ``` ### 7. Initialize conversation and CLI interface What's happening: - We initialize an empty messages array to maintain conversation history - A readline interface is created to accept user input from the command line - Instructions are displayed to guide the user on how to interact with the agent ```typescript let messages: ModelMessage[] = []; console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n"); console.log( "Ask any questions related to ipinfo_io, like summarize my last 5 emails, send an email, etc... :)))\n", ); const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "> ", }); rl.prompt(); ``` ### 8. Handle user input and stream responses with real-time tool feedback What's happening: - We use streamText instead of generateText to stream responses in real-time - toolChoice: "auto" allows the model to decide when to use Ipinfo io tools - stopWhen: stepCountIs(10) allows up to 10 steps for complex multi-tool operations - onStepFinish callback displays which tools are being used in real-time - We iterate through the text stream to create a typewriter effect as the agent responds - The complete response is added to conversation history to maintain context - Errors are caught and displayed with helpful retry suggestions ```typescript rl.on("line", async (userInput: string) => { const trimmedInput = userInput.trim(); if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) { console.log("\nGoodbye!"); rl.close(); process.exit(0); } if (!trimmedInput) { rl.prompt(); return; } messages.push({ role: "user", content: trimmedInput }); console.log("\nAgent is thinking...\n"); try { const stream = streamText({ model: openai("gpt-5"), messages, tools, toolChoice: "auto", stopWhen: stepCountIs(10), onStepFinish: (step) => { for (const toolCall of step.toolCalls) { console.log(`[Using tool: ${toolCall.toolName}]`); } if (step.toolCalls.length > 0) { console.log(""); // Add space after tool calls } }, }); for await (const chunk of stream.textStream) { process.stdout.write(chunk); } console.log("\n\n---\n"); // Get final result for message history const response = await stream.response; if (response?.messages?.length) { messages.push(...response.messages); } } catch (error) { console.error("\nAn error occurred while talking to the agent:"); console.error(error); console.log( "\nYou can try again or restart the app if it keeps happening.\n", ); } finally { rl.prompt(); } }); rl.on("close", async () => { await mcpClient.close(); console.log("\n👋 Session ended."); process.exit(0); }); } main().catch((err) => { console.error("Fatal error:", err); process.exit(1); }); ``` ## Complete Code ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Composio } from "@composio/core"; import * as readline from "readline"; import { streamText, type ModelMessage, stepCountIs } from "ai"; import { createMCPClient } from "@ai-sdk/mcp"; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!process.env.OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set"); if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set"); if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set"); const composio = new Composio({ apiKey: composioAPIKey, }); async function main() { // Create a tool router session for the user const session = await composio.create(composioUserID!, { toolkits: ["ipinfo_io"], }); const mcpUrl = session.mcp.url; const mcpClient = await createMCPClient({ transport: { type: "http", url: mcpUrl, headers: session.mcp.headers, // Authentication headers for the Composio MCP server }, }); const tools = await mcpClient.tools(); let messages: ModelMessage[] = []; console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n"); console.log( "Ask any questions related to ipinfo_io, like summarize my last 5 emails, send an email, etc... :)))\n", ); const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "> ", }); rl.prompt(); rl.on("line", async (userInput: string) => { const trimmedInput = userInput.trim(); if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) { console.log("\nGoodbye!"); rl.close(); process.exit(0); } if (!trimmedInput) { rl.prompt(); return; } messages.push({ role: "user", content: trimmedInput }); console.log("\nAgent is thinking...\n"); try { const stream = streamText({ model: openai("gpt-5"), messages, tools, toolChoice: "auto", stopWhen: stepCountIs(10), onStepFinish: (step) => { for (const toolCall of step.toolCalls) { console.log(`[Using tool: ${toolCall.toolName}]`); } if (step.toolCalls.length > 0) { console.log(""); // Add space after tool calls } }, }); for await (const chunk of stream.textStream) { process.stdout.write(chunk); } console.log("\n\n---\n"); // Get final result for message history const response = await stream.response; if (response?.messages?.length) { messages.push(...response.messages); } } catch (error) { console.error("\nAn error occurred while talking to the agent:"); console.error(error); console.log( "\nYou can try again or restart the app if it keeps happening.\n", ); } finally { rl.prompt(); } }); rl.on("close", async () => { await mcpClient.close(); console.log("\n👋 Session ended."); process.exit(0); }); } main().catch((err) => { console.error("Fatal error:", err); process.exit(1); }); ``` ## Conclusion You've successfully built a Ipinfo io agent using the Vercel AI SDK with streaming capabilities! This implementation provides a powerful foundation for building AI applications with natural language interfaces and real-time feedback. Key features of this implementation: - Real-time streaming responses for a better user experience with typewriter effect - Live tool execution feedback showing which tools are being used as the agent works - Dynamic tool loading through Composio's Tool Router with secure authentication - Multi-step tool execution with configurable step limits (up to 10 steps) - Comprehensive error handling for robust agent execution - Conversation history maintenance for context-aware responses You can extend this further by adding custom error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows. ## How to build Ipinfo io MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/ipinfo_io/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/ipinfo_io/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/ipinfo_io/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/ipinfo_io/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/ipinfo_io/framework/codex) - [OpenClaw](https://composio.dev/toolkits/ipinfo_io/framework/openclaw) - [Hermes](https://composio.dev/toolkits/ipinfo_io/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/ipinfo_io/framework/cli) - [Google ADK](https://composio.dev/toolkits/ipinfo_io/framework/google-adk) - [LangChain](https://composio.dev/toolkits/ipinfo_io/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/ipinfo_io/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/ipinfo_io/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/ipinfo_io/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 Ipinfo io MCP? With a standalone Ipinfo io MCP server, the agents and LLMs can only access a fixed set of Ipinfo io tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Ipinfo io and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Vercel AI SDK v6? Yes, you can. Vercel AI SDK v6 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 Ipinfo io tools. ### Can I manage the permissions and scopes for Ipinfo io while using Tool Router? Yes, absolutely. You can configure which Ipinfo io 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 Ipinfo io data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)