Ext Ops Panel
Open dashboard
Comparison

Shodan vs BlackVeil DNS & Email Security Scanner

Shodan is an MCP server published by Cyreslab-AI. Marketplaces we read that list it: 1 (Docker MCP Catalog). BlackVeil DNS & Email Security Scanner is an MCP server published by blackveilsecurity.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceShodanBlackVeil DNS & Email Security Scanner
Docker MCP Catalog Listed
Version: sha256:f99f2d2d6955
Forks (GitHub): 12
Pulls (Docker Hub): 47 264
Stars (Docker Hub): 8
Stars (GitHub): 53
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 3.111.0
Forks (GitHub): 7
Stars (GitHub): 9
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Shodan vs BlackVeil DNS & Email Security Scanner
FactShodanBlackVeil DNS & Email Security Scanner
Marketplaces that list it11
Stars (GitHub) (differs)53 (better)9 (worse)
Pulls (Docker Hub) (differs)47 264No figure on Docker Hub
Forks (GitHub) (differs)12 (better)7 (worse)
Last release (differs)Not published2026-11-10
Where it runs (differs)On your machine (mcp/cyreslab-ai-shodan)Remote server (dns-mcp.blackveilsecurity.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)5Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/cyreslab-ai/shodan-mcp-servergithub.com/madaburns/bv-mcp
Changes in the last 7 days (differs)05
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 22 h ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Shodan

In its own words, on Docker MCP Catalog:

MCP server for Shodan — host/network recon, CVE and exploit lookup, InternetDB, and persistent alerts (34 tools).

BlackVeil DNS & Email Security Scanner

In its own words, on Official MCP Registry:

DNS and email security scanner with 82 MCP tools for SPF, DMARC, DNSSEC, SSL, and brand audits.

How to run each

Shodan As a local MCP server: Docker image

Claude Code
claude mcp add --env "SHODAN_API_KEY=<YOUR_SHODAN_API_KEY>" --transport stdio cyreslab-ai-shodan -- docker run -i --rm -e SHODAN_API_KEY mcp/cyreslab-ai-shodan

Requires: SHODAN_API_KEY (secret)

BlackVeil DNS & Email Security Scanner As a remote MCP server

Claude Code
claude mcp add --transport http dns https://dns-mcp.blackveilsecurity.com/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only BlackVeil DNS & Email Security Scanner has a remote endpoint we check. How we check endpoints

Tools each declares

Only Shodan has

  • get_host_info
  • get_ssl_info
  • scan_network_range
  • search_iot_devices
  • search_shodan

Only BlackVeil DNS & Email Security Scanner has

  • analyze_drift
  • assess_spoofability
  • batch_scan
  • batch_scan_findings
  • batch_scan_start
  • batch_scan_status
  • brand_audit_batch_start
  • brand_audit_get_report
  • brand_audit_single
  • brand_audit_status
  • check_agent_discovery
  • check_authoritative_dns_infra
Show the remaining 69
  • check_bimi
  • check_caa
  • check_dane
  • check_dane_https
  • check_dbl
  • check_dkim
  • check_dmarc
  • check_dnskey_strength
  • check_dnssec
  • check_dnssec_chain
  • check_fast_flux
  • check_http_security
  • check_llms_txt
  • check_lookalikes
  • check_mta_sts
  • check_mx
  • check_mx_reputation
  • check_ns
  • check_nsec_walkability
  • check_ptr
  • check_rbl
  • check_realtime_threat_feed
  • check_resolver_consistency
  • check_root_server_set
  • check_shadow_domains
  • check_spf
  • check_srv
  • check_ssl
  • check_subdomailing
  • check_subdomain_takeover
  • check_svcb_https
  • check_tlsrpt
  • check_txt_hygiene
  • check_zone_hygiene
  • compare_baseline
  • compare_domains
  • cymru_asn
  • delete_brand_audit_watch
  • discover_brand_domains
  • discover_brand_domains_findings
  • discover_brand_domains_start
  • discover_brand_domains_status
  • discover_subdomains
  • explain_finding
  • generate
  • get_benchmark
  • get_domain_rank
  • get_provider_insights
  • list_brand_audit_watches
  • map_compliance
  • map_supply_chain
  • osint_investigate_domain_start
  • osint_investigate_email_start
  • osint_investigate_infrastructure_start
  • osint_investigate_supply_chain_start
  • osint_investigate_username_start
  • osint_investigation_report
  • osint_investigation_status
  • prioritize_portfolio_leads
  • rdap_lookup
  • register_brand_audit_watch
  • resolve_spf_chain
  • scan_buckets_findings
  • scan_buckets_start
  • scan_buckets_status
  • scan_domain
  • sge_quickscan
  • simulate_attack_paths
  • validate_fix

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (BlackVeil DNS & Email Security Scanner as of 2026-10-20). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

The marketplaces of BlackVeil DNS & Email Security Scanner publish no settings it asks for, so we do not compare settings.

What it can do: Shodan · What it can do: BlackVeil DNS & Email Security Scanner · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built