Skip to main content
Glama
carlslee95

mcp-ip2location

by carlslee95
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-ip2location

No user-submitted related servers found.

    Related Servers

    • ip-info-mcp

      yuwan0405
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables IP address information lookup through natural language, including current public IP, geolocation, ISP, coordinates, and IPv4/IPv6 details via MCP stdio.
      -

    • Netdetective MCP Server

      BACH-AI-Tools
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that provides access to the Netdetective API for querying information about IP addresses. It enables users to retrieve metadata for a specified IP address or the connecting client's default IP address.
      1
      MIT

    • personal-mcp-server

      jango-blockchained
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server providing IP address lookup capabilities. Enables AI assistants to fetch details about public IP addresses or the user's current device IP.
      103 npm
      ISC

    • @ipgeolocationapi/mcp

      thebigasif
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      39 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources