DNS lookups, health reports, SSL certs, security scans, GEO scoring, uptime checks
MCPpedia last refreshed this data
io.github.venomseven/nslookup is an MCP server that DNS lookups, health reports, SSL certs, security scans, GEO scoring, uptime checks. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 60/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"nslookup": {
"args": [
"-y",
"@nslookup-io/mcp-server"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
DNS lookups, SSL certificate checks, security scanning, GEO (AI readiness) scoring, and domain intelligence — via the Model Context Protocol.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@nslookup-io/mcp-server' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @nslookup-io/mcp-server against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in security / devops
MCP server for using the GitLab API
MCP server for Komodo - manage Docker containers, servers, stacks, and deployments via AI
AI-powered reverse engineering assistant that bridges IDA Pro with language models through MCP.
MCP Server for kubernetes management commands
MCP Security Weekly
Get CVE alerts and security updates for io.github.venomseven/nslookup and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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
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:
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.
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.
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.
The hosted endpoint is a remote Streamable-HTTP server. Public tools work immediately; the first time you call a my_ tool, an OAuth-capable client opens a browser window to sign in to your nslookup.io account (see Signing in).
Claude Code (CLI)
claude mcp add --transport http nslookup https://mcp.nslookup.io/mcp
Claude Desktop / claude.ai (custom connector)
nslookup — URL: https://mcp.nslookup.io/mcpOr drop it into an .mcp.json (project) / your client's MCP config:
{
"mcpServers": {
"nslookup": {
"type": "http",
"url": "ht
... [View full README on GitHub](https://github.com/NsLookup-io/nslookup-mcp#readme)