mcp-ip2location
Related Servers
Alternatives to mcp-ip2location
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to query IP intelligence tools such as geolocation, VPN/security checks, ASN, timezone, astronomy, user-agent parsing, abuse contacts, and bulk lookups via natural language.19 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides IP geolocation data via ipinfo.io, enabling querying IP addresses for location, ISP, and other details through natural language.5 npmMIT
- AlicenseAqualityDmaintenanceProvides GeoIP and ASN intelligence lookup for IP addresses, enabling AI agents to retrieve location and network information via the IPRout API.2MIT
- AlicenseNot gradedqualityAmaintenanceEnables LLMs to query IP addresses against free MaxMind GeoLite2 geolocation databases.MIT
- AlicenseNot gradedqualityDmaintenanceEnables IP address intelligence lookup including geolocation, network information, privacy detection (VPN/proxy/Tor), company data, and abuse contacts using IPLocate.io API. Supports both IPv4 and IPv6 addresses with comprehensive analysis tools and security assessment capabilities.322 npmMIT

@whoisjson/mcp-serverofficial
AlicenseAqualityDmaintenanceEnables AI assistants to perform WHOIS, DNS, SSL, and domain availability lookups via the WhoisJSON API.421 npmMIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: single IP geolocation, bulk geolocation, proxy detection, domain WHOIS, and reverse IP lookup. The overlap between ip_geolocation and bulk_geolocate is resolved by the batch vs. single distinction, so no ambiguity exists.
Tool names follow mixed conventions: 'ip_geolocation' is a noun phrase, 'proxy_check' and 'whois_lookup' are object-verb, 'bulk_geolocate' is modifier-verb, and 'hosted_domains' is a noun phrase. There is no consistent verb_noun or resource_action pattern, making the naming unpredictable.
With 5 tools, the server is well-scoped for an IP intelligence service. Each tool provides a distinct and necessary capability without unnecessary redundancy, and the count is within the ideal 3-15 range.
The tool surface covers the primary IP lookup domain: geolocation, proxy detection, bulk geolocation, WHOIS for domains, and reverse IP. Minor gaps exist, such as no direct domain-to-IP resolution or standalone ASN lookup, but these can be worked around with existing tools.