io.github.venomseven/nslookup

REMOTE · MCP.NSLOOKUP.IO · 2 COMPONENTS · SCANNED AUG 3

DNS lookups, health reports, SSL certs, security scans, GEO scoring, uptime checks

Available components

remote · mcp.nslookup.io 66 npm · @nslookup-io/mcp-server 66

+2 this week 66 66 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security54

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to call this server, and 23 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability79

AI-judged instruction clarity (excellent).Pass
Tool/resource definitions use about 2303 tokens (~100/item across 23 items; 23 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.nslookup.io

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.toml

[mcp_servers.venomseven-nslookup]
url = "https://mcp.nslookup.io/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "venomseven-nslookup": {
      "type": "remote",
      "url": "https://mcp.nslookup.io/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add venomseven-nslookup --url https://mcp.nslookup.io/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  venomseven-nslookup:
    url: "https://mcp.nslookup.io/mcp"

// mcp.json

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

2 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
28 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 63

First indexed and scored.

Show 5 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://mcp.nslookup.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=nslookup.io	CN=WE1,O=Google Trust Services,C=US	11 Jul 2026	9 Oct 2026	ECDSA 256	ECDSA-SHA256	68eac46c974ddd10131b92e353cdbf25
SANs: nslookup.io, *.nslookup.io
CN=WE1,O=Google Trust Services,C=US (CA)	CN=GTS Root R4,O=Google Trust Services LLC,C=US	13 Dec 2023	20 Feb 2029	ECDSA 256	ECDSA-SHA384	7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA)	CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE	15 Nov 2023	28 Jan 2028	ECDSA 384	SHA256-RSA	7fe530bf331343bedd821610493d8a1b

DNSSEC secure

Validation of mcp.nslookup.io. — Secure

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
io.	present	57355	8	Verified
nslookup.io.	present	2371	13	Verified
mcp.nslookup.io.				Verified address RRset verified with the apex keys

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Header	Value
strict-transport-security	max-age=15724800; includeSubDomains

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://mcp.nslookup.io/mcp	Verified	200
http (plaintext)	http://mcp.nslookup.io/mcp	Inconclusive	405

MCP tools — 23 exposed · ~2,270 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

bimi_check ~95

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.

Input Output Examples

Name	Type	Req	Description
domain	string	yes	Domain name to check the BIMI record for (e.g. easydmarc.com)

No output schema declared.

No examples provided.

bimi_vmc ~75

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.

Input Output Examples

Name	Type	Req	Description
domain	string	yes	Domain name to check BIMI/VMC for (e.g. google.com)

No output schema declared.

No examples provided.

dns_change_review ~187

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.

Input Output Examples

Name	Type	Req	Description
domain	string	yes	Domain whose current public DNS will be compared against the proposed records (e.g. example.com)
records	—	yes	The proposed (future) DNS state: either BIND zone-file text or an array of {type, name?, value, ttl?, priority?} records. This is the COMPLETE desired state for the zone — records present now but omi…
server	string	—	DNS server to use when fetching the current records. Default: cloudflare.

No output schema declared.

No examples provided.

dns_health ~136

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.

Input Output Examples

Name	Type	Req	Description
domain	string	yes	Domain name to check DNS health for (e.g. example.com)

No output schema declared.

No examples provided.

dns_lookup ~91

Look up all common DNS records (A, AAAA, NS, MX, TXT, CNAME, SOA) for a domain. Returns results from a specified DNS server.

Input Output Examples

Name	Type	Req	Description
domain	string	yes	Domain name to look up (e.g. example.com)
server	string	—	DNS server to query. Default: cloudflare. Use 'authoritative' for the domain's own nameservers.

No output schema declared.

No examples provided.

dns_propagation ~100

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.

Input Output Examples

Name	Type	Req	Description
domain	string	yes	Domain name to check propagation for (e.g. example.com)
recordType	string	yes	DNS record type to check (e.g. A, AAAA, MX, NS, TXT, CNAME)

No output schema declared.

No examples provided.

dns_record ~147

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.

Input Output Examples

Name	Type	Req	Description
domain	string	yes	Domain name (or IP address for PTR lookups) to query (e.g. example.com)
server	string	—	DNS server to query. Default: cloudflare. Use 'authoritative' for the domain's own nameservers.
type	string	yes	DNS record type (e.g. A, MX, TXT, CNAME, SPF, HTTPS, DNSKEY)

No output schema declared.

No examples provided.

domain_scanner ~71

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.

Input Output Examples

Name	Type	Req	Description
domain	string	yes	Domain name to scan (e.g. example.com)

No output schema declared.

No examples provided.

geo_checker ~93

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.

Input Output Examples

Name	Type	Req	Description
domain	string	yes	Domain name to check GEO score for (e.g. github.com)

No output schema declared.

No examples provided.

hosting_report ~94

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.

Input Output Examples

Name	Type	Req	Description
domain	string	yes	Domain or URL to build a hosting report for (e.g. github.com). URLs are normalized to a bare hostname.

No output schema declared.

No examples provided.

my_certificates ~67

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).

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

my_dns_changes ~82

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).

Input Output Examples

Name	Type	Req	Description
limit	integer	—	Maximum reviews to return (default 10)

No output schema declared.

No examples provided.

my_incidents ~113

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).

Input Output Examples

Name	Type	Req	Description
limit	integer	—	Maximum incidents to return (default 20)
status	string	—	'open' (default) = unresolved incidents (triggered or acknowledged); 'all' = include resolved history

No output schema declared.

No examples provided.

my_monitors ~66

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).

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

my_overview ~73

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).

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

my_uptime_history ~113

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).

Input Output Examples

Name	Type	Req	Description
hours	integer	—	History window in hours (default 24)
monitorId	integer	—	Monitor id (from my_monitors)
url	string	—	Monitor URL to match instead of an id (e.g. https://example.com)

No output schema declared.

No examples provided.

rdap_lookup ~158

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.

Input Output Examples

Name	Type	Req	Description
query	string	yes	What to look up: an IPv4/IPv6 address (e.g. 8.8.8.8), an AS number (e.g. AS13335 or 13335), or a domain name (e.g. example.com)

No output schema declared.

No examples provided.

security_scan ~76

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).

Input Output Examples

Name	Type	Req	Description
domain	string	yes	Domain name to security scan (e.g. example.com)

No output schema declared.

No examples provided.

ssl_certificate ~65

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.

Input Output Examples

Name	Type	Req	Description
domain	string	yes	Domain name to check SSL certificate for (e.g. github.com)

No output schema declared.

No examples provided.

status_page ~127

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.

Input Output Examples

Name	Type	Req	Description
domain	string	—	Custom domain the status page is served on (e.g. status.acme.com)
slug	string	—	Status page slug (e.g. 'nslookup-io' for hosted.nslookup.io/nslookup-io)

No output schema declared.

No examples provided.

uptime_check ~88

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.

Input Output Examples

Name	Type	Req	Description
timeout	number	—	Timeout in milliseconds (default: 10000)
url	string	yes	Full URL to check (e.g. https://github.com)

No output schema declared.

No examples provided.

uptime_check_multi ~89

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.

Input Output Examples

Name	Type	Req	Description
timeout	number	—	Timeout in milliseconds (default: 30000)
url	string	yes	Full URL to check (e.g. https://github.com)

No output schema declared.

No examples provided.

webservers ~64

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.

Input Output Examples

Name	Type	Req	Description
domain	string	yes	Domain name to look up IP addresses for (e.g. example.com)

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	63
27 Jul	64
28 Jul	65
29 Jul	65
30 Jul	66
31 Jul	65
1 Aug	65
2 Aug	66
3 Aug	66