nslookup
Server Details
DNS lookups, health reports, SSL certs, security scans, GEO scoring, uptime checks
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- NsLookup-io/nslookup-mcp
- GitHub Stars
- 21
- Server Listing
- nslookup.io MCP Server
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4/5 across 23 of 23 tools scored. Lowest: 2.9/5.
Tools have mostly distinct purposes, e.g., dns_lookup vs dns_record vs dns_propagation are different operations. A few overlaps like bimi_check versus bimi_vmc and dns_lookup versus dns_record could cause slight confusion, but descriptions are clear enough.
All tools use snake_case with consistent verb_noun pattern (e.g., dns_lookup, bimi_check, uptime_check). The my_* prefix for account-specific tools provides a clear sub-pattern. No mixed conventions.
23 tools is somewhat high but justified for a DNS/domain monitoring server covering lookups, health checks, security, SSL, RDAP, BIMI, uptime, and account management. Each tool adds distinct value, though a few could be merged.
Covers DNS, SSL, security, hosting, BIMI, RDAP, and account monitoring comprehensively. Minor gaps: no direct WHOIS (RDAP covers registration) and no DNS record modification tools (read-only focus). Overall well-rounded.
Available Tools
23 toolsbimi_checkInspect
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., logo URL, and authority (VMC) URL if declared.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain name to check the BIMI record for (e.g. easydmarc.com) |
bimi_vmcInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain name to check BIMI/VMC for (e.g. google.com) |
dns_change_reviewInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain whose current public DNS will be compared against the proposed records (e.g. example.com) | |
| server | No | DNS server to use when fetching the current records. Default: cloudflare. | |
| 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 omitted here are treated as deletions. |
dns_healthInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain name to check DNS health for (e.g. example.com) |
dns_lookupInspect
Look up all common DNS records (A, AAAA, NS, MX, TXT, CNAME, SOA) for a domain. Returns results from a specified DNS server.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain name to look up (e.g. example.com) | |
| server | No | DNS server to query. Default: cloudflare. Use 'authoritative' for the domain's own nameservers. |
dns_propagationInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain name to check propagation for (e.g. example.com) | |
| recordType | Yes | DNS record type to check (e.g. A, AAAA, MX, NS, TXT, CNAME) |
dns_recordInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| type | Yes | DNS record type (e.g. A, MX, TXT, CNAME, SPF, HTTPS, DNSKEY) | |
| domain | Yes | Domain name (or IP address for PTR lookups) to query (e.g. example.com) | |
| server | No | DNS server to query. Default: cloudflare. Use 'authoritative' for the domain's own nameservers. |
domain_scannerInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain name to scan (e.g. example.com) |
geo_checkerInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain name to check GEO score for (e.g. github.com) |
hosting_reportInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain or URL to build a hosting report for (e.g. github.com). URLs are normalized to a bare hostname. |
my_certificatesInspect
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).
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
my_dns_changesInspect
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).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum reviews to return (default 10) |
my_incidentsInspect
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).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum incidents to return (default 20) | |
| status | No | 'open' (default) = unresolved incidents (triggered or acknowledged); 'all' = include resolved history |
my_monitorsInspect
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).
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
my_overviewInspect
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).
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
my_uptime_historyInspect
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).
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | Monitor URL to match instead of an id (e.g. https://example.com) | |
| hours | No | History window in hours (default 24) | |
| monitorId | No | Monitor id (from my_monitors) |
rdap_lookupInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| query | 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) |
security_scanInspect
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).
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain name to security scan (e.g. example.com) |
ssl_certificateInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain name to check SSL certificate for (e.g. github.com) |
status_pageInspect
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/) or by the custom domain the page is served on. Provide exactly one of slug or domain.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | No | Status page slug (e.g. 'nslookup-io' for hosted.nslookup.io/nslookup-io) | |
| domain | No | Custom domain the status page is served on (e.g. status.acme.com) |
uptime_checkInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Full URL to check (e.g. https://github.com) | |
| timeout | No | Timeout in milliseconds (default: 10000) |
uptime_check_multiInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Full URL to check (e.g. https://github.com) | |
| timeout | No | Timeout in milliseconds (default: 30000) |
webserversInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain name to look up IP addresses for (e.g. example.com) |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Your Connectors
Sign in to create a connector for this server.