IPGeolocation MCP Server
Related Servers
Alternatives to IPGeolocation MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceOfficial parseAPI MCP server providing IP/place data, email/phone/domain validation, weather, currency, timezone, and holiday lookups as tools for AI agents.321,168 npmMIT
- AlicenseAqualityCmaintenanceIP Geolocation MCP server using IP2Location.io API to ease the query of geolocation information.116PythonMIT
- 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.45 npmISC
- AlicenseNot gradedqualityFmaintenanceMCP server for IP geolocation lookups using ipinfo.io, with single, own, and batch queries.1MIT
TDQS
Scored across 17 tools
Each dedicated tool (company, currency, network, security, abuse, ASN) overlaps in data with the unified lookup_ip, which is a genuine source of confusion, but every description explicitly states the tradeoff ("this response is limited to X; lookup_ip can return these together with..."). Bulk variants are likewise cross-referenced against bulk_lookup_ip, and the timezone/astronomy singletons vs series/conversion pairs are clearly separated.
All names follow a verb_noun shape with a consistent `bulk_` prefix for batch variants (bulk_lookup_ip, bulk_security_check, bulk_parse_user_agent). The only inconsistency is verb choice for synonymous single-domain reads — lookup_company/lookup_asn vs get_abuse_contact vs check_security — which is readable but not perfectly predictable.
17 tools is slightly above the ideal band, but each maps to a distinct upstream endpoint or a distinct batch/cache primitive, so nothing feels padded. The set stays under the 25-tool red flag and the count is driven by the API's breadth (geo, timezone, astronomy, ASN, security, UA, bulk).
The surface covers the full lifecycle: single and bulk IP lookup, per-domain read tools, security and abuse, timezone get+convert, astronomy single+range, user-agent parse+bulk, plus get_my_ip and a zero-credit get_cached_result for pagination continuity. No dead ends — oversized bulk responses have a documented retrieval path.