Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.4hmetuyar/dns-intelligence

NPM · @GUARDBEE/MCP-DNS-INTELLIGENCE

DNS record enumeration, misconfiguration and dangling-subdomain detection

+9 this week 79 Trust /100

Last scanned (1 hour ago)

Scores higher than 61% of npm servers

Category Security

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 195 tokens (~48/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
  • Stability observed for 19 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Oct 26 +6
    • Stability: unverified → 0.43 ▲ functional
  • 29 Sept 26 +15
    • Malware scan: unverified → pass ▲ security
  • 28 Sept 26 55

    First indexed and scored.

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 17 Oct 2026 · Analysed npm/@guardbee/mcp-dns-intelligence@0.2.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~195 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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_email_security ~61

Check SPF, DMARC, and DKIM configuration for a domain and get actionable remediation advice

NameTypeReqDescription
dkimSelectorsarray–Additional DKIM selectors to check (default: common selectors)
domainstringyesDomain to check email security for

No output schema declared.

No examples provided.

enumerate_dns ~45

Enumerate all DNS records for a domain and detect SPF, DMARC, DKIM misconfigurations

NameTypeReqDescription
domainstringyesDomain to enumerate (e.g. example.com)

No output schema declared.

No examples provided.

enumerate_subdomains ~45

Enumerate common subdomains for a domain and detect dangling subdomain takeover candidates

NameTypeReqDescription
domainstringyesRoot domain to enumerate subdomains for (e.g. example.com)

No output schema declared.

No examples provided.

lookup_dns ~44

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

NameTypeReqDescription
domainstringyesDomain to query
typestringyesDNS record type to look up

No output schema declared.

No examples provided.

Install

How do I install the io.github.4hmetuyar/dns-intelligence MCP server?

io.github.4hmetuyar/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.

npm · @guardbee/mcp-dns-intelligence

# add to Claude Code
claude mcp add 4hmetuyar-dns-intelligence -- npx -y @guardbee/mcp-dns-intelligence
Common questions

What is the io.github.4hmetuyar/dns-intelligence MCP server?

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

Is the io.github.4hmetuyar/dns-intelligence MCP server safe to use?

io.github.4hmetuyar/dns-intelligence scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. It declares no install or post-install scripts. 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.4hmetuyar/dns-intelligence MCP server expose?

io.github.4hmetuyar/dns-intelligence exposes 4 tools: enumerate_dns, enumerate_subdomains, check_email_security, lookup_dns. Their descriptions and schemas cost roughly 195 tokens of context every time the server is loaded.

Is the io.github.4hmetuyar/dns-intelligence MCP server still maintained?

io.github.4hmetuyar/dns-intelligence is still listed as active in the MCP registry. We last reached this channel on 17 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.4hmetuyar/dns-intelligence MCP server under?

io.github.4hmetuyar/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.