Nslookup

What nslookup MCP server does

The nslookup MCP server exposes nslookup.io capabilities through the Model Context Protocol. Its public tools cover DNS records, propagation, web server addresses, DNS change reviews, RDAP registration data, hosting details, public status pages, DNS health, SSL/TLS certificates, BIMI and VMC, email security, uptime, and GEO scoring.

It also provides six account-oriented tools for authenticated nslookup.io monitoring data: an account overview, monitor listings, incidents, uptime history, DNS changes, and certificate expiry information. These tools read data from the connected nslookup.io account rather than performing anonymous domain lookups.

How it works

Two connection modes are available. The hosted endpoint at https://mcp.nslookup.io/mcp uses Streamable HTTP and can provide both anonymous public tools and authenticated account tools. The local npm package runs through stdio with npx -y @nslookup-io/mcp-server and provides the public tools only.

The public operations use nslookup.io's stateless, no-auth endpoints. Account operations require browser-based OAuth sign-in when using the hosted connection; there is no API key. After sign-in, the client can reuse the authenticated session. The server includes tools for all common DNS records and specific queries across 53 DNS record types, plus propagation checks against more than 18 global servers.

Setup and configuration

For the hosted nslookup MCP server, add https://mcp.nslookup.io/mcp as an HTTP MCP connection. Claude Code can add it with claude mcp add --transport http nslookup https://mcp.nslookup.io/mcp; other HTTP-capable clients can use an MCP configuration with type set to http and the same URL.

For local use, install nothing permanently and run the package through Node.js 18 or newer:

{
  "mcpServers": {
    "nslookup": {
      "command": "npx",
      "args": ["-y", "@nslookup-io/mcp-server"]
    }
  }
}

Configure only one connection entry named nslookup. Registering both hosted and local entries can route calls to the wrong server. Choose the hosted mode when access to personal monitoring data is required.

Tools and capabilities

• Query common DNS records with dns_lookup, or request a particular type with dns_record.
• Compare DNS visibility across global resolvers with dns_propagation.
• Review proposed DNS changes with current-state diffs, findings, suggested fixes, and a 0–100 risk score.
• Inspect ownership, hosting, CDN or proxy details, mail servers, server location, and public status pages.
• Audit DNS, SSL/TLS, email authentication, BIMI, VMC, cookies, and related security settings.
• Check uptime from one location or seven global locations, and inspect GEO factors such as crawler access and structured data.
• Read authenticated monitor, incident, history, DNS-change, and certificate data through the my_ tools.

Limitations and notes

The local transport cannot access the six my_ account tools. Those tools require the hosted endpoint and browser OAuth. Public tools do not require an account or API key. The README names Claude Desktop, Claude Code, Cursor, and Windsurf as connection targets; configuration details depend on whether the client supports HTTP MCP connections, stdio, or both.