Nmap Online MCP. Audit ports, map networks, and find hidden domains.

You're trying to run a proper network audit, but you gotta jump between terminals, web dashboards, and ten different tools? Forget that headache. This server puts professional-grade diagnostics right where your agent is—in the chat window. You don’t need to switch anything; you just talk to it.

This setup exposes everything you need for deep reconnaissance: port scanning, domain mapping, IP tracking, and web scraping. It's built so you can map out an entire attack surface without ever leaving your current view.

Auditing Service Surfaces

Need to know what services are running? You can run a basic Nmap scan using nmap_scan against any target IP or host, which identifies open and closed ports. This tells you exactly what service surface is exposed for exploitation. If you want to verify the core identity of that machine, ping_host sends ICMP packets to test connectivity and measure latency.

For a more granular view of web content, you can use get_http_headers to pull the raw HTTP response headers from any target URL. You'll also find that if you need to map out all the internal links on a page for thorough content mapping, get_page_links scrapes and extracts every single clickable link from the webpage.

Domain and IP Resolution

Verifying who owns an address or domain is straightforward. You can check official registration details—the ownership and when it was registered—using whois_lookup. If you're dealing with a specific name, running dns_lookup performs a forward DNS lookup to get the associated IP address. Conversely, if you only have an IP address but need to know what domain might belong there, reverse_dns runs a reverse lookup to map that IP back to a potential domain name.

To dig deeper into naming conventions, list_subdomains searches for other subdomains tied to a root domain.

Network Pathing and Geography

Mapping network topology is critical. You can trace the entire path taken when reaching a destination host across multiple routers using traceroute, which shows you every hop in the journey. To check basic connectivity and measure lag, use ping_host. For understanding physical location, geoip_lookup determines the geographical area—the city, country, and ISP—associated with any given IP address.

This helps pinpoint where a server actually lives.

Putting It Together

You can combine these functions to build a profile from nothing. You run whois_lookup to see who registered 'example.com'. Then, you use dns_lookup to get its primary IP. Next, you hit it with geoip_lookup to figure out the physical region of that IP. You'll then run nmap_scan against that IP to check for open ports.

If there’s a path issue, you can confirm connectivity using ping_host, or trace the route entirely with traceroute. This stack lets your agent handle all the complex diagnostics—the name resolution, the port scanning, the geolocation lookup, and the link scraping—all in one place.