nslookup-io/nslookup-mcp
Developer toolsこのページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。 原文を見る
MCP server for DNS lookups, propagation checks, and certificate monitoring via nslookup.io
概要
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. 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. - — DNS, SSL, security, GEO, and domain-intelligence lookups that work , with no account and no API key. - — read your own nslookup.io monitoring account (uptime, DNS, WHOIS, SSL, propagation, BIMI/VMC monitors). These are always listed but require . Jump to Connect to get set up, or the Tool reference for the full list. There are two ways to connect. — see the note below.
README
以下は原文 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.
インストール
npx -y @nslookup-io/mcp-server設定
{ "mcpServers": { "nslookup": { "type": "http", "url": "https://mcp.nslookup.io/mcp" } } }