NsLookup.io

listing.by

Look up DNS records, check propagation, inspect SSL certificates, run security scans and test uptime from multiple locations.

state.ok.long (state.ok.title)Streamable HTTP

listing.connect

listing.explain.none

https://mcp.nslookup.io/mcp

listing.note.none listing.note.none_direct

listing.share.h

listing.share.p

mcp.tc/i/nslookup-io

listing.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.

listing.can

  • 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

listing.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.

listing.tools_more
  • 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.

listing.prov.live_on

listing.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?

listing.setup.h

listing.setup.remote

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http nslookup-io https://mcp.nslookup.io/mcp
  1. 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:
https://mcp.nslookup.io/mcp
  1. 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:
  1. Check that the URL reads https://mcp.nslookup.io/mcp and click Add.
  2. 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

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "nslookup-io": {
      "url": "https://mcp.nslookup.io/mcp"
    }
  }
}

VS Code

Or from a terminal:

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
{
  "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
{
  "mcpServers": {
    "nslookup-io": {
      "serverUrl": "https://mcp.nslookup.io/mcp"
    }
  }
}
  1. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.

Codex

codex mcp add nslookup-io --url https://mcp.nslookup.io/mcp

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.nslookup-io]
url = "https://mcp.nslookup.io/mcp"

Gemini CLI

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.

{
  "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.

listing.faq

Can I paste mcp.tc/i/nslookup-io into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://mcp.nslookup.io/mcp, so your client talks to NsLookup.io directly. The quick link is for sharing: it opens this page, with setup steps for every client.

Does NsLookup.io need an API key or a sign-in?

No. NsLookup.io doesn't ask for an account or key.

Is NsLookup.io a remote or a local server?

Remote. NsLookup.io hosts it at https://mcp.nslookup.io/mcp, and it speaks Streamable HTTP. There's nothing to install.

What can NsLookup.io do?

It has 23 tools, including dns_lookup, dns_record and dns_propagation. You can look up any of 53 DNS record types for a domain, check DNS propagation across 18+ global servers and inspect SSL/TLS certificates and expiry.

Which clients can use it?

Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT in developer mode, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.

Who wrote this page?

mcp.tc's robot read NsLookup.io's own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can't confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

listing.em.h

listing.em.lead listing.em.how

listing.em.badge

em.prev_lightem.prev_dark
Markdown
[![NsLookup.io on mcp.tc](https://mcp.tc/i/nslookup-io/badge.svg)](https://mcp.tc/i/nslookup-io)
HTML
<a href="https://mcp.tc/i/nslookup-io"><img src="https://mcp.tc/i/nslookup-io/badge.svg" alt="NsLookup.io on mcp.tc" height="20"></a>

listing.em.badge_note

listing.em.widget

HTML
<script src="https://mcp.tc/w/nslookup-io.js" async></script>

listing.em.widget_note

iframe

HTML
<iframe src="https://mcp.tc/embed/nslookup-io" title="NsLookup.io on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

listing.em.iframe_note

JSON

listing.em.json

https://mcp.tc/i/nslookup-io.json

listing.em.fields

listing.disclaimer_checked