# io.github.GuardBee/dns-intelligence (npm · @guardbee/mcp-dns-intelligence)

DNS record enumeration, misconfiguration and dangling-subdomain detection

- Trust score: 80/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-16

## Components

- npm · `@guardbee/mcp-dns-intelligence`: 80/100 (this document), [markdown](https://verifymcp.io/servers/guardbee-dns-intelligence/guardbee-mcp-dns-intelligence.md), [page](https://verifymcp.io/servers/guardbee-dns-intelligence/guardbee-mcp-dns-intelligence)

## Channel facts

- Registry: `npm`
- Package: `@guardbee/mcp-dns-intelligence`
- Version: `0.8.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-16.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to GuardBee/guardbee-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 563 tokens (~93/item across 6 items; 6 tools + 0 resources), lean.
  - 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the io.github.GuardBee/dns-intelligence MCP server?

io.github.GuardBee/dns-intelligence runs locally as an npm package, launched with npx -y @guardbee/mcp-dns-intelligence. 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 guardbee-dns-intelligence -- npx -y @guardbee/mcp-dns-intelligence
```

### Cursor

```json
{
  "mcpServers": {
    "guardbee-dns-intelligence": {
      "command": "npx",
      "args": [
        "-y",
        "@guardbee/mcp-dns-intelligence"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "guardbee-dns-intelligence": {
      "command": "npx",
      "args": [
        "-y",
        "@guardbee/mcp-dns-intelligence"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add guardbee-dns-intelligence -- npx -y @guardbee/mcp-dns-intelligence
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "guardbee-dns-intelligence": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@guardbee/mcp-dns-intelligence"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add guardbee-dns-intelligence --command npx --arg -y --arg @guardbee/mcp-dns-intelligence
```

### Hermes

```yaml
mcp_servers:
  guardbee-dns-intelligence:
    command: "npx"
    args: ["-y", "@guardbee/mcp-dns-intelligence"]
```

### Netclaw

```json
{
  "McpServers": {
    "guardbee-dns-intelligence": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@guardbee/mcp-dns-intelligence"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add guardbee-dns-intelligence -t stdio -c npx -a -y @guardbee/mcp-dns-intelligence
```

### Other

```json
{
  "mcpServers": {
    "guardbee-dns-intelligence": {
      "command": "npx",
      "args": [
        "-y",
        "@guardbee/mcp-dns-intelligence"
      ]
    }
  }
}
```

## 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-15 (score 80, +42)

- [security improvement] Injection markers: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Dependency health: unverified → 0.85
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100

### 2026-10-14 (score 38, −11)

- [security regression] Known CVEs: pass → unverified
- [functional regression] Dependency health: 0.85 → unverified
- [functional] Package version: 0.3.0 → 0.8.0
- [functional] Package version: 0.3.0 → 0.7.0
- [functional] Package version: 0.3.0 → 0.5.0

### 2026-10-13 (score 49)

First indexed and scored.

## MCP tools (6)

### `enumerate_dns` (~136 tokens)

Enumerate all DNS records for a domain and detect misconfigurations: SPF, DMARC, DKIM key strength, MTA-STS/TLS-RPT, MX, DNSSEC (signed / broken / weak algorithms) and CAA (including whether it blocks the CA of the live certificate) and nameservers (lame delegation, anonymous zone transfer, open recursion)

Input parameters:

- `domain` (string, required): Domain to enumerate (e.g. example.com)
- `nameserverProbe` (boolean): Query each nameserver directly for lame delegation, SOA serial drift, anonymous zone transfer (AXFR) and open recursion (default: true)

### `audit_domains` (~96 tokens)

Audit several domains at once (e.g. every brand or country domain) and compare them: an A–F grade per domain from all DNS, email, DNSSEC, CAA and nameserver checks, plus each domain's most serious findings

Input parameters:

- `domains` (array, required): Domains to audit, e.g. ["example.com", "example.de"]
- `nameserverProbe` (boolean): Query nameservers directly (default: true)

### `enumerate_subdomains` (~142 tokens)

Find subdomains from Certificate Transparency logs and a common-name wordlist, and detect subdomain takeovers: CNAMEs to S3, GitHub Pages, Azure, Heroku, Netlify and other providers whose resource is gone (verified fingerprints), or to targets that no longer exist

Input parameters:

- `certificateTransparency` (boolean): Add names found in Certificate Transparency logs via crt.sh and Cert Spotter (default: true; sends only the domain name)
- `domain` (string, required): Root domain to enumerate subdomains for (e.g. example.com)
- `httpProbe` (boolean): Fetch pages behind provider CNAMEs to match takeover fingerprints (default: true)

### `check_takeover` (~67 tokens)

Check specific hostnames (e.g. from your DNS zone or certificate logs) for subdomain takeover

Input parameters:

- `hosts` (array, required): Hostnames to check, e.g. ["blog.example.com"]
- `httpProbe` (boolean): Fetch pages to match takeover fingerprints (default: true)

### `check_email_security` (~78 tokens)

Check a domain's email security: MX, SPF (nested lookup count), DMARC, DKIM key strength, MTA-STS and TLS-RPT, with remediation advice

Input parameters:

- `dkimSelectors` (array): Additional DKIM selectors to check (default: common selectors)
- `domain` (string, required): Domain to check email security for

### `lookup_dns` (~44 tokens)

Perform a targeted DNS lookup for specific record types on a domain

Input parameters:

- `domain` (string, required): Domain to query
- `type` (string, required): DNS record type to look up

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/guardbee-dns-intelligence/guardbee-mcp-dns-intelligence#diagnostics

## Score history

- 2026-10-16: 80
- 2026-10-15: 80
- 2026-10-14: 38
- 2026-10-13: 49

## Common questions

### What is the io.github.GuardBee/dns-intelligence MCP server?

io.github.GuardBee/dns-intelligence is an MCP server listed in the public MCP registry as io.github.GuardBee/dns-intelligence. DNS record enumeration, misconfiguration and dangling-subdomain detection. This page covers its npm package (@guardbee/mcp-dns-intelligence).

### Is the io.github.GuardBee/dns-intelligence MCP server safe to use?

io.github.GuardBee/dns-intelligence scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 io.github.GuardBee/dns-intelligence MCP server expose?

io.github.GuardBee/dns-intelligence exposes 6 tools: enumerate_dns, audit_domains, enumerate_subdomains, check_takeover, check_email_security, lookup_dns. Their descriptions and schemas cost roughly 563 tokens of context every time the server is loaded.

### Is the io.github.GuardBee/dns-intelligence MCP server still maintained?

io.github.GuardBee/dns-intelligence is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.GuardBee/dns-intelligence MCP server under?

io.github.GuardBee/dns-intelligence declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@guardbee/mcp-dns-intelligence
- Socket report: https://socket.dev/npm/package/@guardbee/mcp-dns-intelligence
- Repository: https://github.com/GuardBee/guardbee-mcp
- Changelog RSS feed: https://verifymcp.io/servers/guardbee-dns-intelligence/guardbee-mcp-dns-intelligence.xml
- Changelog JSON feed: https://verifymcp.io/servers/guardbee-dns-intelligence/guardbee-mcp-dns-intelligence.json
- HTML version of this page: https://verifymcp.io/servers/guardbee-dns-intelligence/guardbee-mcp-dns-intelligence