dns
Server Details
DNS and email security scanner with 79 MCP tools for SPF, DMARC, DNSSEC, SSL, and brand audits.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- MadaBurns/bv-mcp
- GitHub Stars
- 7
- Server Listing
- Blackveil DNS
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 3.9/5 across 68 of 74 tools scored. Lowest: 3.2/5.
Most tools have clearly distinct purposes, but some overlap exists, e.g., check_dnssec vs check_dnssec_chain, or multiple OSINT investigation start tools that are similar. The brand_audit_* series and check_shadow_domains/discover_brand_domains also have overlapping concepts. Overall, an agent could distinguish most tools with careful reading.
Tool names use a mix of verb patterns: check_, generate_, scan_, map_, resolve_, start_, status_, etc. While many follow check_ (a large group), the variety of prefixes (analyze_, assess_, validate_, compare_, batch_) and some inconsistent suffixes (findings vs report) create moderate inconsistency. The pattern is not fully predictable.
74 tools is excessive for a single server. The domain of DNS security is broad but could be organized into fewer, more granular tools or sub-categories. Many tools are highly specific (e.g., check_root_server_set, check_nsec_walkability), and the sheer number risks overwhelming agents and users. A more curated set would improve coherence.
The tool set is remarkably comprehensive, covering DNS checks, email authentication, brand audits, OSINT, cloud buckets, compliance mapping, and remediation generation. Minor gaps exist (e.g., no direct tool for DKIM key generation beyond config, or DNSSEC maintenance), but the overall surface is very complete for its domain.
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.