Home / MCP registry index / com.blackveilsecurity/dns

BlackVeil DNS & Email Security Scanner

com.blackveilsecurity/dns in the official MCP registry. Endpoint https://dns-mcp.blackveilsecurity.com/mcp. Source: github.com/MadaBurns/bv-mcp.

The registry describes it as: DNS and email security scanner with 81 MCP tools for SPF, DMARC, DNSSEC, SSL, and brand audits.

We read its 81 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

check_mx check_spf check_dmarc check_dkim check_dnssec check_ssl check_mta_sts check_ns check_caa check_bimi check_tlsrpt check_http_security check_dane check_ptr check_dane_https check_svcb_https check_lookalikes check_subdomailing scan_domain batch_scan batch_scan_start batch_scan_status batch_scan_findings compare_domains compare_baseline check_shadow_domains check_txt_hygiene check_mx_reputation check_srv check_zone_hygiene generate get_domain_rank get_benchmark get_provider_insights assess_spoofability check_resolver_consistency explain_finding map_supply_chain analyze_drift validate_fix resolve_spf_chain discover_subdomains map_compliance sge_quickscan prioritize_portfolio_leads simulate_attack_paths check_dbl check_rbl cymru_asn rdap_lookup check_realtime_threat_feed check_nsec_walkability check_dnssec_chain check_agent_discovery check_llms_txt check_dnskey_strength check_fast_flux check_subdomain_takeover check_authoritative_dns_infra check_root_server_set and 21 more

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/com-blackveilsecurity-dns/badge.svg)](https://lazaretto.dev/mcp-registry/com-blackveilsecurity-dns)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Email MCP servers · Security MCP servers

AgentMart
ai.ciphyr.agentmart/agentmart
112 tools, nothing matched
2026-10-21
Fine Structure
ai.finestructure/fine-structure
99 tools, nothing matched
2026-10-21
StartupHub.ai
ai.startuphub/startuphub
68 tools, nothing matched
2026-10-21
Refine Job Search
co.getrefine/refine
62 tools, nothing matched
2026-10-22
ai.sendraven/mcp
ai.sendraven/mcp
56 tools, nothing matched
2026-10-22
netsi
io.github.bluedotsoft/netsi
51 tools, nothing matched
2026-10-22