DNS Security Checks Guide — BlackVeil DNS & Email Security Scanner MCP Resource

DNS Security Checks Guide is one of 6 resources on the BlackVeil DNS & Email Security Scanner MCP server. Connect the server and your client can attach it as context.

by client

How to attach DNS Security Checks Guide from your client

• Claude Code BlackVeil DNS & Email Security Scanner Resource/DNS Security Checks Guide run in your project directory
• Claude Desktop BlackVeil DNS & Email Security Scanner Resource/DNS Security Checks Guide ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor BlackVeil DNS & Email Security Scanner Resource/DNS Security Checks Guide ~/.cursor/mcp.json
• VS Code BlackVeil DNS & Email Security Scanner Resource/DNS Security Checks Guide .vscode/mcp.json
• Zed BlackVeil DNS & Email Security Scanner Resource/DNS Security Checks Guide ~/.config/zed/settings.json
• Windsurf BlackVeil DNS & Email Security Scanner Resource/DNS Security Checks Guide ~/.codeium/windsurf/mcp_config.json
• Cline BlackVeil DNS & Email Security Scanner Resource/DNS Security Checks Guide ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI BlackVeil DNS & Email Security Scanner Resource/DNS Security Checks Guide ~/.gemini/settings.json
• Grok BlackVeil DNS & Email Security Scanner Resource/DNS Security Checks Guide .mcp.json (in your project root)
• ChatGPT BlackVeil DNS & Email Security Scanner Resource/DNS Security Checks Guide Settings → Connectors → Advanced → Developer mode
• Claude.ai BlackVeil DNS & Email Security Scanner Resource/DNS Security Checks Guide Settings → Connectors → Add custom connector
• LangChain BlackVeil DNS & Email Security Scanner Resource/DNS Security Checks Guide pip install langchain-mcp-adapters

Other resources on this server

• Scoring Methodology
• Supported DNS Record Types
• Agent Workflow Guide
• Intelligence Layer Guide
• DNS Remediation Guide

BlackVeil DNS & Email Security Scanner also offers 7 prompts — things you invoke, where a resource is context you attach.

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.