Ext Ops Panel
Open dashboard
Comparison

com.stackhawk/stackhawk vs dev.dnsdoctor/dns-doctor

com.stackhawk/stackhawk is an MCP server published by stackhawk.com. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). dev.dnsdoctor/dns-doctor is an MCP server published by dnsdoctor.dev. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-16. 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
Marketplacecom.stackhawk/stackhawkdev.dnsdoctor/dns-doctor
Official MCP Registry Listed
Version: 1.1.1
Downloads/month (PyPI): 160
Downloads/week (PyPI): 47
Forks (GitHub): 8
Stars (GitHub): 9
Not marked · First seen
Listed
Version: 1.10.3
Downloads/month (npm): 827
Downloads/week (npm): 126
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Docker MCP Catalog Listed
Version: sha256:f5c273bf008b
Forks (GitHub): 8
Pulls (Docker Hub): 31 289
Stars (Docker Hub): 0
Stars (GitHub): 9
Not marked · First seen
Not listed

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

com.stackhawk/stackhawk vs dev.dnsdoctor/dns-doctor
Factcom.stackhawk/stackhawkdev.dnsdoctor/dns-doctor
Marketplaces that list it22
Stars (GitHub) (differs)9 (better)2 (worse)
Pulls (Docker Hub) (differs)31 289No figure on Docker Hub
Forks (GitHub) (differs)8 (better)0 (worse)
Last release (differs)Not published2026-10-15
Where it runs (differs)On your machine (stackhawk-mcp)Remote server (dnsdoctor.dev/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)7Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle2
Licence (differs)NOASSERTIONApache-2.0
Repository (differs)github.com/stackhawk/stackhawk-mcpgithub.com/dnsdoctor/claude-plugin
Changes in the last 7 days (differs)07
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 days 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

com.stackhawk/stackhawk

In its own words, on Official MCP Registry:

An MCP server that provides interaction with StackHawk's security scanning platform.

dev.dnsdoctor/dns-doctor

In its own words, on Official MCP Registry:

Scan, fix, verify and monitor DNS: SPF, DMARC, DKIM, propagation, health, expiry. Validated fixes.

How to run each

com.stackhawk/stackhawk As a local MCP server: PyPI package

Claude Code
claude mcp add --env "STACKHAWK_API_KEY=<YOUR_STACKHAWK_API_KEY>" --transport stdio stackhawk -- uvx stackhawk-mcp

Requires: STACKHAWK_API_KEY (secret)

dev.dnsdoctor/dns-doctor As a remote MCP server

Claude Code
claude mcp add --transport http dns-doctor https://dnsdoctor.dev/mcp

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

Only dev.dnsdoctor/dns-doctor has a remote endpoint we check. How we check endpoints

Tools each declares

Only com.stackhawk/stackhawk has

  • get_app_findings_for_triage
  • get_organization_info
  • list_applications
  • run_stackhawk_scan
  • setup_stackhawk_for_project
  • validate_field_exists
  • validate_stackhawk_config

Only dev.dnsdoctor/dns-doctor has

  • add_monitored_domain
  • audit_spf_includes
  • build_dmarc_upgrade
  • build_parked_domain_records
  • check_dkim_selector
  • check_domain_verification
  • check_lookalikes
  • check_propagation
  • check_record
  • check_reverse_dns
  • count_spf_lookups
  • generate_dmarc_record
Show the remaining 13
  • get_alerts
  • get_domain_records
  • get_email_test
  • get_lookalikes
  • get_readiness
  • get_report
  • list_email_tests
  • lookup_registration
  • parse_dmarc_report
  • scan_domain
  • start_email_test
  • start_monitoring_signup
  • validate_dmarc_record

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (dev.dnsdoctor/dns-doctor as of 2026-10-16). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

The marketplaces of dev.dnsdoctor/dns-doctor publish no settings it asks for, so we do not compare settings.

What it can do: com.stackhawk/stackhawk · What it can do: dev.dnsdoctor/dns-doctor · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. 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