The IP2Location IP Geolocation MCP Server retrieves comprehensive information for IPv4 and IPv6 addresses:
Geolocation Data: Country, region, city, latitude, longitude, ZIP code, and time zone
Network Details: ASN, ISP, domain, and network speed
Security Insights: Proxy detection, threat assessment, and fraud scoring
Mobile Information: MNC, MCC, and Mobile Brand
Contextual Data: Currency, language, IAB category, weather, elevation, and population
Integration: Easily integrates with Claude Desktop via JSON configuration
Usage Options: Free tier (1,000 queries/day) or enhanced access with API key (up to 50,000 queries/month)
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@IP2Location IP Geolocation MCP Server Where is 8.8.8.8 located?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
IP2Location.io MCP Server is a Model Context Protocol (MCP) server that enables MCP-compatible AI clients to perform IP address geolocation and network intelligence lookups using the IP2Location.io API.
Give it an IPv4 or IPv6 address and the MCP server can retrieve information such as geographic location, ASN, ISP, domain, network type, and proxy information, depending on your IP2Location.io API plan.
This makes it useful for IP investigation, network troubleshooting, traffic analysis, localization, security analysis, and enriching IP addresses found in logs or other datasets.
Comprehensive Geolocation Data: Retrieve country, region, city, ZIP/postal code, latitude, longitude, time zone, and other location information.
ASN Lookup: Identify the Autonomous System Number (ASN) and Autonomous System (AS) associated with an IP address.
Network Intelligence: Retrieve information such as ISP, domain, connection speed, usage type, and other network attributes depending on your plan.
Proxy and Security Information: Detect proxy-related information and, on supported plans, additional VPN, Tor, data center, threat, and fraud information.
IPv4 and IPv6 Support: Query both IPv4 and IPv6 addresses.
Bulk IP Lookup: Send multiple IP addresses in one prompt and automatically use the IP2Location.io Bulk API when available.
MCP Integration: Use IP intelligence directly from MCP-compatible AI applications.
Asynchronous Requests: Uses httpx for asynchronous API requests.
The fields returned by IP2Location.io depend on your API subscription plan.
There are two ways to use this MCP server.
Recommended when you want to connect directly to the hosted IP2Location.io MCP server.
You need:
An MCP-compatible client such as Claude Desktop
Node.js / npx
An IP2Location.io API key
Use this option when you want to run the MCP server locally.
You need:
Python 3.13 or later
uv
An MCP-compatible client such as Claude Desktop
An IP2Location.io API key
You can sign up for a free IP2Location.io API key. The Free plan provides up to 50,000 IP Geolocation API queries per month.
The underlying IP2Location.io REST API also supports limited keyless access of up to 1,000 queries per day. For this MCP server, configuring an API key is recommended and is used in the setup examples below.
You can use this MCP server in Claude Desktop in either of the following ways:
Cloud-hosted MCP server: Recommended if you want to connect directly to the hosted IP2Location.io MCP server.
Local MCP server: Use this if you want to download and run the original MCP server on your own machine.
Related MCP server: Netdetective MCP Server
Follow these steps to connect Claude Desktop to the hosted IP2Location.io MCP server.
Make sure you have installed Claude Desktop. If you have not installed it yet, download it from here for Windows and macOS, or follow this guide for Linux users.
Open the claude_desktop_config.json file in your choice of editor. If you do not have one yet, follow this guide to create one.
Add the following to your claude_desktop_config.json:
{
"mcpServers": {
"ip2location": {
"command": "npx",
"args": [
"-y",
"mcp-remote@latest",
"https://mcp.ip2location.io/",
"--header",
"X-API-Key:YOUR_API_KEY"
]
}
}
}Replace YOUR_API_KEY with your actual IP2Location.io API key. To get your API key, log in to your dashboard.
Restart Claude Desktop after saving the changes, and you should see the MCP server appear in the Connectors menu.
Follow these steps if you prefer to run the MCP server locally.
Set up the uv package manager. You can refer to the guide to do so.
Make sure you have installed Claude Desktop. If you have not installed it yet, download it from here for Windows and macOS, or follow this guide for Linux users.
Open the claude_desktop_config.json file in your choice of editor. If you do not have one yet, follow this guide to create one.
Add the following to your claude_desktop_config.json:
{
"mcpServers": {
"ip2locationio": {
"command": "uvx",
"args": [
"mcp-ip2location-io"
],
"env": {
"IP2LOCATION_API_KEY": "<YOUR API key HERE>"
}
}
}
}To get your API key, log in to your dashboard. Replace <YOUR API key HERE> in the example above with your actual API key.
Restart Claude Desktop after saving the changes, and you should see it appear in the Connectors menu.
Once the MCP server is connected, ask your MCP client questions about an IPv4 or IPv6 address using natural language. Just enter your query about the IP in a chat in Claude Desktop.
Where is the location of (IP)?Where is (IP) located?What is the latitude and longitude of (IP)?For instance, below is the result of the IP 8.8.8.8:
In Claude Desktop, the model will automatically generate the output based on the result returned by IP2Location.io MCP server.
Depending on the IP2Location.io plan being used:
Is this IP address a proxy: 8.8.8.8?You can also utilize IP2Location.io Bulk IP Geolocation API to query for multiple IP addresses.
Look up 8.8.8.8 8.8.6.6 9.9.9.9The MCP server detects multiple IP addresses and sends them to the IP2Location.io Bulk API when possible.
IP addresses can be separated by commas, spaces, or new lines.
IP2Location.io Bulk IP Geolocation API access requires an eligible paid plan.
IP2LOCATION_API_KEYYour IP2Location.io API key IP2LOCATION_API_KEY.
The Free plan currently provides up to 50,000 IP Geolocation API queries per month and access to basic IP information.
Paid plans provide higher query quotas and additional attributes.
You can sign up for a free API key, or subscribe higher plan for comprehensive geo-ip data.
Do not commit your API key to a public Git repository.
get_geolocationDescription
Fetch geolocation for the given IP address or a batch of IP addresses. It helps users retrieve detailed information such as country, region, city, latitude, longitude, ZIP code, time zone, ASN, and proxy information for any IPv4 or IPv6 address. It automatically routes requests to the IP2Location.io Bulk API for efficient processing when multiple IPs are detected.
Arguments
ip (str): One IPv4 or IPv6 address, or multiple IP addresses separated by commas, spaces, or new lines.
Single IP example:
8.8.8.8Multiple IP example:
1.1.1.1, 8.8.8.8, 9.9.9.9Return value A JSON string containing the geolocation data. If multiple IPs are queried, it returns a JSON object where each key is an IP address mapped to its respective data.
Depending on your API plan, returned information can include:
Category | Possible information |
Location & Geography | Country, region, district, city, ZIP code, latitude, longitude, time zone |
Network & Connectivity | ASN, ISP, domain, net speed, IDD code, area code, address type, usage type |
Autonomous System | ASN, AS name and, on supported plans, AS domain, AS CIDR and AS usage type |
Mobile | MCC, MNC, mobile brand |
Currency & Language | Currency code/name/symbol and language information |
Proxy & Security | Proxy status/type, provider, last seen, threat information and fraud score |
Other Data | IAB category, weather information, elevation, population and other plan-dependent data |
If a single IP request fails or the IP is invalid, the tool returns an error message as a string. For bulk requests, any individual failed IPs will return an error object mapped to that specific IP address without failing the entire batch.
Yes. IP2Location.com and IP2Location.io provide free access or free tiers.
IP2Location.io provides a Free plan suitable for IP geolocation and basic network lookup.
The Free plan includes up to 50,000 IP Geolocation API queries per month and provides basic information including:
IP address
Country
Region
City
ZIP/postal code
Latitude and longitude
Time zone
ASN
AS name
Basic proxy detection
The IP2Location.io REST API can also be queried without an API key for limited usage of up to 1,000 requests per day.
The Free plan requires attribution. Check the IP2Location.io pricing page for current limits and conditions.
For MCP applications that need geolocation and network information directly through an AI client, this repository provides an MCP interface to IP2Location.io.
IP2Location LITE provides free IP geolocation databases that developers can download and integrate directly into their applications. Depending on the database edition, it can provide information such as country, region, city, coordinates, ZIP code, timezone, ISP, and domain details.
Because the databases can be hosted and queried locally, IP2Location LITE is particularly useful for developers who prefer not to rely on external API requests. It is available in multiple formats and supports IPv4 and IPv6 data.
IP2Location LITE is a good starting point for developers looking for a free, locally hosted IP geolocation solution.
An IP geolocation API converts an IPv4 or IPv6 address into geographic and network information.
For example, an application can send:
8.8.8.8and receive information such as:
Country
Region or state
City
ZIP/postal code
Latitude and longitude
Time zone
ASN
ISP
Domain
Network usage type
Proxy information
The exact fields depend on the service and subscription level.
IP geolocation can be useful for:
Website and application localization
Regional content selection
Traffic analytics
Network troubleshooting
Security investigation
Fraud-risk analysis
Login and authentication context
Server log enrichment
IP address research
This MCP server makes these lookups accessible through natural-language prompts instead of requiring the user to construct REST API requests manually.
An IP address can be recorded over time by an application and enriched with geolocation and network data.
For example, a security application might record IP addresses from login events and use an IP intelligence service to identify:
Approximate country or city
ASN
ISP
Network operator
Proxy status
Changes in network or geographic region
This can help investigate traffic patterns or unusual network activity.
However, IP geolocation is not precise person or device tracking.
An IP address may belong to:
A shared household connection
A corporate gateway
A mobile carrier
A VPN
A proxy
A cloud provider
A data center
A NAT gateway shared by many users
Latitude and longitude returned by an IP geolocation service are approximate geographic coordinates and should not be interpreted as GPS coordinates, a street address, or proof of an individual's physical location.
This MCP server performs IP address lookups. It does not continuously monitor or track IP addresses by itself.
Yes, the IP2Location.io REST API supports this type of use case.
Normally, an IP address is passed to the API:
?ip=8.8.8.8If the ip parameter is omitted from a direct IP2Location.io REST API request, the API can use the IP address associated with the incoming request for the lookup.
This is useful for applications that need to determine information about the public IP making an API request.
Typical "my IP" data can include:
Public IP address
Country
Region
City
Coordinates
ZIP/postal code
Time zone
ASN
The get_geolocation MCP tool in this repository expects an IP address as its argument, so MCP usage is primarily designed for looking up an IP address supplied in the conversation.
The best tool depends on the information you need.
IP2Location.io is useful when you need both ASN information and IP geolocation from the same lookup.
Basic lookup information includes:
ASN
Autonomous System name
Higher-level IP2Location.io data can additionally include:
AS number
AS name
AS domain
AS CIDR
AS usage type
Through this MCP server, you may ask:
What is the ASN of 8.8.8.8?or:
Tell me who operates the network for 8.8.8.8 and where the IP is located.RDAP and WHOIS services are useful when you need registration information about IP address blocks and organizations.
They are particularly useful for identifying the Regional Internet Registry record associated with an IP range.
BGP looking glasses and routing-analysis services are more appropriate when you need information about:
Route announcements
Prefixes
BGP paths
Peering
Routing changes
Which ASN is currently announcing a network
IP intelligence services are preferable when an application needs structured information that combines several datasets, such as:
Geolocation
ASN
ISP
Proxy detection
VPN detection
Network classification
Security data
For MCP users who want geolocation and ASN information in the same workflow, this project provides a convenient interface to IP2Location.io.
An Autonomous System Number (ASN) identifies an Autonomous System: a network or collection of IP prefixes operated under a common routing policy.
Examples of organizations with ASNs include:
Internet service providers
Cloud hosting providers
Content delivery networks
Universities
Large enterprises
Telecommunications companies
ASN information can be useful when investigating an IP because it can reveal which network is responsible for routing that address.
For example:
8.8.8.8is associated with:
ASN: 15169
AS: Google LLCASN lookup is commonly used for:
Network troubleshooting
Security investigations
Traffic analysis
Identifying hosting providers
Grouping traffic by network
Investigating suspicious IP addresses
IP geolocation provides an estimated geographic location based on network and IP allocation information.
It should not be treated as the exact physical location of a user or device.
Accuracy can be affected by:
VPNs
Proxy servers
Mobile networks
Corporate networks
Carrier-grade NAT
Satellite connections
Cloud infrastructure
ISP routing and address allocation changes
Country-level results are generally more reliable than exact city or coordinate-level results.
Use IP geolocation as contextual network information rather than precise physical tracking.
The amount of information returned depends on the IP2Location.io plan.
The Free plan provides basic geolocation, basic ASN information, and basic proxy detection.
Higher-level plans can provide additional information such as:
ISP
Domain
Network speed
Usage type
Mobile network information
Detailed Autonomous System information
Detailed proxy information
VPN detection
Tor detection
Data center detection
Threat information
Fraud score
Additional geolocation attributes
For the latest query limits, fields, and pricing, refer to:
See the LICENSE.TXT file.
Fetch geolocation for the given IP address(es).
CRITICAL INSTRUCTION FOR AI AGENT: If the user provides multiple IP addresses in their prompt, DO NOT call this tool multiple times sequentially. You MUST batch all IP addresses together into a single comma-separated string and make exactly ONE tool call.
It helps users to retrieve detailed information such as country, region, city, latitude, longitude, ZIP code, time zone, ASN, and proxy information for any IPv4 or IPv6 address.
Args: ip: The IP address to analyze (IPv4 or IPv6). For multiple IPs, you MUST combine them into a single string separated by commas (e.g., "1.1.1.1, 2.2.2.2").
Returns: A JSON string result includes:
Location & Geography:
Country, region, district, city, ZIP code, latitude & longitude, time zone.
Network & Connectivity
ASN (Autonomous System Number), ISP (Internet Service Provider), domain, net speed, IDD code, area code, address type, usage type.
Mobile Information
MNC (Mobile Network Code), MCC (Mobile Country Code), Mobile Brand.
Currency & Language
currency code, currency name, currency symbol, language code, language name.
Proxy & Security
proxy type, last seen, threat level/type, proxy provider, fraud score.
Others
IAB category, weather, elevation, population and more.
Note that some information may only available in paid plan. Learn more on this in https://www.ip2location.io/pricing.
| Name | Required | Description | Default |
|---|---|---|---|
| ip | Yes |
| Name | Required | Description |
|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Describes the return structure in detail and notes that some information may be limited to paid plans. No annotations exist, so the description carries the burden; it discloses the tool is a read operation but lacks info on error handling or rate limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Well-structured with headings, critical instruction upfront, and detailed return breakdown. Slightly verbose but each section adds clear value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given one required parameter, no annotations, and presence of an output schema, the description provides extensive return field details and notes on plan limitations, making it complete for effective use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema provides no description for the 'ip' parameter (0% coverage), but the description compensates fully by explaining it accepts IPv4/IPv6 and can be comma-separated for multiple IPs.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states the tool fetches geolocation for IP addresses, specifying the range of detailed data returned. No sibling tools exist, but it distinguishes itself as a geolocation lookup tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides explicit critical instruction to batch multiple IPs into a single comma-separated string to avoid multiple calls. Does not mention when not to use or alternatives, but this is adequate given the single-purpose tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
With only one tool, there is no possibility of confusion or overlap. The tool's purpose is clearly defined and distinct.
The single tool 'get_geolocation' follows a clear verb_noun pattern, which is consistent and predictable.
While the server has only one tool, it is sufficient for its focused purpose of IP geolocation. The count is slightly below the typical 3-15 range but still reasonable.
The tool provides comprehensive geolocation data covering location, network, security, and more. No obvious gaps exist for a read-only service of this nature.
IPInfo MCP — wraps ipinfo.io (free tier, no auth required for basic usage)
Geo-based flight search MCP server. Find more flights between any two places on earth
Geospatial MCP server for earthquake, tsunami, volcano, disaster, and FX data queries.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ip2location/mcp-ip2location-io'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
