# nslookup [Health: Active]

**Category:** 📊 Monitoring  
**Repository:** https://github.com/NsLookup-io/nslookup-mcp  
**GitHub Stars:** 23  
**npm Downloads (last month):** 267  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/nslookup

## Description
DNS lookups, SSL certificates, security scanning, and propagation checks via nslookup.io

## Tools
Capabilities this server exposes over MCP:

- **dns_lookup** — Look up all common DNS records (A, AAAA, NS, MX, TXT, CNAME, SOA) for a domain. Returns results from a specified DNS server.
- **dns_record** — Look up a specific DNS record type for a domain. Supports 53 record types including A, AAAA, MX, TXT, CNAME, SOA, PTR, CAA, SRV, DNSKEY, DS, TLSA, HTTPS, SPF, and more.
- **dns_propagation** — Check DNS propagation for a domain across 18+ global DNS servers (Cloudflare, Google, Quad9, OpenDNS, regional servers, and authoritative nameservers). Shows if DNS changes have propagated worldwide.
- **webservers** — Get the IP addresses (both IPv4 and IPv6) for a domain by looking up A and AAAA records. Also returns the punycode and unicode domain representations.
- **ssl_certificate** — Check the SSL/TLS certificate for a domain. Returns issuer, expiry date, days until expiry, certificate chain validity, cipher strength, SAN domains, fingerprint, and TLS protocol version.
- **bimi_vmc** — Check BIMI (Brand Indicators for Message Identification) and VMC (Verified Mark Certificate) for a domain. Returns BIMI DNS record status, VMC certificate details, logo URL, trademark info, and expiry.
- **security_scan** — Run a security scan on a domain to detect DNS misconfigurations, missing SPF/DKIM/DMARC records, cookie security issues, and other web security vulnerabilities. Returns findings with severity levels (critical, high, medium, low, info).
- **uptime_check** — Perform a one-time HTTP uptime check on a URL from a single location. Returns whether the site is up or down, HTTP status code, and response time in milliseconds. For multi-location checks, use uptime_check_multi instead.
- **uptime_check_multi** — Check if a website is up or down from 7 global locations simultaneously: Amsterdam, Sydney, London, Frankfurt, Delhi, Warsaw, and South Carolina. Returns status, response time, and HTTP status code for each location.
- **dns_health** — Run a comprehensive DNS health audit on a domain — 39 checks across 7 categories: DNSSEC (chain of trust, algorithms, validation), MX & email (PTR, MTA-STS, redundancy), DNS hygiene (SPF conflicts, wildcards, apex CNAME), TTL & SOA configuration, nameserver setup (diversity, lame delegation, EDNS0), CAA certificates, and operational maturity (security.txt, abuse mailbox). Returns an overall severity-weighted score (0–100) plus per-category scores.
- **geo_checker** — Check a domain's GEO (Generative Engine Optimization) score — how well the site is optimized for AI search engines like ChatGPT, Gemini, Claude, and Perplexity. Returns three scores (Technical Readiness, Entity Readiness, Answer Readiness), AI crawler access status, structured data analysis, and prioritized recommendations.
- **rdap_lookup** — Look up registration data (RDAP — the successor to WHOIS) for an IP address, AS number, or domain name. The query type is detected automatically. Returns the owning organization, network range/CIDR, RIR (ARIN, RIPE, APNIC, LACNIC, AFRINIC), country, status, registration/last-changed dates, nameservers, and abuse/registrant contacts, plus the raw RDAP JSON.
- **hosting_report** — Find out who hosts a website. Returns the hosting provider, IP/ASN/network owner, server location, DNS/nameserver provider, CDN or proxy detection (Cloudflare, Fastly, etc.), SSL certificate issuer, and mail servers/provider for a domain in one combined report.
- **domain_scanner** — Scan a domain's email security posture: SPF, DKIM, DMARC, and BIMI configuration. Returns per-indicator scores and detected issues so you can see how well the domain is protected against spoofing and phishing.
- **dns_change_review** — Review proposed DNS changes BEFORE applying them. Compares a domain's current public DNS with a proposed future state, returns a diff, deterministic rule-based findings (SPF/DMARC/MX/CAA/DNSSEC pitfalls, dangling records, mail breakage, etc.) with suggested fixes, and an overall 0-100 risk score. Stateless — nothing is stored.
- **bimi_check** — Check only the BIMI (Brand Indicators for Message Identification) DNS record for a domain — faster than bimi_vmc because it skips the VMC certificate download and validation. Returns the BIMI record at default._bimi.<domain>, logo URL, and authority (VMC) URL if declared.
- **status_page** — Read a public status page hosted on nslookup.io status pages. Returns the page name, overall status, per-component status and uptime, and active incidents/maintenance. Look up by slug (pages served at hosted.nslookup.io/<slug>) or by the custom domain the page is served on. Provide exactly one of slug or domain.
- **my_overview** — Get an account health snapshot for your NsLookup.io monitoring: an aggregated 0-100 health score with per-subsystem breakdown (uptime, SSL, DNS, propagation, VMC, WHOIS) plus your current product limits/quota. Requires sign-in to your NsLookup.io account (or an API token).
- **my_monitors** — List all monitors in your NsLookup.io account across every type — uptime, API, DNS, WHOIS, DNS propagation, SSL certificates, and BIMI/VMC — with their configuration and latest known state. Requires sign-in to your NsLookup.io account (or an API token).
- **my_incidents** — List incidents from your NsLookup.io monitoring (downtime, SSL expiry, DNS changes, propagation issues, VMC problems) — open ones by default, or the full recent history — plus a per-status/per-source summary. Requires sign-in to your NsLookup.io account (or an API token).
- **my_uptime_history** — Get uptime and response-time history for one of your NsLookup.io uptime monitors: availability stats plus hourly buckets over the requested window. Identify the monitor by id or by URL. Requires sign-in to your NsLookup.io account (or an API token).
- **my_dns_changes** — List recent DNS changes detected on your monitored domains, each with its DNS Change Review risk assessment (0-100 risk score, severity counts, added/removed/modified record counts), plus the latest risk per monitor. Requires sign-in to your NsLookup.io account (or an API token).
- **my_certificates** — Get an SSL certificate expiry overview for your monitored domains: per-alert-level counts (ok / warning / critical / expired) and every certificate sorted by soonest expiry, highlighting the ones expiring within 30 days. Requires sign-in to your NsLookup.io account (or an API token).

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

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

## Documentation

## 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:

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

_Full upstream README: https://allmcps.com/mcp/nslookup/readme_