Who owns an IP address?
Scored across 2 tools
lookup_ip already includes reverse DNS (PTR) data alongside RDAP, while reverse_dns_lookup is essentially a PTR-only subset. The descriptions clarify the intended split, but an agent could reasonably choose either tool for a simple PTR query, creating a fuzzy boundary.
Both names use snake_case, but the patterns differ: lookup_ip is verb_noun while reverse_dns_lookup is adjective_noun_verb. Readable and related, but not a predictable shared convention.
Two tools is on the thin side for an IP intelligence server, though neither is redundant and each has a distinct core function. The surface is borderline minimal rather than well-scoped.
The set covers registry ownership, abuse contact, ranges, reverse DNS, and batch CSV output for both IPv4 and IPv6. Minor gaps exist—no dedicated single-address structured detail tool or historical registration data—but core IP lookup workflows are covered.
Use this when the user wants an ip lookup, asks who owns this ip, needs the ip address owner or the whois ip details, wants the ip abuse contact, or needs an ip range lookup: it reads the five regional internet registries through RDAP and the reverse DNS (PTR) name, for one to twenty IPv4 or IPv6 addresses or CIDR ranges, and returns a CSV download for the batch. Limits: registry data shows the network holder and its country, not a street address or a person's location; some registries publish no abuse email; reverse DNS exists only when the network sets it. Do not use for an ip locator that claims a precise location, for looking up a domain name (that is a domain lookup), or for scanning a host.
Inputs: ips (required). Returns: count, notes, columns, sources, +6 more
Use this when the user wants a reverse dns lookup, an ip address lookup for PTR names, or a quick ip lookup of hostnames: it queries DNS-over-HTTPS for the in-addr.arpa or ip6.arpa name of one to twenty public IPv4 or IPv6 addresses and returns host names with a CSV download, without reading a registry. Limits: a PTR name exists only when the network operator sets it; private, loopback, link-local, shared, multicast, documentation and reserved addresses are not queried. Do not use when the user wants the owner, the registration dates or the abuse contact of an address (use lookup_ip for that).
Inputs: ips (required). Returns: count, notes, records, sources, +4 more
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
IP geolocation: country, continent, ASN and ISP lookup
IP address utilities MCP.
One routable IPv6 per AI agent, verifiable from the DNS root. Keyless tools need no signup.
Open-source IP address and CIDR tools for network calculations and public IP lookup.
Add one secure layer between your agents and this server.
