Classify whether an IP is a known residential-proxy exit node.

Returns ResidentialProxyDetails with is_residential_proxy (the canonical yes/no), and — when true — service, last_seen (YYYY-MM-DD), and percent_days_seen over a 7-day window. Useful for fraud, bot, and ad-fraud detection. This is distinct from the general privacy flags on ipinfo_lookup_ips (VPN / Tor / open web proxy / hosting): use this tool only to detect residential-proxy networks that route traffic through real residential IPs. Requires IPINFO_API_TOKEN with the Enterprise residential-proxy add-on; absence surfaces as auth_insufficient_scope (distinct from auth_invalid for a missing/wrong token).

Build an interactive ipinfo.io map for a set of IPs.

Returns MapResult{url, mapped_ip_count, skipped_ips, skipped_count, truncated}. skipped_ips is a list of {ip, reason} entries for filtered inputs, capped at 100; truncated flags overflow. skipped_count is the true total even when the list is capped, so mapped_ip_count + skipped_count equals the input length. Errors raise ToolError with a JSON-encoded envelope.

Geolocate one or more IPs and return ISP/ASN details.

Returns a list in input order (after dedup and invalid-IP filtering); match results back to your input via the ip field. IPs that fail upstream are omitted and logged; if the batch resolves no IPs at all the failure is raised rather than masked — auth_insufficient_scope when the upstream returned nothing (token tier likely lacks /batch access; look IPs up one at a time or upgrade to Core+), otherwise a retryable api_error. Defaults to detail="summary" (heavy nested blocks omitted); pass detail="full" for every field. Capped at 1,000 IPs per call (too_many_ips above that): this tool returns one record per IP, so for larger batches use ipinfo_summarize_ips (fixed-size aggregates) or ipinfo_generate_map_url. Higher plan tiers populate more fields; see the server instructions for the Lite/Core/Plus/Enterprise tier mapping. For VPN/Tor/open-proxy/hosting detection read the privacy flags on each record; for residential-proxy exit-node classification use the separate ipinfo_check_residential_proxy tool. Typically completes in seconds; bounded by a 120s tool timeout that surfaces as a timeout envelope. Errors raise ToolError with a JSON-encoded envelope.

Geolocate the calling client's own IP. No arguments.

On stdio transports the result is this server's outbound IP, not the end user's. Use ipinfo_lookup_ips when the caller already has a specific IP. Errors raise ToolError with a JSON-encoded envelope.

Aggregate one or more IP lookups into counts and percentages.

Uses the same validation, deduplication, cache, and upstream batch lookup path as ipinfo_lookup_ips, but returns fixed-size summary buckets instead of per-IP records. This is the preferred tool for large log-analysis tasks such as "where did visitors come from?" when the caller does not need the underlying records. Percentages are based on mapped_ip_count; filtered and failed IPs are counted separately. Errors raise ToolError with a JSON-encoded envelope.