Ipdata.co
ipdata provides a simple HTTP-based API that allows you to look up the location, ownership, and threat profile of any IP address.
Verdict
Common use cases
- Enrich support tickets with visitor location
- Flag VPN or proxy IPs during signup
- Validate regional compliance for EU users
- Identify carrier for mobile traffic analysis
- Audit ASN peers for network security
Integration
- Vendor
- Ipdata.co
- Category
- developer-tools
- Auth
- API_KEY
- Tools
- 33
- Composio slug
ipdata_co
Tools
- 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.
- EU-only calling IP lookup
Tool to lookup the calling client IP via EU-residency endpoint. Use when you need IP data processed and stored within EU.
- EU-specific IP lookup
Tool to lookup a specific IP address via the EU-only data residency endpoint. Use when you need IP lookup processed and stored within the EU.
- Get Carrier Data for an IP
Tool to return mobile carrier data for a specific IP. Use when you need carrier name, MCC, and MNC for an IP address.
- Get City from IP
Tool to return only city for an IP. Use when only the city name is required.
- 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.
- Get Continent Name from IP
Tool to return only continent name for an IP. Use when only the continent name is required.
- Get Country Name from IP
Tool to return only country name for an IP. Use when only the country name is required.
- Get Currency for IP
Tool to retrieve currency information for a specific IP. Use when you need currency details based on the geolocation of an IP address.
- Get Emoji Flag from IP
Tool to return only emoji flag for an IP. Use when only the country flag emoji is required.
- Get Emoji Unicode from IP
Tool to return only emoji_unicode for an IP. Use when only the Unicode country flag emoji is required.
- Get Longitude from IP
Tool to return only longitude for an IP. Use when only the longitude value is required.
- Get Region from IP
Tool to return only region for an IP. Use when only the region name is required.
- Get Threat for IP
Tool to return only the threat object for the calling IP. Use when only the threat details are required for the current 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 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: 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: Continent Code
Tool to return only continent_code for an IP. Use when only the continent code is required.
- IPData: Country Code
Tool to return only country_code for an IP. Use when only the 2-letter country code is required.
- IPDATA Field Carrier
Tool to return only the carrier object for the calling IP. Use when you need mobile carrier details of a specific IP.
- 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 Field Currency
Tool to return only currency object for an IP. Use when currency details are needed.
- IPData: IP
Tool to return only the caller’s IP string. Use when you need just the origin IP of your request.
- 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: Languages
Tool to return only the languages array for an IP. Use when only language details for an IP are required.
- IPData: Latitude
Tool to return only the latitude for an IP. Use when only the latitude coordinate is needed.
- 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.
- IPData: Postal Code
Tool to return only postal code for an IP. Use when only the postal code (ZIP/postcode) is required.
- IPData: Region Code
Tool to return only region_code for an IP. Use when only the ISO 3166-2 region code is required.
- IPData Threat for IP
Tool to return threat intelligence data for a specific IP. Use when you need to determine if an IP is a Tor node, VPN, proxy, datacenter, threat actor, or listed on blocklists.
- IPData: Time Zone
Tool to return only the time_zone object for an IP. Use when only timezone data is required.
- IPData Time Zone for IP
Tool to return timezone data for a specific IP. Use when you need timezone details, including name, abbreviation, offset, DST status, and local current time for an IP.
- Lookup Calling IP
Tool to lookup full data for the calling client IP. Use when you need geolocation, network, and threat intelligence for the current IP.
Setup
Setup guide
- 11. Sign up at ipdata.co and copy your API key from the dashboard. 2. In Switchy, open Settings → Integrations → Add MCP and select Ipdata.co. 3. Paste your API key into the prompt and click Connect. 4. Switchy confirms the connection by testing a sample lookup; you'll see a green checkmark if it succeeds. 5. Open any Space, type '@Ipdata.co lookup 8.8.8.8' and send. 6. The MCP returns geolocation, ASN, and threat data for that IP in the chat. 7. If you need EU-residency processing, use the EU-specific tools explicitly (e.g. '@Ipdata.co EU-specific IP lookup 1.2.3.4'). 8. Check your Ipdata.co dashboard to monitor API usage and upgrade if you hit rate limits.
What teammates see: by default, memories from Ipdata.co are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Geolocate Support Ticket
@Ipdata.co lookup the IP 203.0.113.45 and return the city, country, and timezone so we can assign this ticket to the right support hub.Open in a Space →
Check Threat Score
@Ipdata.co lookup 198.51.100.22 and tell me if it's flagged as a proxy, VPN, or on any threat lists — we're reviewing a suspicious signup.Open in a Space →
Identify Mobile Carrier
@Ipdata.co get carrier data for 192.0.2.88 — we need the carrier name and MCC to tag this session in our mobile analytics.Open in a Space →
Lookup Company Data
@Ipdata.co get company data for 104.16.123.96 and return the organization name and domain — we're qualifying this inbound lead.Open in a Space →
EU-Residency Lookup
@Ipdata.co EU-specific IP lookup 185.60.216.35 and return full geolocation and ASN details — this request must be processed in the EU for compliance.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Ipdata.co look up the company and network details for IP address 8.8.8.8
Based on the IP lookup, 8.8.8.8 is registered to Google LLC (domain: google.com). The network prefix is 8.8.8.0/24, and the usage type is classified as 'hosting'. This IP is part of Google's public DNS infrastructure, operating from their Mountain View, California data center. The ASN is AS15169, one of the largest autonomous systems globally.
This example shows the MCP's company data lookup capability, useful for identifying who owns an IP block. Requires an API key with access to the company data endpoint. Note that results vary by IP — residential IPs may return ISP data rather than specific company details.
@Ipdata.co check the carrier information for mobile IP 203.0.113.45 and tell me which network it's on
The IP 203.0.113.45 resolves to Vodafone India (carrier name: Vodafone IN). The Mobile Country Code (MCC) is 404 and the Mobile Network Code (MNC) is 46, identifying this as Vodafone's network in India. This data is useful for understanding mobile traffic sources and can help with regional targeting or fraud detection for mobile users.
Demonstrates the carrier lookup tool, which only returns meaningful data for mobile IPs. Desktop or data center IPs will return null carrier fields. This is particularly valuable for mobile app analytics or detecting VPN/proxy usage patterns where carrier data is absent.
@Ipdata.co I have a list of visitor IPs from our EU site — can you look up 185.60.216.35 using the EU-residency endpoint and summarize the location data?
Using the EU-specific endpoint, IP 185.60.216.35 resolves to Amsterdam, Netherlands (continent: Europe). The city coordinates are approximately 52.3740° N, 4.8897° E, within the NL country code. This lookup was processed entirely within EU infrastructure, ensuring GDPR compliance for data residency requirements. The IP appears to be from a residential ISP block in the Amsterdam metro area.
Showcases the EU-residency endpoint option, critical for teams with GDPR or data sovereignty requirements. The EU endpoint has the same feature set as the global endpoint but processes all requests within EU borders. Slightly higher latency for non-EU requests, but necessary for compliance-sensitive use cases.
Use-case deep-dives
When IP geolocation catches suspicious account creation patterns
A 6-person B2B SaaS team sees 40 trial signups per day and wants to flag high-risk accounts before they hit the product. The Ipdata MCP wins here because it returns company data, carrier info, and ASN details in one lookup—enough to spot VPN farms, datacenter IPs, or mismatched billing countries without building a fraud stack. The API key auth keeps setup under 5 minutes. The trade-off: if you're processing signups in real-time at scale (500+ per hour), you'll hit rate limits on the free tier and need to budget for paid plans. For early-stage teams triaging signups manually in Slack or a dashboard, this MCP gives you the context to route suspicious accounts to manual review before they burn support time.
How IP lookup speeds up regional support assignment
A 12-person support team handles 200 tickets daily across EMEA and APAC time zones. They need to route tickets to the right region without asking customers where they're located. The Ipdata MCP solves this with the 'Get Country Name from IP' and 'Get City from IP' tools—simple lookups that return location in under 200ms. The EU-specific endpoint matters if you're handling GDPR-sensitive tickets and need data residency guarantees. The threshold: if your ticket volume exceeds 1,000 per day, you'll want to cache lookups or batch them to avoid redundant API calls. For mid-sized teams running Zendesk or Intercom workflows, this MCP turns IP addresses into routing decisions without custom middleware.
When IP geolocation isn't the right call for personalization
A 3-person marketing team wants to show localized landing pages based on visitor location. The Ipdata MCP can return continent, country, and city from an IP, but this scenario hits two problems: first, you're guessing location from IP instead of asking the user (VPNs and mobile carriers make this unreliable for personalization). Second, the 33-tool API surface is overkill—you only need country-level data, not ASN prefixes or carrier MCC codes. If you're personalizing content, use browser geolocation APIs or a CDN's edge logic instead. The Ipdata MCP makes sense here only if you're logging visitor geography for analytics or A/B test segmentation, not for real-time page rendering.
Frequently asked
What does the Ipdata.co MCP do in Switchy?
It lets your AI agents look up geographic, network, and company data for any IP address without writing API code. Agents can check where traffic originates, identify mobile carriers, resolve ASN details, or find which organization owns an IP. Useful for security workflows, fraud detection, or enriching user analytics inside Switchy conversations.
Do I need an Ipdata.co paid plan to connect the MCP?
You need an Ipdata.co API key, which means at least their free tier. The free plan caps at 1,500 requests per day. If your team runs frequent IP lookups across multiple agents or conversations, you'll hit that limit quickly and need a paid plan. Switchy doesn't include Ipdata credits.
Can the MCP look up IPv6 addresses and ASN prefix lists?
Yes. The MCP supports both IPv4 and IPv6 lookups across all 33 tools, including advanced ASN queries that return prefix announcements, peering relationships, and registry metadata. If you need EU-residency guarantees for GDPR, two dedicated tools route requests through Ipdata's EU-only endpoints.
How is this different from calling Ipdata's API directly in code?
The MCP removes the need to write HTTP clients, parse JSON responses, or manage rate limits in your application. Your agents call natural-language tools like "Get Country Name from IP" instead of constructing REST requests. You still pay Ipdata's pricing, but orchestration happens inside Switchy's conversation layer.
Who on the team should connect the Ipdata.co MCP?
Whoever holds the Ipdata.co account and API key. Once connected, all workspace members can invoke the tools in their agent conversations. If you rotate API keys for security, the person who connected it will need to update the credential in Switchy's integration settings.