MCP服务器用于DNS查询、传播检查和通过 nslookup.io 进行证书监控
概览
MCP服务器支持 nslookup.io DNS查询、SSL证书检查、安全扫描、GEO（AI准备度）评分、域智能以及您自己的监控账户——通过模型上下文协议。 nslookup.io MCP 服务器为任何支持 MCP 的 AI 助手（Claude、ChatGPT、Cursor、Windsurf 等）提供了直接访问 nslookup.io 的 DNS、证书、安全和监控工具。用通俗易懂的语言问——“对 github.com 运行 DNS 健康检查”或“我的哪种 SSL 证书最早过期？”——助手会帮你调出合适的工具。 - — 无需账户和API密钥即可正常工作的DNS、SSL、安全、地理和域智能查询。- — 读取您自己的 nslookup.io 监控账户（运行时间、DNS、WHOIS、SSL、传播、BIMI/VMC监控）。这些账户始终列出，但需要。 跳转到Connect设置，或查看工具参考页面查看完整列表。 连接有两种方式。—— 见下方说明。
概述（AI 翻译）
nslookup.io 的 MCP 服务器 通过模型上下文协议，进行DNS查询、SSL证书检查、安全扫描、GEO（人工智能准备度）评分、域智能以及您自己的监控账户。
网站 ·API文档 ·npm ·联系方式
这是什么？
nslookup.io MCP 服务器为任何支持 MCP 的 AI 助手（Claude、ChatGPT、Cursor、Windsurf 等）提供直接访问 nslookup.io 的 DNS、证书、安全和监控工具。用通俗易懂的语言询问——“对 github.com 运行 DNS 健康检查” 或 “我的哪个 SSL 证书最早过期？” ——助手会为你调出合适的工具。
共23件工具，分为两组：
- 17个公共工具 — DNS、SSL、安全、地理环境（GEO）和域智能查询，匿名，无需账户和API密钥。
- 6
my_账户工具 — 读取您自己的 nslookup.io 监控账户（运行时间、DNS、WHOIS、SSL、传播、BIMI/VMC 监控）。这些工具总是列出，但需要登录。
跳转到Connect设置，或查看工具参考页面查看完整列表。
连接
连接方式有两种。选一个——见下方说明。
| |**托管（推荐）**本地（NPX / 标准） | |—|—|—|
本页由 AI 翻译，技术细节请以原文为准。
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" } } }