IPGeolocation MCP Server
Related Servers
Alternatives to IPGeolocation MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceOfficial parseAPI MCP server providing IP/place data, email/phone/domain validation, weather, currency, timezone, and holiday lookups as tools for AI agents.32245 npmMIT
- AlicenseAqualityBmaintenanceIP Geolocation MCP server using IP2Location.io API to ease the query of geolocation information.118PythonMIT
- FlicenseAqualityDmaintenanceProvides IP address geolocation and related info via an API, with MCP server integration for easy use in AI tools.1-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides IP geolocation services using MaxMind's GeoIP2 databases, allowing users to retrieve geographical information for single or multiple IP addresses including country, city, coordinates, and ASN details.GPL 3.0
- AlicenseNot gradedqualityDmaintenanceMCP server providing IP address lookup capabilities. Enables AI assistants to fetch details about public IP addresses or the user's current device IP.ISC
- AlicenseNot gradedqualityFmaintenanceMCP server for IP geolocation lookups using ipinfo.io, with single, own, and batch queries.1MIT
TDQS
Scored across 17 tools
The six ipgeo-derived lookups (lookup_ip, lookup_company, lookup_currency, lookup_network, check_security, lookup_asn) all return overlapping slices of the same underlying data, and an agent could reasonably satisfy a request with either the dedicated tool or lookup_ip with an include token. The descriptions do explicitly flag this ('this response is limited to X; lookup_ip can return these together with...') and the single-vs-bulk and single-date-vs-range pairs (parse_user_agent/bulk_parse_user_agent, get_astronomy/get_astronomy_time_series, get_timezone/convert_timezone) are cleanly delineated, which keeps it readable but still overlapping.
All names are snake_case verb_noun, which is readable, but the verb choice is inconsistent for the same operation class: lookup_asn/lookup_network vs check_security vs get_abuse_contact all fetch a per-IP data slice. The bulk_ prefix is also applied inconsistently (bulk_lookup_ip, bulk_security_check, bulk_parse_user_agent) rather than as a parameter or suffix convention.
17 tools is slightly above the comfortable band but justified by the breadth of the upstream API (IP, bulk, ASN, security, abuse, UA, timezone, astronomy) plus the required pagination tool get_cached_result. Each tool maps to a real endpoint or capability, though the dedicated thin wrappers around ipgeo arguably duplicate lookup_ip.
Coverage is broad: single and bulk lookup, security, abuse, ASN/WHOIS, UA parsing, timezone and conversion, astronomy single and series, caching, and egress IP. The main gap is account/plan awareness — a credit-metered API with no tool to check remaining credits or plan entitlements, which agents will need to reason about paid-only endpoints and 401s.