IPGeolocation.io MCP Server

Official MCP server for IPGeolocation.io. Includes 16 MCP tools: IP geolocation, threat/VPN/proxy detection, timezone lookups and conversions, sunrise/sunset/moon data, ASN details, abuse contacts, and user-agent parsing. Seven tools work on the free plan (1,000 credits/day). Paid plans unlock all 16 plus bulk endpoints (up to 50,000 items per call; default 1,000, configurable via `IPGEOLOCATION_MCP_MAX_BULK_ITEMS`).

Works with Claude Desktop, Cursor, Windsurf, VS Code, Codex, Cline, Glama, and any other MCP client.

Quick Start

1. Create a free IPGeolocation API key

2. Cursor users can install in one click:

3. Add this to your MCP client config (see Install by Client below for the exact config file path for your client):

{
  "mcpServers": {
    "ipgeolocation": {
      "command": "npx",
      "args": ["-y", "ipgeolocation-io-mcp"],
      "env": {
        "IPGEOLOCATION_API_KEY": ""
      }
    }
  }
}

4. Restart your client.

5. Test it: ask "Where is 8.8.8.8 located?"

Table of Contents

• Quick Start
• Install by Client
• Verify It Works
• Tools by Plan
• Tool Reference
• Prompt Examples
• Example Answers and Tool Output
• Error Codes
• How It Works
• Caching
• Environment Variables
• Building from Source
• Docker
• Testing
• Troubleshooting
• Pricing
• Links
• License
• Privacy Policy

Install by Client

Requirements

• Node.js 22 or later
• `npx` available in your terminal
• An IPGeolocation.io API key for most tools

`get_my_ip` works without an API key. Everything else requires one.

Sign up for a free IPGeolocation API key

Codex CLI

codex mcp add ipgeolocation --env IPGEOLOCATION_API_KEY= -- npx -y ipgeolocation-io-mcp
codex mcp list

Start a new Codex session after adding the server.

Claude Desktop

Add to `claude_desktop_config.json`:

{
  "mcpServers": {
    "ipgeolocation": {
      "command": "npx",
      "args": ["-y", "ipgeolocation-io-mcp"],
      "env": {
        "IPGEOLOCATION_API_KEY": ""
      }
    }
  }
}

Restart Claude Desktop after saving. We also ship `manifest.json` for clients that support MCP Bundles.

Cline

Open MCP Servers panel > Configure > Advanced MCP Settings. Add to `cline_mcp_settings.json`:

{
  "mcpServers": {
    "ipgeolocation": {
      "command": "npx",
      "args": ["-y", "ipgeolocation-io-mcp"],
      "env": {
        "IPGEOLOCATION_API_KEY": ""
      }
    }
  }
}

Restart Cline after saving.

Cursor

One-click install:

Or add to `.cursor/mcp.json` manually:

{
  "mcpServers": {
    "ipgeolocation": {
      "command": "npx",
      "args": ["-y", "ipgeolocation-io-mcp"],
      "env": {
        "IPGEOLOCATION_API_KEY": ""
      }
    }
  }
}

Restart Cursor after saving.

Windsurf

Add to `~/.codeium/windsurf/mcp_config.json`:

{
  "mcpServers": {
    "ipgeolocation": {
      "command": "npx",
      "args": ["-y", "ipgeolocation-io-mcp"],
      "env": {
        "IPGEOLOCATION_API_KEY": ""
      }
    }
  }
}

Restart Windsurf after saving.

VS Code / GitHub Copilot

Add to your VS Code `settings.json`:

{
  "mcp": {
    "servers": {
      "ipgeolocation": {
        "command": "npx",
        "args": ["-y", "ipgeolocation-io-mcp"],
        "env": {
          "IPGEOLOCATION_API_KEY": ""
        }
      }
    }
  }
}

Restart VS Code after saving.

Glama

You can try the server on Glama directly. Only `IPGEOLOCATION_API_KEY` is required. Leave other environment variable fields empty unless you want to change cache, timeout, or output limits.

If you don't have a key yet, create a free IPGeolocation API key.

Any Other MCP Client

Use this config:

{
  "command": "npx",
  "args": ["-y", "ipgeolocation-io-mcp"],
  "env": {
    "IPGEOLOCATION_API_KEY": ""
  }
}

Verify It Works

Try these after setup:

Tools by Plan

Free Plan

1,000 credits per day. These 7 tools are available:

Paid Plans

All 16 tools. Paid plans also add `network`, `company`, and extended `asn` fields to `lookup_ip`, plus the `include` parameter for `security`, `abuse`, `hostname`, `liveHostname`, `hostnameFallbackLive`, `user_agent`, `geo_accuracy`, `dma_code`, or `*`.

Credit math for `lookup_ip` with `include`:

For current plan details and pricing, see the IPGeolocation pricing page.

Tool Reference

lookup_ip

Single IP or domain lookup. Free and paid. 1 credit.

Use this when you need location, timezone, currency, or ASN for one IP address. On paid plans you can add `include` modules to pull security, abuse, or hostname data in the same call, which avoids extra requests.

Free plan returns base location, country metadata, currency, timezone, and basic ASN. Paid plans add `network`, `company`, extended ASN, and the `include` parameter. Note that domain lookups require a paid plan.

Tip: combining `include` with `fields` can cut your credit cost. For example, `include=security&fields=security` costs 2 credits instead of 3 because you skip the base geolocation response. Similarly, `include=abuse&fields=abuse` costs 1 credit instead of 2.

bulk_lookup_ip

Batch IP lookup. Paid. 1 credit per IP.

Takes an array of IPs or domains (up to 1,000 by default, configurable with `IPGEOLOCATION_MCP_MAX_BULK_ITEMS`). Supports the same `include`, `fields`, and `excludes` options as `lookup_ip`.

get_my_ip

Returns the public IP of the machine running the server. Free. 0 credits. No API key needed.

Takes no parameters. Always hits the network (not cached). Useful as a quick check to confirm the server process is up.

check_security

Threat and anonymity data for one IP. Paid. 2 credits.

Returns threat score, VPN/proxy/Tor flags, provider names, confidence scores, bot/spam indicators, anonymity flags, and cloud-provider status.

If the same prompt also asks for location, ASN, or abuse data, you're better off using `lookup_ip` with `include=security` because it bundles everything in one call (3 credits total instead of 2 + 1 separately).

bulk_security_check

Batch version of `check_security`. Paid. 2 credits per IP.

get_timezone

Current time and timezone details for a location. Free and paid. 1 credit.

Accepts IANA timezone names, coordinates, IP addresses, airport codes (IATA/ICAO), or UN/LOCODEs. The response includes timezone offsets, date/datetime variants, `current_time`, `current_time_unix`, `time_24`, `time_12`, `week`, `month`, `year`, timezone abbreviations, and DST transition details.

Always hits the network (not cached) because it returns the current time.

convert_timezone

Converts a time between two locations. Free and paid. 1 credit.

Takes the same location input types as `get_timezone` for both source and destination. If you leave out the `time` parameter, it converts the current time. Always hits the network (not cached).

get_astronomy

Sun and moon data for one location on one date. Free and paid. 1 credit.

Returns sunrise, sunset, moonrise, moonset, morning and evening twilight, solar noon, day length, moon phase, sun/moon status flags, and live sun/moon position (altitude, azimuth).

Always hits the network (not cached) because skipping `date` defaults to today.

get_astronomy_time_series

Astronomy data for a date range, up to 90 days. Free and paid. 1 credit per request.

Each daily entry includes `mid_night`, `night_end`, `morning`, `sunrise`, `sunset`, `evening`, `night_begin`, `sun_status`, `solar_noon`, `day_length`, `moon_phase`, `moonrise`, `moonset`, and `moon_status`. Use this instead of calling `get_astronomy` repeatedly for a range.

parse_user_agent

Parses one UA string into browser, device, OS, and engine data. Paid. 1 credit.

Also classifies bots and crawlers. Note: this parses the `uaString` you pass in. It does not infer a caller UA from the MCP connection itself.

Returns `name`, `type`, `version`, `device`, `engine`, and `operating_system`.

bulk_parse_user_agent

Batch version of `parse_user_agent`. Paid. 1 credit per string.

Takes up to 1,000 strings per request by default (configurable with `IPGEOLOCATION_MCP_MAX_BULK_ITEMS`).

lookup_company

Returns just the company name and ASN holder for one IP. Paid. 1 credit.

Returns `company` and `asn` objects. `lookup_ip` returns the same data plus location, timezone, and more. Use this when the company/ASN pair is all you need and you want a smaller response.

lookup_currency

Currency, country calling code, TLD, and languages for one IP. Free and paid. 1 credit.

Returns `currency` and `country_metadata` objects.

lookup_network

Route prefix, connection type, and anycast status for one IP. Paid. 1 credit.

Returns a `network` object with `connection_type`, `route`, and `is_anycast`.

lookup_asn

Full ASN lookup. Paid. 1 credit.

`lookup_ip` also returns an `asn` object, but only with basic metadata. This tool returns the full ASN record, including peers, upstreams, downstreams, routes, and WHOIS. Call it once with the `include` fields you need, then filter locally instead of making multiple calls for different slices.

get_abuse_contact

Abuse contact details for one IP. Paid. 1 credit.

Returns the abuse route, country, contact name, organization, address, email addresses, and phone numbers. If you also need geolocation or security data for the same IP, use `lookup_ip` with `include=abuse` (or `include=security,abuse`) to get everything in one call.

Prompt Examples

Check if an IP is safe

• Is 49.12.212.42 safe to trust in our network? Give me the threat summary and city.
• Check these IPs for VPN, proxy, Tor, bot, and spam indicators: 49.12.212.42, 2.56.12.11, 8.8.8.8
• For 203.0.113.42, tell me the threat score, whether it is a cloud provider, and whether it looks like a relay.

Find who owns an IP

• Who uses 1.1.1.1 and which ASN routes it?
• For AS24940, list upstream ASN numbers only.
• Is this IP anycast and what route prefix is announced for it: 1.1.1.1

Get abuse contacts

• For IP 2.56.12.11, give me the abuse contact email, phone number, and organization.
• I need the abuse contact for 1.0.0.0 and the network route involved.
• For this IP, show me the abuse contact details only: 198.51.100.27

Timezone lookups and conversions

• What time is it in Tokyo right now?
• Convert 2026-03-07 09:30 from New York to Tokyo time.
• What is the current local time at JFK airport?

Sunrise, sunset, and moon data

• Give sunrise and sunset for London on 2026-06-21.
• Show sunrise times in Karachi from 2026-03-10 to 2026-03-15.
• For New York, give me moon phase and day length on 2026-07-17.

Parse user-agent strings

• Parse this user agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10\_11\_2) AppleWebKit/601.3.9 (KHTML, like Gecko) Version/9.0.2 Safari/601.3.9
• Parse these user agents in bulk and tell me the browser, OS, and device type for each.
• Does this user agent look like a crawler or bot? Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.96 Mobile Safari/537.36 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)

Example Answers and Tool Output

The text answers below show what a client might say. Exact wording depends on the model. The JSON blocks show raw tool output, trimmed for readability.

Single IP lookup

Prompt: Locate 91.128.103.196 and give me the country, city, ASN, and local time.

Example answer: 91.128.103.196 is in Stockholm, Sweden. ASN is AS1257, operated by Tele2 Sverige AB. Timezone is Europe/Stockholm, local time was 2026-02-12 18:36:54.

{
  "ip": "91.128.103.196",
  "location": {
    "country_name": "Sweden",
    "state_prov": "Stockholms lan",
    "city": "Stockholm"
  },
  "asn": {
    "as_number": "AS1257",
    "organization": "Tele2 Sverige AB",
    "country": "SE"
  },
  "time_zone": {
    "name": "Europe/Stockholm",
    "current_time": "2026-02-12 18:36:54.401+0100"
  }
}

Time conversion

Prompt: Convert 2025-01-21 13:42:52 from DXB to LHR.

Example answer: 2025-01-21 13:42:52 in Dubai converts to 2025-01-21 09:42:52 in London. The difference is 4 hours.

{
  "original_time": "2025-01-21 13:42:52",
  "converted_time": "2025-01-21 09:42:52",
  "diff_hour": 4,
  "diff_min": 240
}

Abuse contact

Prompt: Give me the abuse contact for 1.0.0.0.

Example answer: The abuse contact for 1.0.0.0 is IRT-APNICRANDNET-AU in Australia, covering route 1.0.0.0/24. Email: helpdesk@apnic.net.

{
  "ip": "1.0.0.0",
  "abuse": {
    "route": "1.0.0.0/24",
    "country": "AU",
    "name": "IRT-APNICRANDNET-AU",
    "address": "PO Box 3646, South Brisbane, QLD 4101, Australia",
    "emails": ["helpdesk@apnic.net"]
  }
}

Error Codes

All tools return structured errors instead of crashing the server. API errors include the upstream status/message plus a `guidance` field so MCP clients can tell the user what to check next instead of only repeating the upstream response.

Exact status codes can vary by endpoint and request mode. If an upstream endpoint returns a status outside this table, the server does not guess the cause. It passes the upstream status and message through with `category: "undocumented_api_error"` and adds guidance for the MCP client to explain the response as an undocumented upstream status without inventing a cause.

How It Works

This is a stdio MCP server that wraps the ipgeolocation.io v3 APIs.

At runtime:

1. Your MCP client starts the server process.

2. The client reads the tool list.

3. When a prompt matches a tool, the client calls it.

4. The server validates inputs, calls our API, and returns structured JSON.

5. Cacheable responses are stored in process memory so repeated identical requests skip the API call.

Authenticated upstream requests send the API key in the `x-ipgeolocation-api-key` header. The key is not added to request URLs.

`lookup_company`, `lookup_currency`, and `lookup_network` are wrappers around parts of the full IP lookup response. They exist as separate tools so MCP clients can discover them when a user only needs one piece of data.

Caching

Tools that return stable data (not current-time lookups) cache their responses in process memory. Repeated lookups are faster and don't use additional credits. Client retries don't generate duplicate API calls.

• Process-level cache, not client or model memory
• Cache entries are scoped by API key, so separate MCP sessions do not share cached upstream data
• Default TTL: 5 minutes (`300000` ms)
• Cache resets when the server process stops
• Cache misses on TTL expiry, changed parameters, or `force_refresh: true`

Cached: `lookup_ip`, `bulk_lookup_ip`, `check_security`, `bulk_security_check`, `lookup_company`, `lookup_currency`, `lookup_network`, `parse_user_agent`, `bulk_parse_user_agent`, `lookup_asn`, `get_abuse_contact`, `get_astronomy_time_series`

Always live (not cached): `get_my_ip`, `get_timezone`, `convert_timezone`, `get_astronomy`

Environment Variables

Building from Source

git clone https://github.com/IPGeolocation/ipgeolocation-io-mcp.git
cd ipgeolocation-io-mcp
npm install
npm run build

Run it directly:

IPGEOLOCATION_API_KEY= node dist/cli.js

Inspect with MCP Inspector:

IPGEOLOCATION_API_KEY= npx @modelcontextprotocol/inspector node dist/cli.js

Docker

docker build -t ipgeolocation-mcp .
docker run -e IPGEOLOCATION_API_KEY= ipgeolocation-mcp

Testing

npm test               # full suite
npm run test:unit      # unit tests only
npm run test:integration  # integration tests only

Troubleshooting

Client uses an old tool after updating: Restart the client and confirm it loaded the latest npm version.

401 errors: Check that `IPGEOLOCATION_API_KEY` is set in your config. Some tools are paid-only and return 401 on the free plan. Domain lookups in `lookup_ip` also require a paid plan.

423 errors: You passed a private/bogon IP like `10.0.0.1` or `192.168.1.1`. These have no geolocation data.

504 timeouts: The upstream API did not respond in time. Increase the timeout with `IPGEOLOCATION_REQUEST_TIMEOUT_MS` (default: 15000 ms, max: 120000 ms).

Pricing

For current plan details, credits, and pricing, see the IPGeolocation pricing page.

Links

• IPGeolocation Website
• IPGeolocation API Documentation
• IPGeolocation Pricing
• Create a Free IPGeolocation API Key
• Changelog

License

MIT

Privacy Policy

Read the IPGeolocation Privacy Policy.