check_svcb_https — BlackVeil DNS & Email Security Scanner MCP Tool Read-only
check_svcb_https
(check svcb https) is one of 80 tools on the
BlackVeil DNS & Email Security Scanner
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_svcb_https from your client
- Claude Code BlackVeil DNS & Email Security Scanner check_svcb_https run in your project directory
- Claude Desktop BlackVeil DNS & Email Security Scanner check_svcb_https ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor BlackVeil DNS & Email Security Scanner check_svcb_https ~/.cursor/mcp.json
- VS Code BlackVeil DNS & Email Security Scanner check_svcb_https .vscode/mcp.json
- Zed BlackVeil DNS & Email Security Scanner check_svcb_https ~/.config/zed/settings.json
- Windsurf BlackVeil DNS & Email Security Scanner check_svcb_https ~/.codeium/windsurf/mcp_config.json
- Cline BlackVeil DNS & Email Security Scanner check_svcb_https ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI BlackVeil DNS & Email Security Scanner check_svcb_https ~/.gemini/settings.json
- Grok BlackVeil DNS & Email Security Scanner check_svcb_https .mcp.json (in your project root)
- ChatGPT BlackVeil DNS & Email Security Scanner check_svcb_https Settings → Connectors → Advanced → Developer mode
- Claude.ai BlackVeil DNS & Email Security Scanner check_svcb_https Settings → Connectors → Add custom connector
- LangChain BlackVeil DNS & Email Security Scanner check_svcb_https pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http dns https://dns-mcp.blackveilsecurity.com/mcpOther tools on this server
- 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_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_dnskey_strength
- check_fast_flux
- check_subdomain_takeover
- check_authoritative_dns_infra
- check_root_server_set
- discover_brand_domains
- discover_brand_domains_start
- discover_brand_domains_status
- discover_brand_domains_findings
- brand_audit_single
- brand_audit_batch_start
- brand_audit_status
- brand_audit_get_report
- list_brand_audit_watches
- register_brand_audit_watch
- delete_brand_audit_watch
- scan_buckets_start
- scan_buckets_status
- scan_buckets_findings
- osint_investigate_domain_start
- osint_investigate_infrastructure_start
- osint_investigate_supply_chain_start
- osint_investigate_username_start
- osint_investigate_email_start
- osint_investigation_status
- osint_investigation_report
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.