# Zovo DNS Checker (remote · dns-checker.zovo.one)

Live DNS & email auth checks

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

## Components

- remote · `dns-checker.zovo.one`: 74/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-dns-checker/dns-checker.md), [page](https://verifymcp.io/servers/theluckystrike-dns-checker/dns-checker)

## Channel facts

- Endpoint: `https://dns-checker.zovo.one/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-22.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 519 tokens (~173/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Zovo DNS Checker MCP server?

Zovo DNS Checker is a hosted endpoint at https://dns-checker.zovo.one/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http theluckystrike-dns-checker 'https://dns-checker.zovo.one/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-dns-checker": {
      "url": "https://dns-checker.zovo.one/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-dns-checker": {
      "type": "http",
      "url": "https://dns-checker.zovo.one/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-dns-checker]
url = "https://dns-checker.zovo.one/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-dns-checker": {
      "type": "remote",
      "url": "https://dns-checker.zovo.one/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-dns-checker --url 'https://dns-checker.zovo.one/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-dns-checker:
    url: "https://dns-checker.zovo.one/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-dns-checker": {
      "Transport": "http",
      "Url": "https://dns-checker.zovo.one/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-dns-checker -t streamable-http -u 'https://dns-checker.zovo.one/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-dns-checker": {
      "type": "http",
      "url": "https://dns-checker.zovo.one/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-22 (score 74)

First indexed and scored.

## MCP tools (2)

### `check_email_dns` (~200 tokens)

Check email DNS

Use this when the user wants an email DNS check, a DMARC checker, an SPF record checker, a DKIM checker, or an MX lookup for a domain. Reads the live public DNS records through DNS-over-HTTPS and returns MX hosts, the SPF record with its DNS-lookup count against the limit of 10, the DMARC policy, reporting and alignment, DKIM keys for the selectors you give, and a pass/warn/fail findings list with a fix and a CSV report. Do not use for internal DNS server visibility, full deliverability tests, or reading or sending mail.

Input parameters:

- `dkim_selectors` (array): Up to 5 DKIM selector names to test, e.g. ["mail", "selector1"]. Ask the mail provider or check the DKIM signature header if the selector is unknown.
- `domain` (string, required): The domain to check, without http or a path, e.g. example.com.

Output parameters:

- `checked_at` (string)
- `dkim` (array)
- `dmarc` (object)
- `domain` (string)
- `downloads` (object)
- `findings` (array)
- `limits` (string)
- `mx` (object)
- `source` (object)
- `sources` (array)
- `spf` (object)
- `summary` (object)

### `lookup_dns_records` (~189 tokens)

Look up DNS records

Use this when the user wants a dns lookup, an mx record check, or a txt record lookup for a domain. Reads live public DNS records through DNS-over-HTTPS and returns A, AAAA, MX, NS, TXT, CNAME, CAA, and SOA records with their TTLs, plus a CSV report. Do not use for internal DNS server visibility, reverse DNS of an IP address, or records outside the supported type list.

Input parameters:

- `domain` (string, required): The domain to look up, e.g. example.com or mail.example.com.
- `types` (array): Record types to return, a subset of A, AAAA, MX, NS, TXT, CNAME, CAA, SOA, e.g. ["MX", "TXT"]. Omit for A, AAAA, MX, NS, TXT, CNAME, CAA, and SOA.

Output parameters:

- `checked_at` (string)
- `counts` (object)
- `domain` (string)
- `downloads` (object)
- `findings` (array)
- `limits` (string)
- `records` (object)
- `source` (object)
- `sources` (array)
- `total` (number)
- `types` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-dns-checker/dns-checker#diagnostics

## Score history

- 2026-10-22: 74

## Common questions

### What is the Zovo DNS Checker MCP server?

Zovo DNS Checker is an MCP server listed in the public MCP registry as io.github.theluckystrike/dns-checker. Live DNS & email auth checks. This page covers its hosted endpoint (https://dns-checker.zovo.one/mcp).

### Is the Zovo DNS Checker MCP server safe to use?

Zovo DNS Checker scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Zovo DNS Checker MCP server expose?

Zovo DNS Checker exposes 2 tools: check_email_dns, lookup_dns_records. Their descriptions and schemas cost roughly 389 tokens of context every time the server is loaded.

### Does the Zovo DNS Checker MCP server require authentication?

No. We connected to Zovo DNS Checker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Zovo DNS Checker MCP server still maintained?

Zovo DNS Checker is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://dns-checker.zovo.one/mcp
- Website: https://dns-checker.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-dns-checker/dns-checker.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-dns-checker/dns-checker.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-dns-checker/dns-checker