mcp-ip2location
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IP2LOCATION_API_KEY | Yes | API key from IP2Location.io. Required to authenticate requests for all tools (IP geolocation, proxy check, WHOIS, bulk lookup, hosted domains). Get a free key at https://www.ip2location.io. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ip_geolocationA | Look up the geographic location of an IPv4 or IPv6 address: country, region, city, coordinates, timezone, ASN and network operator. Use this when the user asks where an IP address is located or who operates it. |
| proxy_checkA | Check whether an IP address is a known proxy, VPN, or anonymizer exit. Use this to assess whether traffic from an IP can be trusted, e.g. for fraud triage or log investigation. |
| whois_lookupA | Fetch WHOIS registration data for a domain: creation/expiry dates, registrar, nameservers and registrant. Use this to judge how old or trustworthy a domain is, e.g. when vetting a sender or website. |
| bulk_geolocateA | Geolocate up to 50 IP addresses in a single request and return a compact table. Useful for analyzing a list of IPs from a log file. |
| hosted_domainsA | List domain names hosted on a given IP address (reverse-IP lookup). Use this to find other sites sharing the same server, e.g. when investigating a suspicious host or mapping an organisation's footprint. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct information need: IP geolocation, proxy/VPN detection, domain WHOIS, bulk geolocation, and reverse-IP domain lookup. The only near-overlap is ip_geolocation and bulk_geolocate, but the singular/bulk distinction in their descriptions makes them unambiguous.
All tool names use lower_snake_case and are descriptive, but they mix patterns: noun+noun (ip_geolocation, hosted_domains), noun+verb (proxy_check), and adjective+verb (bulk_geolocate). This is a minor deviation from a strict verb_noun convention, though still readable and predictable.
Five tools is well-scoped for an IP intelligence server. Each tool adds a distinct capability without unnecessary overlap, and the count feels neither thin nor heavy.
The set covers the core IP intelligence workflow: single and bulk geolocation, proxy detection, domain WHOIS, and reverse-IP domain listing. A notable minor gap is the lack of an IP-specific WHOIS endpoint or DNS resolution, but these are secondary and don't create dead ends.