nslookup MCP Server

Use This MCP server To

Run a DNS health check on any domain Find when my SSL certificates expire Check DNS propagation status after changes Get security and GEO readiness scores for a domain View my personal domain monitoring dashboard Look up detailed DNS record types Scan domains for security issues

README

MCP Server for nslookup.io
DNS lookups, SSL certificate checks, security scanning, GEO (AI readiness) scoring, domain intelligence, and your own monitoring account — via the Model Context Protocol.

Website · API Docs · npm · Contact

What is this?

The nslookup.io MCP server gives any MCP-capable AI assistant (Claude, ChatGPT, Cursor, Windsurf, …) direct access to nslookup.io's DNS, certificate, security, and monitoring tools. Ask in plain language — "Run a DNS health check on github.com" or "Which of my SSL certificates expire soonest?" — and the assistant calls the right tool for you.

23 tools total, in two groups:

17 public tools — DNS, SSL, security, GEO, and domain-intelligence lookups that work anonymously, with no account and no API key.
6 my_ account tools — read your own nslookup.io monitoring account (uptime, DNS, WHOIS, SSL, propagation, BIMI/VMC monitors). These are always listed but require signing in.

Jump to Connect to get set up, or the Tool reference for the full list.

Connect

There are two ways to connect. Pick one — see the note below.

	Hosted (recommended)	Local (npx / stdio)
Endpoint	`https://mcp.nslookup.io/mcp`	`npx -y @nslookup-io/mcp-server`
Transport	Streamable HTTP (remote)	stdio (runs on your machine)
Install	Nothing to install	Requires Node.js 18+
17 public tools	✅ Anonymous	✅ Anonymous
6 `my_` account tools	✅ Browser sign-in (OAuth) on first use	❌ Not available locally — use the hosted connector

Use the hosted endpoint if you want your own monitoring data — it's the only mode where the my_ account tools sign in for you, right in the browser. The local mode is great for the 17 public tools with zero setup.

Connect for your account (portal) tools

To use your own NsLookup.io monitoring data (the 6 my_ account tools), add the hosted connector and sign in. There is no API key — authentication is a one-time browser sign-in (OAuth) against your nslookup.io account.

Claude Code (CLI)

claude mcp add --transport http nslookup https://mcp.nslookup.io/mcp

Then invoke an account tool — e.g. ask "show my monitoring overview". A browser sign-in window appears; after you sign in once, all 6 my_ tools work (the client remembers it).

Claude Desktop / claude.ai — add a custom connector with URL https://mcp.nslookup.io/mcp, then sign in when prompted.

.mcp.json (project) or any HTTP-capable client:

{ "mcpServers": { "nslookup": { "type": "http", "url": "https://mcp.nslookup.io/mcp" } } }

The 17 public tools work immediately over this same endpoint — you only sign in the first time you reach for your own data.

nslookup-mcp FAQ

Can I use this to check DNS records for any website?

Yes — you can anonymously look up all common DNS records for any domain without an account.

Can I monitor my own SSL certificates and DNS status?

Yes — by signing into your nslookup.io account through the hosted connector, you can access your personal monitoring data.

Which AI assistants support this server?

It works with Claude.ai, Claude Desktop, ChatGPT, Cursor, Windsurf, and any MCP-capable client that supports HTTP connectors.

Do I need an API key to use this server?

No API key is needed; public tools work anonymously, and account tools require only a one-time browser sign-in.

How hard is it to set up?

Setup is copy-paste-config — you add a URL or a small config snippet to your AI assistant's MCP settings.

Can I use this server locally on my machine?

Yes — the local mode supports all public tools without sign-in but not your personal monitoring data.

Can I use both hosted and local modes at the same time?

No — you should configure either hosted or local mode to avoid conflicts.