# NsLookup.io MCP server > Look up DNS records, check propagation, inspect SSL certificates, run security scans and test uptime from multiple locations. - Listing: https://mcp.tc/i/nslookup-io - Connect: use the server's own URL `https://mcp.nslookup.io/mcp` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint. - Type: remote (Streamable HTTP) - Auth: none - Category: [Cloud & DevOps](https://mcp.tc/c/cloud-devops) - Vendor: NsLookup.io - Homepage: - Repository: - Package: npm `@nslookup-io/mcp-server` ## About Connects an assistant to nslookup.io for DNS and domain intelligence. It can look up 53 DNS record types, check propagation across 18+ global DNS servers, inspect SSL/TLS certificates, verify BIMI/VMC records, audit DNS health, scan SPF/DKIM/DMARC and web security, run RDAP lookups, identify hosting providers, and test website availability from 7 locations. It can also review proposed DNS changes before they are applied. The hosted endpoint is a Streamable HTTP server. The 17 public tools work with no sign-in or API key. Six my\_ tools read your own NsLookup.io monitoring account (monitors, incidents, uptime history, DNS changes, certificate expiry) and need a browser OAuth sign-in. A local npx package offers the public tools only. ## What it can do - Look up any of 53 DNS record types for a domain - Check DNS propagation across 18+ global servers - Inspect SSL/TLS certificates and expiry - Audit DNS health and email security (SPF, DKIM, DMARC, BIMI) - Check site uptime from 7 locations worldwide - Review proposed DNS changes with a risk score before applying - Run RDAP lookups and find a site's hosting provider - Read your own NsLookup.io monitors and incidents after sign-in ## Tools (23) - `dns_lookup`: Look up common DNS records (A, AAAA, NS, MX, TXT, CNAME, SOA) for a domain. - `dns_record`: Look up a specific DNS record type; supports 53 types. - `dns_propagation`: Check DNS propagation across 18+ global DNS servers. - `webservers`: Get IPv4 and IPv6 addresses for a domain plus punycode and unicode forms. - `ssl_certificate`: Check a domain's SSL/TLS certificate, chain, expiry, and protocol details. - `bimi_vmc`: Check BIMI record and Verified Mark Certificate details for a domain. - `security_scan`: Scan a domain for DNS, email, cookie and web security issues with severity levels. - `uptime_check`: One-time HTTP uptime check of a URL from a single location. - `uptime_check_multi`: Check a URL's availability from 7 global locations at once. - `dns_health`: Run a 39-check DNS health audit with an overall and per-category score. - `geo_checker`: Score how well a site is optimized for AI search engines. - `rdap_lookup`: Registration data (RDAP) for an IP, AS number, or domain. - `hosting_report`: Report hosting provider, network owner, CDN, nameservers and mail provider for a site. - `domain_scanner`: Scan a domain's SPF, DKIM, DMARC and BIMI posture with scores and issues. - `dns_change_review`: Diff current DNS against proposed records and return findings and a 0-100 risk score. - `bimi_check`: Quickly check only the BIMI DNS record for a domain. - `status_page`: Read a status page hosted on nslookup.io by slug or custom domain. - `my_overview`: Account health snapshot with score, subsystem breakdown and quota (sign-in required). - `my_monitors`: List all monitors in your account with configuration and latest state. - `my_incidents`: List open or recent incidents from your monitoring with a summary. - `my_uptime_history`: Uptime and response-time history for one of your uptime monitors. - `my_dns_changes`: Recent DNS changes on your monitored domains with risk assessments. - `my_certificates`: SSL certificate expiry overview for your monitored domains. ## Example prompts - "Run a DNS health check on example.com" - "Has the DNS change for example.com propagated worldwide?" - "When does the SSL certificate for example.com expire?" - "Is example.com up from all locations right now?" ## Install ### Claude Code 1. Run this in a terminal, in your project folder: ```bash claude mcp add --transport http nslookup-io https://mcp.nslookup.io/mcp ``` 2. Start Claude Code and type `/mcp`. **nslookup-io** should show as connected. Add `--scope user` to make it available in every project, not just this one. ### Claude Desktop 1. Open **Settings → Connectors** and click **Add custom connector**. 2. Name it **NsLookup.io** and paste this URL: ```url https://mcp.nslookup.io/mcp ``` 3. Click **Add**. Its tools appear in the chat’s tools menu. Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too. ### claude.ai 1. Open the connector form on claude.ai. This button fills in the name and URL for you: [Add to claude.ai]() (opens connector settings) 2. Check that the URL reads `https://mcp.nslookup.io/mcp` and click **Add**. 3. Turn it on in a chat from the tools menu. Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**. ### ChatGPT 1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**. 2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server. 3. Paste `https://mcp.nslookup.io/mcp` as the server URL and choose **No authentication**. Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts. ### Cursor [Add to Cursor]() (opens Cursor) Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project): `mcp.json`: ```json { "mcpServers": { "nslookup-io": { "url": "https://mcp.nslookup.io/mcp" } } } ``` ### VS Code [Install in VS Code]() (opens VS Code) Or from a terminal: ```bash code --add-mcp '{"name":"nslookup-io","type":"http","url":"https://mcp.nslookup.io/mcp"}' ``` Or commit it to the repo in `.vscode/mcp.json`: `.vscode/mcp.json`: ```json { "servers": { "nslookup-io": { "type": "http", "url": "https://mcp.nslookup.io/mcp" } } } ``` ### Devin Desktop 1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows): `mcp_config.json`: ```json { "mcpServers": { "nslookup-io": { "serverUrl": "https://mcp.nslookup.io/mcp" } } } ``` 2. Refresh the MCP server list in Cascade. Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers. ### Codex ```bash codex mcp add nslookup-io --url https://mcp.nslookup.io/mcp ``` Or edit `~/.codex/config.toml` directly: `config.toml`: ```toml [mcp_servers.nslookup-io] url = "https://mcp.nslookup.io/mcp" ``` ### Gemini CLI ```bash gemini mcp add --transport http nslookup-io https://mcp.nslookup.io/mcp ``` This adds it to the current project. Add `-s user` to use it everywhere. ### Any client Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file. ```json { "mcpServers": { "nslookup-io": { "type": "http", "url": "https://mcp.nslookup.io/mcp" } } } ``` Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE. Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.nslookup.io/mcp`. ## Details - Server version: 1.6.0 - MCP protocol version: 2025-11-25 - Last checked: 2026-10-04 (reachable) - Listed: 2026-10-04 - Updated: 2026-10-04 --- Source: https://mcp.tc/i/nslookup-io (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report